Pass Your Juniper JN0-364 Exam Easy!

Juniper JN0-364 Exam Questions & Answers, Accurate & Verified By IT Experts

Instant Download, Free Fast Updates, 99.6% Pass Rate

JN0-364 Premium VCE File

Juniper JN0-364 Premium File

69 Questions & Answers

Last Update: Oct 24, 2026

$69.99

JN0-364 Bundle gives you unlimited access to "JN0-364" files. However, this does not replace the need for a .vce exam simulator. To download VCE exam simulator click here
JN0-364 Premium VCE File
Juniper JN0-364 Premium File

69 Questions & Answers

Last Update: Oct 24, 2026

$69.99

Juniper JN0-364 Exam Bundle gives you unlimited access to "JN0-364" files. However, this does not replace the need for a .vce exam simulator. To download your .vce exam simulator click here

Juniper JN0-364 Practice Test 3

Question 20

During production incident triage, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
  2. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
  3. Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
  4. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

Explanation

Correct Answer

A:

Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. In the live production incident, the reported evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The intervention follows the governing fact that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. Closure requires the corresponding specific confirmation: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.

Incorrect Answers

B:

Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the live production incident being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

C:

Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. This action was designed for the separate Aggregate route contribution case, not the live production incident being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

D:

Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. This action was designed for the separate Equal-cost multipath eligibility case, not the live production incident being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

Question 21

During production incident triage, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
  2. Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.
  3. Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
  4. Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.

Explanation

Correct Answer

D:

Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. In the live production incident, the reported evidence is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. The intervention follows the governing fact that Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. Closure requires the corresponding specific confirmation: The MAC stabilizes on its expected port or approved redundancy construct and packet loss disappears.

Incorrect Answers

A:

Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. This action was designed for the separate Native VLAN mismatch case, not the live production incident being assessed. The present observation is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Its governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The narrower applicable remedy is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.

B:

Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing. This action was designed for the separate IRB routed gateway missing case, not the live production incident being assessed. The present observation is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Its governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The narrower applicable remedy is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.

C:

Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. This action was designed for the separate Unknown unicast flooding behavior case, not the live production incident being assessed. The present observation is: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. Its governing mechanism is: Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. The narrower applicable remedy is: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.

Question 22

During production incident triage, engineers observe: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
  2. Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
  3. Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
  4. Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

Explanation

Correct Answer

C:

Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. In the live production incident, the reported evidence is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. The intervention follows the governing fact that OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. Closure requires the corresponding specific confirmation: The OSPFv3 neighbor reaches the expected state and learned IPv6 prefixes appear in inet6.0.

Incorrect Answers

A:

Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. This action was designed for the separate IPv6 over IPv4 transit tunnel case, not the live production incident being assessed. The present observation is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Its governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The narrower applicable remedy is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.

B:

Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. This action was designed for the separate ICMPv6 packet-too-big handling case, not the live production incident being assessed. The present observation is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Its governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The narrower applicable remedy is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.

D:

Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. This action was designed for the separate IS-IS IPv6 reachability TLVs case, not the live production incident being assessed. The present observation is: An IPv6 routing interface has global unicast addresses and a healthy OSPFv2 adjacency, yet OSPFv3 neighbor state is absent and no IPv6 routes are learned. Its governing mechanism is: OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. The narrower applicable remedy is: Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.

Question 23

During production incident triage, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
  2. Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
  3. Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
  4. Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.

Explanation

Correct Answer

B:

Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted. In the live production incident, the reported evidence is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The intervention follows the governing fact that Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. Closure requires the corresponding specific confirmation: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.

Incorrect Answers

A:

Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members. This action was designed for the separate MSTP region mismatch case, not the live production incident being assessed. The present observation is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Its governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The narrower applicable remedy is: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.

C:

Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. This action was designed for the separate RSTP alternate port activation case, not the live production incident being assessed. The present observation is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Its governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The narrower applicable remedy is: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.

D:

Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. This action was designed for the separate Unexpected BPDU on edge port case, not the live production incident being assessed. The present observation is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Its governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The narrower applicable remedy is: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.

Question 24

During production incident triage, engineers observe: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.
  2. Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
  3. Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
  4. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

Explanation

Correct Answer

A:

Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling. In the live production incident, the reported evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The intervention follows the governing fact that RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. Closure requires the corresponding specific confirmation: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.

Incorrect Answers

B:

Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. This action was designed for the separate MPLS interface not enabled case, not the live production incident being assessed. The present observation is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Its governing mechanism is: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The narrower applicable remedy is: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.

C:

Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. This action was designed for the separate LDP discovery and IGP mismatch case, not the live production incident being assessed. The present observation is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Its governing mechanism is: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The narrower applicable remedy is: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.

D:

Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the live production incident being assessed. The present observation is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. Its governing mechanism is: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The narrower applicable remedy is: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.

Question 25

During production incident triage, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
  2. Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.
  3. Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
  4. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

Explanation

Correct Answer

A:

Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. In the live production incident, the reported evidence is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. The intervention follows the governing fact that Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. Closure requires the corresponding specific confirmation: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.

