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 42

Question 410

During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit next-hop reachability and route-active state after every underlay change.
  2. Review route-preference conventions for static backups during routing-policy audits.
  3. Review generated-route contributors and policy conditions whenever edge reachability changes.
  4. Test covered and uncovered address samples as part of aggregate change validation.

Explanation

Correct Answer

D:

Test covered and uncovered address samples as part of aggregate change validation. The current live production incident demonstrates why this check matters: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. It monitors the mechanism that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The continuing safeguard should be correlated with the specific acceptance test: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.

Incorrect Answers

A:

Audit next-hop reachability and route-active state after every underlay change. This control addresses the distinct Recursive next-hop resolution operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

B:

Review route-preference conventions for static backups during routing-policy audits. This control addresses the distinct Administrative preference overrides static operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

C:

Review generated-route contributors and policy conditions whenever edge reachability changes. This control addresses the distinct Generated default route prerequisite operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

Question 411

During production incident triage, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review passive-interface policy whenever a customer-facing segment is added.
  2. Baseline OSPF timer settings per transport class and alert on configuration drift.
  3. Document broadcast-segment DR priorities and rehearse controlled elections.
  4. Alert on repeated OSPF adjacency resets and divergent LSA conditions.

Explanation

Correct Answer

A:

Review passive-interface policy whenever a customer-facing segment is added. The current live production incident demonstrates why this check matters: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. It monitors the mechanism that Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The continuing safeguard should be correlated with the specific acceptance test: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.

Incorrect Answers

B:

Baseline OSPF timer settings per transport class and alert on configuration drift. This control addresses the distinct OSPF hello dead timer mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The directly relevant continuing check is: Review passive-interface policy whenever a customer-facing segment is added. The governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

C:

Document broadcast-segment DR priorities and rehearse controlled elections. This control addresses the distinct DR priority zero misconception operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The directly relevant continuing check is: Review passive-interface policy whenever a customer-facing segment is added. The governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

D:

Alert on repeated OSPF adjacency resets and divergent LSA conditions. This control addresses the distinct OSPF LSDB discrepancy operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The directly relevant continuing check is: Review passive-interface policy whenever a customer-facing segment is added. The governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

Question 412

During production incident triage, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Monitor aggregate active state and contributor counts before each upstream announcement change.
  2. Review generated-route contributors and policy conditions whenever edge reachability changes.
  3. Test covered and uncovered address samples as part of aggregate change validation.
  4. Exercise backup-path liveness detection under downstream and local failure scenarios.

Explanation

Correct Answer

D:

Exercise backup-path liveness detection under downstream and local failure scenarios. The current live production incident demonstrates why this check matters: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. It monitors the mechanism that A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The continuing safeguard should be correlated with the specific acceptance test: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.

Incorrect Answers

A:

Monitor aggregate active state and contributor counts before each upstream announcement change. This control addresses the distinct Aggregate route contribution operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The directly relevant continuing check is: Exercise backup-path liveness detection under downstream and local failure scenarios. The governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.

B:

Review generated-route contributors and policy conditions whenever edge reachability changes. This control addresses the distinct Generated default route prerequisite operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The directly relevant continuing check is: Exercise backup-path liveness detection under downstream and local failure scenarios. The governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.

C:

Test covered and uncovered address samples as part of aggregate change validation. This control addresses the distinct Aggregate rejection behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The directly relevant continuing check is: Exercise backup-path liveness detection under downstream and local failure scenarios. The governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary.

Question 413

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit local-preference policy for consistency across ingress points.
  2. Include AS-path comparisons in periodic interdomain routing audit reports.
  3. Record negotiated BGP timers and correlate flap events with packet-loss telemetry.
  4. Document intended MED comparison scope and test different-neighbor-AS cases.

Explanation

Correct Answer

C:

Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism that BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The continuing safeguard should be correlated with the specific acceptance test: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.

Incorrect Answers

A:

Audit local-preference policy for consistency across ingress points. This control addresses the distinct BGP local preference egress operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.

