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 20

Question 190

During production incident triage, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
  2. A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
  3. NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
  4. VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.

Explanation

Correct Answer

C:

NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. This principle directly explains the live production incident: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The aligned engineering response is: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. The result should be established through: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.

Incorrect Answers

A:

LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. That explanation applies to the different LACP partner mismatch scenario rather than this live production incident. The current fault evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.

B:

A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. That explanation applies to the different LAG member imbalance after failure scenario rather than this live production incident. The current fault evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.

D:

VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. That explanation applies to the different VRRP master priority failover scenario rather than this live production incident. The current fault evidence is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The controlling mechanism is instead: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The correct response would be: Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.

Question 191

During production incident triage, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
  2. VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
  3. A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
  4. BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

Explanation

Correct Answer

B:

VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. This principle directly explains the live production incident: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The aligned engineering response is: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy. The result should be established through: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.

Incorrect Answers

A:

LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. That explanation applies to the different LACP partner mismatch scenario rather than this live production incident. The current fault evidence is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The controlling mechanism is instead: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The correct response would be: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.

C:

A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. That explanation applies to the different LAG member imbalance after failure scenario rather than this live production incident. The current fault evidence is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The controlling mechanism is instead: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The correct response would be: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.

D:

BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. That explanation applies to the different BFD detect timer too aggressive scenario rather than this live production incident. The current fault evidence is: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The controlling mechanism is instead: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The correct response would be: Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.

Question 192

During production incident triage, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
  2. Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
  3. BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.
  4. When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.

Explanation

Correct Answer

B:

Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. This principle directly explains the live production incident: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The aligned engineering response is: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate. The result should be established through: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.

Incorrect Answers

A:

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 router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The controlling mechanism is instead: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The correct response would be: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

C:

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: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The controlling mechanism is instead: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The correct response would be: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

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: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The controlling mechanism is instead: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The correct response would be: Use the designed full-mesh or route-reflector topology and validate route reflection where appropriate.

Question 193

During production incident triage, engineers observe: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
  2. When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
  3. BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
  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

C:

BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. This principle directly explains the live production incident: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The aligned engineering response is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. The result should be established through: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.

Incorrect Answers

A:

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 remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The controlling mechanism is instead: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The correct response would be: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

B:

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: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The controlling mechanism is instead: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The correct response would be: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

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 remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The controlling mechanism is instead: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The correct response would be: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.

Question 194

During production incident triage, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
  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 point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.
  4. OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

Explanation

Correct Answer

A:

Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. This principle directly explains the live production incident: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The aligned engineering response is: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries. The result should be established through: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.

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: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The controlling mechanism is instead: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The correct response would be: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.

C:

OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. That explanation applies to the different Point-to-point OSPF network type scenario rather than this live production incident. The current fault evidence is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The controlling mechanism is instead: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The correct response would be: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.

D:

OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. That explanation applies to the different OSPF authentication key mismatch scenario rather than this live production incident. The current fault evidence is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The controlling mechanism is instead: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The correct response would be: Restore the intended area 0 backbone connectivity for the affected ABRs and verify inter-area summaries.

Question 195

During production incident triage, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. 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. MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
  3. LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
  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:

LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. This principle directly explains the live production incident: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The aligned engineering response is: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. The result should be established through: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.

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: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The controlling mechanism is instead: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The correct response would be: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.

B:

MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. That explanation applies to the different Incoming label missing in LFIB scenario rather than this live production incident. The current fault evidence is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The controlling mechanism is instead: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The correct response would be: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.

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: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The controlling mechanism is instead: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The correct response would be: Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.

Question 196

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

  1. An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
  2. An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct.
  3. OSPFv3 supports IPv6 routing and uses link-local addresses for routine neighbor communication, separate from IPv4 OSPFv2.
  4. BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.

Explanation

Correct Answer

B:

An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. This principle directly explains the live production incident: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. The aligned engineering response is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. The result should be established through: An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.

Incorrect Answers

A:

An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. That explanation applies to the different IPv6 static link-local next hop scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The correct response would be: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

C:

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: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. The controlling mechanism is instead: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The correct response would be: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

D:

BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. That explanation applies to the different IPv6 BGP NLRI family omitted scenario rather than this live production incident. The current fault 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 controlling mechanism is instead: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The correct response would be: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

Question 197

During production incident triage, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. 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 database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full.
  3. Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
  4. OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

Explanation

Correct Answer

B:

OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. This principle directly explains the live production incident: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The aligned engineering response is: Correct the actual transport MTU mismatch across the link, then validate database description exchange. The result should be established through: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.

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: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The controlling mechanism is instead: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The correct response would be: Correct the actual transport MTU mismatch across the link, then validate database description exchange.

C:

Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. That explanation applies to the different OSPF LSDB discrepancy scenario rather than this live production incident. The current fault evidence is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The controlling mechanism is instead: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The correct response would be: Correct the actual transport MTU mismatch across the link, then validate database description exchange.

D:

OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. That explanation applies to the different OSPF authentication key mismatch scenario rather than this live production incident. The current fault evidence is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The controlling mechanism is instead: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The correct response would be: Correct the actual transport MTU mismatch across the link, then validate database description exchange.

Question 198

During production incident triage, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone.
  2. BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
  3. VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
  4. VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic.

Explanation

Correct Answer

B:

BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. This principle directly explains the live production incident: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The aligned engineering response is: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. The result should be established through: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.

Incorrect Answers

A:

LACP selects compatible physical links into a logical aggregate based on partner system and aggregation parameters, not carrier alone. That explanation applies to the different LACP partner mismatch scenario rather than this live production incident. The current fault evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The controlling mechanism is instead: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The correct response would be: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.

C:

VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. That explanation applies to the different VRRP master priority failover scenario rather than this live production incident. The current fault evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The controlling mechanism is instead: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The correct response would be: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.

D:

VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. That explanation applies to the different VRRP preemption oscillation scenario rather than this live production incident. The current fault evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The controlling mechanism is instead: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The correct response would be: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.

Question 199

During production incident triage, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. 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. 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. A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.
  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

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. This principle directly explains the live production incident: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The aligned engineering response is: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. The result should be established through: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.

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: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The controlling mechanism is instead: 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. The correct response would be: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

C:

A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. That explanation applies to the different Aggregate route contribution scenario rather than this live production incident. The current fault evidence is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The controlling mechanism is instead: 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. The correct response would be: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

D:

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: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The controlling mechanism is instead: 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. The correct response would be: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

Question 200

During production incident triage, engineers observe: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. Which underlying Junos routing, switching, or protocol principle best explains this specific observation?

  1. BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.
  2. BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.
  3. An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
  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

B:

BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. This principle directly explains the live production incident: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The aligned engineering response is: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. The result should be established through: The received BGP route resolves its next hop, becomes eligible, and forwards over the designed path.

Incorrect Answers

A:

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 prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The controlling mechanism is instead: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The correct response would be: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

C:

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 prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The controlling mechanism is instead: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The correct response would be: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

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: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. The controlling mechanism is instead: BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. The correct response would be: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.


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.