Incorrect Answers

B:

Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route. This action was designed for the separate Recursive next-hop resolution case, not the live production incident being assessed. The present observation is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Its governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The narrower applicable remedy is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

C:

Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. This action was designed for the separate Aggregate route contribution case, not the live production incident being assessed. The present observation is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Its governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The narrower applicable remedy is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

D:

Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. This action was designed for the separate Generated default route prerequisite case, not the live production incident being assessed. The present observation is: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. Its governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. The narrower applicable remedy is: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

Question 26

During production incident triage, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
  2. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
  3. Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
  4. Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.

Explanation

Correct Answer

D:

Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution. In the live production incident, the reported evidence is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The intervention follows the governing fact that LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. Closure requires the corresponding specific confirmation: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.

Incorrect Answers

A:

Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. This action was designed for the separate LDP TCP 646 establishment case, not the live production incident being assessed. The present observation is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Its governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The narrower applicable remedy is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.

B:

Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the live production incident being assessed. The present observation is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Its governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The narrower applicable remedy is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.

C:

Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. This action was designed for the separate RSVP link protection plan case, not the live production incident being assessed. The present observation is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Its governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The narrower applicable remedy is: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.

Question 27

During production incident triage, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
  2. Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
  3. Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
  4. Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

Explanation

Correct Answer

D:

Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. In the live production incident, the reported evidence is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The intervention follows the governing fact that For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. Closure requires the corresponding specific confirmation: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.

Incorrect Answers

A:

Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. This action was designed for the separate Aggregate rejection behavior case, not the live production incident being assessed. The present observation is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Its governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The narrower applicable remedy is: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

B:

Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. This action was designed for the separate Equal-cost multipath eligibility case, not the live production incident being assessed. The present observation is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Its governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The narrower applicable remedy is: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

C:

Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. This action was designed for the separate Filter-based forwarding classification case, not the live production incident being assessed. The present observation is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Its governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The narrower applicable remedy is: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

Question 28

During production incident triage, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
  2. Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
  3. Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
  4. Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

Explanation

Correct Answer

C:

Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. In the live production incident, the reported evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The intervention follows the governing fact that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. Closure requires the corresponding specific confirmation: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

Incorrect Answers

A:

Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. This action was designed for the separate Duplicate IS-IS system ID case, not the live production incident being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

B:

Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the live production incident being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

D:

Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the live production incident being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

Question 29

During production incident triage, engineers observe: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
  2. Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity.
  3. Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
  4. Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

Explanation

Correct Answer

C:

Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. In the live production incident, the reported evidence is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. The intervention follows the governing fact that An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. Closure requires the corresponding specific confirmation: An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.

Incorrect Answers

A:

Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. This action was designed for the separate IPv6 static link-local next hop case, not the live production incident being assessed. The present observation is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Its governing mechanism is: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The narrower applicable remedy is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

B:

Enable and validate OSPFv3 link participation and neighbor exchange using the intended IPv6 link-local connectivity. This action was designed for the separate OSPFv3 neighbor uses link-local case, not the live production incident being assessed. The present observation is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Its governing mechanism is: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The narrower applicable remedy is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

D:

Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. This action was designed for the separate IPv6 BGP NLRI family omitted case, not the live production incident being assessed. The present observation is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Its governing mechanism is: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The narrower applicable remedy is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

Question 30

During production incident triage, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
  2. Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
  3. Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
  4. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

Explanation

Correct Answer

A:

Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. In the live production incident, the reported evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The intervention follows the governing fact that LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. Closure requires the corresponding specific confirmation: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.

Incorrect Answers

B:

Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. This action was designed for the separate Missing LDP FEC label mapping case, not the live production incident being assessed. The present observation is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Its governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The narrower applicable remedy is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.

C:

Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. This action was designed for the separate Incoming label missing in LFIB case, not the live production incident being assessed. The present observation is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Its governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The narrower applicable remedy is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.

D:

Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the live production incident being assessed. The present observation is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Its governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The narrower applicable remedy is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.


Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests

Purchase Individually

JN0-364 Premium File

Premium File
JN0-364 Premium File
69 Q&A
$76.99$69.99

Site Search:

 

VISA, MasterCard, AmericanExpress, UnionPay

SPECIAL OFFER: GET 10% OFF

ExamCollection Premium

ExamCollection Premium Files

Pass your Exam with ExamCollection's PREMIUM files!

  • ExamCollection Certified Safe Files
  • Guaranteed to have ACTUAL Exam Questions
  • Up-to-Date Exam Study Material - Verified by Experts
  • Instant Downloads
Enter Your Email Address to Receive Your 10% Off Discount Code
A Confirmation Link will be sent to this email address to verify your login
We value your privacy. We will not rent or sell your email address

SPECIAL OFFER: GET 10% OFF

Use Discount Code:

MIN10OFF

A confirmation link was sent to your e-mail.
Please check your mailbox for a message from support@examcollection.com and follow the directions.

Next

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.