B:

Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.

D:

Document intended MED comparison scope and test different-neighbor-AS cases. This control addresses the distinct BGP MED comparison scope operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.

Question 414

During production incident triage, engineers observe: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit LACP partner identity and collecting/distributing state during bundle maintenance.
  2. Track graceful-restart capabilities and maintenance test outcomes for every relevant peer.
  3. Monitor member count, error rate and utilization separately from AE state.
  4. Validate planned VRRP priorities and failover behavior after router maintenance.

Explanation

Correct Answer

B:

Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The current live production incident demonstrates why this check matters: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. It monitors the mechanism that Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior. The continuing safeguard should be correlated with the specific acceptance test: Peer capability and restart-state logs show the intended graceful behavior, and routes remain valid during the controlled test.

Incorrect Answers

A:

Audit LACP partner identity and collecting/distributing state during bundle maintenance. This control addresses the distinct LACP partner mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The directly relevant continuing check is: Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.

C:

Monitor member count, error rate and utilization separately from AE state. This control addresses the distinct LAG member imbalance after failure operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The directly relevant continuing check is: Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.

D:

Validate planned VRRP priorities and failover behavior after router maintenance. This control addresses the distinct VRRP master priority failover operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A router attempts graceful routing restart but downstream peers remove its routes immediately because helper behavior is not available or the restart contract is unmet. The directly relevant continuing check is: Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. The governing mechanism is: Graceful restart can temporarily preserve forwarding across a routing process restart when peers honor the protocol's restart assistance behavior.

Question 415

During production incident triage, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Check MPLS interface participation during each core link turn-up.
  2. Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
  3. Check LDP session transport filtering as part of control-plane ACL reviews.
  4. Sample FEC label bindings and forwarding resolution after prefix or IGP changes.

Explanation

Correct Answer

B:

Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The current live production incident demonstrates why this check matters: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. It monitors the mechanism that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The continuing safeguard should be correlated with the specific acceptance test: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.

Incorrect Answers

A:

Check MPLS interface participation during each core link turn-up. This control addresses the distinct MPLS interface not enabled operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

C:

Check LDP session transport filtering as part of control-plane ACL reviews. This control addresses the distinct LDP TCP 646 establishment operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

D:

Sample FEC label bindings and forwarding resolution after prefix or IGP changes. This control addresses the distinct Missing LDP FEC label mapping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

Question 416

During production incident triage, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Audit next-hop reachability and route-active state after every underlay change.
  2. Test covered and uncovered address samples as part of aggregate change validation.
  3. Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
  4. Check classifier counters, filter attachment and target-table availability after changes.

Explanation

Correct Answer

A:

Audit next-hop reachability and route-active state after every underlay change. The current live production incident demonstrates why this check matters: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. It monitors the mechanism that A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. The continuing safeguard should be correlated with the specific acceptance test: The static prefix becomes active with a resolved next hop, and a sourced packet test reaches the destination through the intended interface.

Incorrect Answers

B:

Test covered and uncovered address samples as part of aggregate change validation. This control addresses the distinct Aggregate rejection behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The directly relevant continuing check is: Audit next-hop reachability and route-active state after every underlay change. The governing mechanism is: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

C:

Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. This control addresses the distinct Per-flow hash expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The directly relevant continuing check is: Audit next-hop reachability and route-active state after every underlay change. The governing mechanism is: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

D:

Check classifier counters, filter attachment and target-table availability after changes. This control addresses the distinct Filter-based forwarding classification operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. The directly relevant continuing check is: Audit next-hop reachability and route-active state after every underlay change. The governing mechanism is: A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

Question 417

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Check BGP negotiated families and IPv6 route policy during dual-stack migrations.
  2. Monitor unresolved BGP next hops separately from session establishment.
  3. Audit local-preference policy for consistency across ingress points.
  4. Include AS-path comparisons in periodic interdomain routing audit reports.

Explanation

Correct Answer

