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 16

Question 150

During production incident triage, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.
  2. Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
  3. Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.
  4. A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.

Explanation

Correct Answer

D:

A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. This principle directly explains the live production incident: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The aligned engineering response is: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. The result should be established through: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.

Incorrect Answers

A:

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-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.

B:

Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. That explanation applies to the different Filter-based forwarding classification scenario rather than this live production incident. The current fault evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.

C:

Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. That explanation applies to the different Filter policy overmatch scenario rather than this live production incident. The current fault evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The controlling mechanism is instead: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The correct response would be: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.

Question 151

During production incident triage, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.
  2. OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
  3. OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship.
  4. OSPF stub areas intentionally restrict external LSAs and normally rely on appropriate default reachability from an ABR for external destinations.

Explanation

Correct Answer

A:

External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. This principle directly explains the live production incident: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The aligned engineering response is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. The result should be established through: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.

Incorrect Answers

B:

OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. That explanation applies to the different OSPF hello dead timer mismatch scenario rather than this live production incident. The current fault evidence is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The controlling mechanism is instead: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The correct response would be: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

C:

OSPF neighbors must agree on their area identification over a shared adjacency; incompatible area values prevent a valid neighbor relationship. That explanation applies to the different OSPF area ID mismatch scenario rather than this live production incident. The current fault evidence is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The controlling mechanism is instead: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The correct response would be: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

D:

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 PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The controlling mechanism is instead: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The correct response would be: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

Question 152

During production incident triage, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration.
  2. IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
  3. Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
  4. The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Explanation

Correct Answer

C:

Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. This principle directly explains the live production incident: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The aligned engineering response is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. The result should be established through: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.

Incorrect Answers

A:

Junos IS-IS uses ISO CLNS signaling on participating interfaces, which requires appropriate family iso configuration. That explanation applies to the different IS-IS ISO family missing scenario rather than this live production incident. The current fault evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The controlling mechanism is instead: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The correct response would be: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

B:

IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The controlling mechanism is instead: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The correct response would be: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

D:

The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this live production incident. The current fault evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The controlling mechanism is instead: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The correct response would be: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.

Question 153

During production incident triage, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. 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. OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.
  3. OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
  4. External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

Explanation

Correct Answer

C:

OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. This principle directly explains the live production incident: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The aligned engineering response is: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. The result should be established through: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.

Incorrect Answers

A:

OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. That explanation applies to the different OSPF hello dead timer mismatch scenario rather than this live production incident. The current fault evidence is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The controlling mechanism is instead: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The correct response would be: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.

B:

OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. That explanation applies to the different DR priority zero misconception scenario rather than this live production incident. The current fault evidence is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The controlling mechanism is instead: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The correct response would be: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.

D:

External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. That explanation applies to the different OSPF export policy omission scenario rather than this live production incident. The current fault evidence is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The controlling mechanism is instead: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The correct response would be: Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.

Question 154

During production incident triage, engineers observe: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
  2. Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
  3. RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails.
  4. Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address.

Explanation

Correct Answer

D:

Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. This principle directly explains the live production incident: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The aligned engineering response is: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy. The result should be established through: The intended core device is reported as root and a designated backup root is stable after an election test.

Incorrect Answers

A:

Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. That explanation applies to the different Unexpected BPDU on edge port scenario rather than this live production incident. The current fault evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The controlling mechanism is instead: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The correct response would be: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

B:

Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. That explanation applies to the different Loop protection after BPDU loss scenario rather than this live production incident. The current fault evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The controlling mechanism is instead: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The correct response would be: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

C:

RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. That explanation applies to the different RSTP alternate port activation scenario rather than this live production incident. The current fault evidence is: After a provider switch reboot, the wrong access switch becomes the STP root because its bridge identifier is lower than the intended core root's ID. The controlling mechanism is instead: Spanning-tree root election chooses the lowest bridge ID, which includes configured priority and MAC address. The correct response would be: Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.

Question 155

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

  1. IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
  2. IS-IS relies on a unique system ID to identify LSP originators and topology nodes.
  3. IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.
  4. The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Explanation

Correct Answer

A:

IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. This principle directly explains the live production incident: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The aligned engineering response is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. The result should be established through: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.

