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 14

Question 130

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 underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
  2. RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange.
  3. LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
  4. Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

Explanation

Correct Answer

B:

RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. This principle directly explains the live production incident: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The aligned engineering response is: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling. The result should be established through: The RSVP LSP becomes operational on the authorized explicit route and reports a complete signaled path.

Incorrect Answers

A:

MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. That explanation applies to the different MPLS interface not enabled scenario rather than this live production incident. The current fault evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.

C:

LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. That explanation applies to the different LDP discovery and IGP mismatch scenario rather than this live production incident. The current fault evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.

D:

Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: An RSVP traffic-engineered LSP cannot establish on a required path because its signaled explicit route includes an unavailable transit hop. The controlling mechanism is instead: RSVP-TE can signal explicit constrained LSP paths; missing or disallowed hops prevent a viable PATH and RESV exchange. The correct response would be: Correct the constrained explicit path or restore its required hop and rerun RSVP path signaling.

Question 131

During production incident triage, engineers observe: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
  2. BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
  3. IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
  4. BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

Explanation

Correct Answer

D:

BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. This principle directly explains the live production incident: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The aligned engineering response is: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. The result should be established through: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.

Incorrect Answers

A:

BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. That explanation applies to the different BGP peer autonomous system mismatch scenario rather than this live production incident. The current fault evidence is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The controlling mechanism is instead: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The correct response would be: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

B:

BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. That explanation applies to the different BGP TCP transport blocked scenario rather than this live production incident. The current fault evidence is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The controlling mechanism is instead: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The correct response would be: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

C:

IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. That explanation applies to the different IBGP loopback source resolution scenario rather than this live production incident. The current fault evidence is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The controlling mechanism is instead: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The correct response would be: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

Question 132

During production incident triage, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
  2. BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
  3. BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
  4. An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

Explanation

Correct Answer

A:

When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. This principle directly explains the live production incident: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The aligned engineering response is: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. The result should be established through: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.

Incorrect Answers

B:

BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. That explanation applies to the different BGP peer autonomous system mismatch scenario rather than this live production incident. The current fault evidence is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The controlling mechanism is instead: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The correct response would be: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

C:

BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. That explanation applies to the different BGP TCP transport blocked scenario rather than this live production incident. The current fault evidence is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The controlling mechanism is instead: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The correct response would be: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

D:

An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. That explanation applies to the different EBGP multihop peering scenario rather than this live production incident. The current fault evidence is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The controlling mechanism is instead: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The correct response would be: Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.

Question 133

During production incident triage, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.
  2. ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
  3. Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
  4. Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.

Explanation

Correct Answer

D:

Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. This principle directly explains the live production incident: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The aligned engineering response is: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix. The result should be established through: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.

Incorrect Answers

A:

An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. That explanation applies to the different Aggregate rejection behavior scenario rather than this live production incident. The current fault evidence is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The controlling mechanism is instead: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The correct response would be: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

B:

ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. That explanation applies to the different Equal-cost multipath eligibility scenario rather than this live production incident. The current fault evidence is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The controlling mechanism is instead: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The correct response would be: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

C:

Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. That explanation applies to the different Per-flow hash expectation scenario rather than this live production incident. The current fault evidence is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The controlling mechanism is instead: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The correct response would be: Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.

Question 134

During production incident triage, engineers observe: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
  2. IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
  3. An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
  4. IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

Explanation

Correct Answer

D:

IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. This principle directly explains the live production incident: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The aligned engineering response is: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. The result should be established through: Large IPv6 application transfers succeed and Packet Too Big messages reach the source when necessary.

Incorrect Answers

A:

OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2. That explanation applies to the different OSPFv3 neighbor uses link-local scenario rather than this live production incident. The current fault evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The controlling mechanism is instead: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The correct response would be: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.

B:

IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. That explanation applies to the different IS-IS IPv6 reachability TLVs scenario rather than this live production incident. The current fault evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The controlling mechanism is instead: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The correct response would be: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.

C:

An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. That explanation applies to the different IPv6 over IPv4 transit tunnel scenario rather than this live production incident. The current fault evidence is: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. The controlling mechanism is instead: IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. The correct response would be: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.

Question 135

During production incident triage, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.
  2. BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
  3. Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
  4. BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

Explanation

Correct Answer

B:

BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. This principle directly explains the live production incident: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The aligned engineering response is: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. The result should be established through: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.

Incorrect Answers

A:

IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. That explanation applies to the different IBGP loopback source resolution scenario rather than this live production incident. The current fault evidence is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The controlling mechanism is instead: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The correct response would be: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

C:

Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. That explanation applies to the different BGP local preference egress scenario rather than this live production incident. The current fault evidence is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The controlling mechanism is instead: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The correct response would be: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