A:

Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism that BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The continuing safeguard should be correlated with the specific acceptance test: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.

Incorrect Answers

B:

Monitor unresolved BGP next hops separately from session establishment. This control addresses the distinct BGP next-hop inaccessible operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.

C:

Audit local-preference policy for consistency across ingress points. This control addresses the distinct BGP local preference egress operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.

D:

Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Check BGP negotiated families and IPv6 route policy during dual-stack migrations. The governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.

Question 418

During production incident triage, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
  2. Exercise backup-path liveness detection under downstream and local failure scenarios.
  3. Compare RIB candidate routes with FIB entries in routing acceptance tests.
  4. Review route-preference conventions for static backups during routing-policy audits.

Explanation

Correct Answer

C:

Compare RIB candidate routes with FIB entries in routing acceptance tests. The current live production incident demonstrates why this check matters: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. It monitors the mechanism that Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The continuing safeguard should be correlated with the specific acceptance test: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.

Incorrect Answers

A:

Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. This control addresses the distinct Per-flow hash expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The directly relevant continuing check is: Compare RIB candidate routes with FIB entries in routing acceptance tests. The governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

B:

Exercise backup-path liveness detection under downstream and local failure scenarios. This control addresses the distinct Static backup blackhole operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The directly relevant continuing check is: Compare RIB candidate routes with FIB entries in routing acceptance tests. The governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

D:

Review route-preference conventions for static backups during routing-policy audits. This control addresses the distinct Administrative preference overrides static operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The directly relevant continuing check is: Compare RIB candidate routes with FIB entries in routing acceptance tests. The governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

Question 419

During production incident triage, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Monitor unresolved BGP next hops separately from session establishment.
  2. Include AS-path comparisons in periodic interdomain routing audit reports.
  3. Document intended MED comparison scope and test different-neighbor-AS cases.
  4. Document peer distance, TTL, and authorized transport path for remote eBGP sessions.

Explanation

Correct Answer

D:

Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The current live production incident demonstrates why this check matters: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. It monitors the mechanism that An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The continuing safeguard should be correlated with the specific acceptance test: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.

Incorrect Answers

A:

Monitor unresolved BGP next hops separately from session establishment. This control addresses the distinct BGP next-hop inaccessible operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The directly relevant continuing check is: Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

B:

Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The directly relevant continuing check is: Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

C:

Document intended MED comparison scope and test different-neighbor-AS cases. This control addresses the distinct BGP MED comparison scope operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The directly relevant continuing check is: Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.

Question 420

During production incident triage, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review link-level capability profiles for L1, L2 and L1/L2 routers.
  2. Include interface family iso in standardized IS-IS provisioning templates.
  3. Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
  4. Record DIS priorities and pseudonode behavior in service-provider switching design reviews.

Explanation

Correct Answer

A:

Review link-level capability profiles for L1, L2 and L1/L2 routers. The current live production incident demonstrates why this check matters: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. It monitors the mechanism that An IS-IS adjacency needs compatible protocol levels as well as link reachability. The continuing safeguard should be correlated with the specific acceptance test: A shared Level 1 or Level 2 adjacency comes up and the right set of level-specific routes is exchanged.

Incorrect Answers

B:

Include interface family iso in standardized IS-IS provisioning templates. This control addresses the distinct IS-IS ISO family missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The directly relevant continuing check is: Review link-level capability profiles for L1, L2 and L1/L2 routers. The governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability.

C:

Baseline metric-style compatibility before area-wide IS-IS cost adjustments. This control addresses the distinct IS-IS narrow metric ceiling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The directly relevant continuing check is: Review link-level capability profiles for L1, L2 and L1/L2 routers. The governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability.

D:

Record DIS priorities and pseudonode behavior in service-provider switching design reviews. This control addresses the distinct IS-IS DIS election surprise operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. The directly relevant continuing check is: Review link-level capability profiles for L1, L2 and L1/L2 routers. The governing mechanism is: An IS-IS adjacency needs compatible protocol levels as well as link reachability.


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.