Incorrect Answers

B:

IS-IS relies on a unique system ID to identify LSP originators and topology nodes. That explanation applies to the different Duplicate IS-IS system ID scenario rather than this live production incident. The current fault evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The controlling mechanism is instead: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The correct response would be: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

C:

IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. That explanation applies to the different IS-IS narrow metric ceiling scenario rather than this live production incident. The current fault evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The controlling mechanism is instead: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The correct response would be: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

D:

The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. That explanation applies to the different IS-IS DIS election surprise scenario rather than this live production incident. The current fault evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The controlling mechanism is instead: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The correct response would be: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.

Question 156

During production incident triage, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
  2. BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.
  3. Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
  4. When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.

Explanation

Correct Answer

B:

BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. This principle directly explains the live production incident: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The aligned engineering response is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. The result should be established through: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.

Incorrect Answers

A:

BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. That explanation applies to the different BGP next-hop inaccessible scenario rather than this live production incident. The current fault evidence is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The controlling mechanism is instead: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The correct response would be: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.

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: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The controlling mechanism is instead: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The correct response would be: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.

D:

When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. That explanation applies to the different BGP AS-path comparison scenario rather than this live production incident. The current fault evidence is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The controlling mechanism is instead: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The correct response would be: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.

Question 157

During production incident triage, engineers observe: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.
  2. An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up.
  3. IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
  4. Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.

Explanation

Correct Answer

B:

An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. This principle directly explains the live production incident: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The aligned engineering response is: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. The result should be established through: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.

Incorrect Answers

A:

When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. That explanation applies to the different IS-IS authentication mismatch scenario rather than this live production incident. The current fault evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The controlling mechanism is instead: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The correct response would be: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.

C:

IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. That explanation applies to the different IS-IS route export scope scenario rather than this live production incident. The current fault evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The controlling mechanism is instead: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The correct response would be: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.

D:

Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. That explanation applies to the different IS-IS Level 1 exit default scenario rather than this live production incident. The current fault evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The controlling mechanism is instead: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The correct response would be: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.

Question 158

During production incident triage, engineers observe: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
  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 admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
  4. RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

Explanation

Correct Answer

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. This principle directly explains the live production incident: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The aligned engineering response is: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. The result should be established through: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.

Incorrect Answers

A:

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 LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The controlling mechanism is instead: 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. The correct response would be: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.

C:

RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. That explanation applies to the different RSVP reservable bandwidth shortage scenario rather than this live production incident. The current fault evidence is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The controlling mechanism is instead: 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. The correct response would be: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.

D:

RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. That explanation applies to the different RSVP link protection plan scenario rather than this live production incident. The current fault evidence is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The controlling mechanism is instead: 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. The correct response would be: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.

Question 159

During production incident triage, engineers observe: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.
  2. BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
  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

C:

IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. This principle directly explains the live production incident: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The aligned engineering response is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design. The result should be established through: The session establishes using the intended loopback source and destination and stays up after a physical link fails.

Incorrect Answers

A:

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: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The controlling mechanism is instead: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The correct response would be: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.

B:

BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. That explanation applies to the different BGP export policy omission scenario rather than this live production incident. The current fault evidence is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The controlling mechanism is instead: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The correct response would be: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.

D:

BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. That explanation applies to the different BGP import policy leak scenario rather than this live production incident. The current fault evidence is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The controlling mechanism is instead: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The correct response would be: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.

Question 160

During production incident triage, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.
  2. GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
  3. GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
  4. GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel.

Explanation

Correct Answer

C:

GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. This principle directly explains the live production incident: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The aligned engineering response is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. The result should be established through: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.

Incorrect Answers

A:

GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. That explanation applies to the different GRE confidentiality misconception scenario rather than this live production incident. The current fault evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

B:

GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. That explanation applies to the different GRE encapsulation MTU overhead scenario rather than this live production incident. The current fault evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

D:

GRE encapsulation uses configured outer source and destination IP addresses, which must align with the underlay endpoints of the intended tunnel. That explanation applies to the different GRE tunnel endpoint mismatch scenario rather than this live production incident. The current fault evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The controlling mechanism is instead: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The correct response would be: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.


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.