D:

BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. That explanation applies to the different BGP MED comparison scope scenario rather than this live production incident. The current fault evidence is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The controlling mechanism is instead: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The correct response would be: Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.

Question 136

During production incident triage, engineers observe: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags.
  2. An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.
  3. A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic.
  4. Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.

Explanation

Correct Answer

A:

Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. This principle directly explains the live production incident: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The aligned engineering response is: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff. The result should be established through: Captured handoff frames carry the agreed outer tag and correct inner VLAN values and pass only the authorized service.

Incorrect Answers

B:

An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. That explanation applies to the different IRB routed gateway missing scenario rather than this live production incident. The current fault evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The controlling mechanism is instead: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The correct response would be: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

C:

A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. That explanation applies to the different Unknown unicast flooding behavior scenario rather than this live production incident. The current fault evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The controlling mechanism is instead: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The correct response would be: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

D:

Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. That explanation applies to the different Virtual switch instance membership scenario rather than this live production incident. The current fault evidence is: A wholesale provider transports several customer VLANs inside service VLAN 600, but the far end expects outer tag 601 and drops the frames. The controlling mechanism is instead: Provider bridging adds an outer service tag so multiple customer VLANs can traverse a shared carrier domain while retaining their inner tags. The correct response would be: Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.

Question 137

During production incident triage, engineers observe: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
  2. ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds.
  3. Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
  4. Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.

Explanation

Correct Answer

B:

ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. This principle directly explains the live production incident: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The aligned engineering response is: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. The result should be established through: The forwarding table shows both expected next hops and representative flows use the authorized paths without loop or asymmetry problems.

Incorrect Answers

A:

For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. That explanation applies to the different Administrative preference overrides static scenario rather than this live production incident. The current fault evidence is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The controlling mechanism is instead: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The correct response would be: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

C:

Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. That explanation applies to the different Martian-address acceptance scenario rather than this live production incident. The current fault evidence is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The controlling mechanism is instead: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The correct response would be: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

D:

Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. That explanation applies to the different RIB group forwarding copy scenario rather than this live production incident. The current fault evidence is: PE-19 has two links of nominally equal bandwidth, but only one next hop is installed because routing metrics and multipath settings do not yield eligible equal-cost paths. The controlling mechanism is instead: ECMP depends on eligible equal-cost forwarding choices, not merely matching physical-interface speeds. The correct response would be: Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.

Question 138

During production incident triage, engineers observe: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.
  2. An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
  3. IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.
  4. BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

Explanation

Correct Answer

D:

BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. This principle directly explains the live production incident: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The aligned engineering response is: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. The result should be established through: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.

Incorrect Answers

A:

IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. That explanation applies to the different IS-IS IPv6 reachability TLVs scenario rather than this live production incident. The current fault evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The controlling mechanism is instead: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The correct response would be: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

B:

An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. That explanation applies to the different IPv6 over IPv4 transit tunnel scenario rather than this live production incident. The current fault evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The controlling mechanism is instead: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The correct response would be: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

C:

IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. That explanation applies to the different ICMPv6 packet-too-big handling scenario rather than this live production incident. The current fault evidence is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The controlling mechanism is instead: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The correct response would be: Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.

Question 139

During production incident triage, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
  2. Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.
  3. OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.
  4. OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.

Explanation

Correct Answer

A:

OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. This principle directly explains the live production incident: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The aligned engineering response is: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. The result should be established through: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.

Incorrect Answers

B:

Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. That explanation applies to the different OSPF passive interface scenario rather than this live production incident. The current fault evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The controlling mechanism is instead: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The correct response would be: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

C:

OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations. That explanation applies to the different Stub area external LSA expectation scenario rather than this live production incident. The current fault evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The controlling mechanism is instead: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The correct response would be: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

D:

OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. That explanation applies to the different OSPF metric path preference scenario rather than this live production incident. The current fault evidence is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The controlling mechanism is instead: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The correct response would be: Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.

Question 140

During production incident triage, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
  2. LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC.
  3. RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.
  4. Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

Explanation

Correct Answer

C:

RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. This principle directly explains the live production incident: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The aligned engineering response is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. The result should be established through: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.

Incorrect Answers

A:

MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. That explanation applies to the different MPLS interface not enabled scenario rather than this live production incident. The current fault evidence is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

B:

LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. That explanation applies to the different Missing LDP FEC label mapping scenario rather than this live production incident. The current fault evidence is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

D:

Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. That explanation applies to the different Penultimate hop popping scenario rather than this live production incident. The current fault evidence is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The controlling mechanism is instead: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The correct response would be: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.


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.