McAfee Secured

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

100% Juniper JN0-364 Guaranteed Success With Testking Training Materials

Get Real JN0-364 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

69 Questions & Answers with Testing Engine

"Service Provider Routing and Switching, Specialist (JNCIS-SP) Exam", also known as JN0-364 exam, is a Juniper certification exam.

Pass your tests with the always up-to-date JN0-364 Exam Engine. Your JN0-364 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 97

Question 960

In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 240, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: Traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. What is the direct residual network risk if the fault remains unresolved?

  1. A nominally redundant network fails its practical customer continuity requirement.
  2. A supervisor failure forces routing protocol reconvergence and drops customer traffic.
  3. Half the expected capacity is unavailable and link failover is fragile.
  4. Control-plane churn follows repeated elections among unsuitable devices.

Explanation

Correct Answer

B:

A supervisor failure forces routing protocol reconvergence and drops customer traffic. Enable and verify supported nonstop active routing with required redundancy prerequisites. NSR maintains routing protocol information on the backup Routing Engine beyond basic GRES forwarding preservation.

Incorrect Answers

A:

A nominally redundant network fails its practical customer continuity requirement. The choice would be appropriate if an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover. Here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

C:

Half the expected capacity is unavailable and link failover is fragile. It addresses a different problem: A bundled uplink has two configured members but only one is usable because the second member's operational parameters differ. Here, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

D:

Control-plane churn follows repeated elections among unsuitable devices. This could matter when an unplanned access router becomes designated router after its interface receives an unexpectedly high priority. In this case, traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state.

Question 961

At fictional Lakewood Carrier 241, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. Which targeted remediation best fits the reported behavior?

  1. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.
  2. Run a controlled member failure test and verify surviving-link service forwarding.
  3. Enable and verify supported nonstop active routing with required redundancy prerequisites.
  4. Restore the intended LSP or safe route resolution and verify the forwarding next hop.

Explanation

Correct Answer

A:

Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval.

Incorrect Answers

B:

Run a controlled member failure test and verify surviving-link service forwarding. The choice would be appropriate if a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Here, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

Enable and verify supported nonstop active routing with required redundancy prerequisites. That option concerns traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. The problem here is different: A provider assumes graceful restart will work during a routing process restart without considering neighbor support.

D:

Restore the intended LSP or safe route resolution and verify the forwarding next hop. It addresses a different problem: A service path references an LSP that is down, but its IP route remains visible in the route table. Here, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 962

At fictional Lakewood Carrier 241, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. Why is this particular correction the best fit for the stated defect?

  1. High availability must be evaluated by usable service forwarding as well as control-plane states.
  2. NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover.
  3. BGP route limits help contain unexpected prefix-volume changes from a neighbor.
  4. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.

Explanation

Correct Answer

D:

Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval.

Incorrect Answers

A:

High availability must be evaluated by usable service forwarding as well as control-plane states. That relates to circumstances in which an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover. Here the problem is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

B:

NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover. This addresses a situation in which a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets; however, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

BGP route limits help contain unexpected prefix-volume changes from a neighbor. The choice would be appropriate if a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale. Here, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 963

At fictional Lakewood Carrier 241, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. What direct observation would prove the corrective action worked?

  1. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval.
  2. Loss of one link leaves the logical bundle up and service traffic continues on the other.
  3. A controlled path failure produces the designed BFD event and route withdrawal within target bounds.
  4. The remote LSDB includes the fresh LSP and the loopback route becomes active.

Explanation

Correct Answer

A:

Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.

Incorrect Answers

B:

Loss of one link leaves the logical bundle up and service traffic continues on the other. That relates to circumstances in which a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. Here the problem is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

A controlled path failure produces the designed BFD event and route withdrawal within target bounds. This addresses a situation in which a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; however, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

D:

The remote LSDB includes the fresh LSP and the loopback route becomes active. The choice would be appropriate if a remote PE misses a new loopback route because IS-IS link-state flooding is incomplete after an adjacency reset. Here, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 964

At fictional Lakewood Carrier 241, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. Which failure consequence follows most closely from ignoring this issue?

  1. Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery.
  2. Customers experience extended blackholes before alternate paths take over.
  3. Subscribers suffer flooding or Layer 2 interruption after a supervisor failure.
  4. MPLS traffic cannot use the planned engineered transport path.

Explanation

Correct Answer

A:

Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.

Incorrect Answers

B:

Customers experience extended blackholes before alternate paths take over. It is useful for situations where a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; the reported fault, though, is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

Subscribers suffer flooding or Layer 2 interruption after a supervisor failure. That relates to circumstances in which a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. Here the problem is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

D:

MPLS traffic cannot use the planned engineered transport path. This addresses a situation in which an RSVP LSP stays down but engineers only examine the ingress router's IP default route; however, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 965

In a separate fictional JNCIS-SP lab review for Summitfield Carrier 242, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. What intervention most directly restores the intended routing or switching behavior?

  1. Align supported member configuration and verify aggregation state and distributed traffic.
  2. Configure and validate supported GRES readiness before an authorized controlled failover.
  3. Set deliberate interface priorities and confirm the DR and BDR roles after a controlled election.
  4. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.

Explanation

Correct Answer

D:

Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.

Incorrect Answers

A:

Align supported member configuration and verify aggregation state and distributed traffic. This could help if a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ, but not when a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

B:

Configure and validate supported GRES readiness before an authorized controlled failover. This relates to a case where a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared; the current situation is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

Set deliberate interface priorities and confirm the DR and BDR roles after a controlled election. It is useful for situations where an unplanned access router becomes designated router after its interface receives an unexpectedly high priority; the reported fault, though, is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 966

In a separate fictional JNCIS-SP lab review for Summitfield Carrier 242, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. Which networking principle explains why the proposed correction is appropriate?

  1. A link aggregation group forwards correctly only over members meeting the operational bundle requirements.
  2. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.
  3. BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers.
  4. Unexpected MAC movement often points to changing Layer 2 forwarding topology.

Explanation

Correct Answer

B:

Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.

Incorrect Answers

A:

A link aggregation group forwards correctly only over members meeting the operational bundle requirements. It is relevant if a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ, but the reported issue is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers. This relates to a case where a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; the current situation is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

D:

Unexpected MAC movement often points to changing Layer 2 forwarding topology. It is useful for situations where a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; the reported fault, though, is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 967

In a separate fictional JNCIS-SP lab review for Summitfield Carrier 242, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. Which validation result would confirm the design is now functioning?

  1. Loss of one link leaves the logical bundle up and service traffic continues on the other.
  2. Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval.
  3. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover.
  4. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup.

Explanation

Correct Answer

B:

Peers retain valid routes during a tested restart and withdraw stale state after the appropriate interval. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.

Incorrect Answers

A:

Loss of one link leaves the logical bundle up and service traffic continues on the other. This is applicable when a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails; the present condition is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. This could help if traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state, but not when a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

D:

Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. This relates to a case where a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; the current situation is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 968

In a separate fictional JNCIS-SP lab review for Summitfield Carrier 242, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider assumes graceful restart will work during a routing process restart without considering neighbor support. What likely service impact does this condition create?

  1. A single gateway device fault disconnects all hosts on the VLAN.
  2. Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery.
  3. A nominally redundant network fails its practical customer continuity requirement.
  4. Unnecessary filtering interrupts normal bridged service.

Explanation

Correct Answer

B:

Traffic is blackholed because neighbors keep invalid routes or fail to assist recovery. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.

Incorrect Answers

A:

A single gateway device fault disconnects all hosts on the VLAN. That could help when an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; here, a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

C:

A nominally redundant network fails its practical customer continuity requirement. It is relevant if an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover, but the reported issue is that a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

D:

Unnecessary filtering interrupts normal bridged service. This could help if a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop, but not when a provider assumes graceful restart will work during a routing process restart without considering neighbor support.

Question 969

At fictional Brightstone Backbone 243, a regional service-provider network, during a two-site transit migration, operations observes: A switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. Which configuration or operational correction most directly addresses this failure?

  1. Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery.
  2. Configure supported BFD monitoring with the neighbor protocol and validate failure detection behavior.
  3. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership.
  4. Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains.

Explanation

Correct Answer

D:

Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains. NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover. MAC tables and customer bridge forwarding remain stable during controlled switchover.

Incorrect Answers

A:

Confirm the configured graceful-restart and helper capabilities on participating peers before testing recovery. This could matter when a provider assumes graceful restart will work during a routing process restart without considering neighbor support. In this case, a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets.

B:

Configure supported BFD monitoring with the neighbor protocol and validate failure detection behavior. That could help when a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; here, a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets.

C:

Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. This is applicable when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services; the present condition is that a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets.

Question 970

At fictional Brightstone Backbone 243, a regional service-provider network, during a two-site transit migration, operations observes: A switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. Which Junos forwarding or control-plane rule applies to this case?

  1. NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover.
  2. VRRP provides a shared virtual gateway address with an active router and standby candidates.
  3. Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery.
  4. IPv4 and IPv6 route lookups use separate address-family tables.

Explanation

Correct Answer

A:

NSB is intended to maintain relevant Layer 2 control-plane continuity through supported failover. Verify nonstop bridging and platform-specific switchover readiness for the intended bridge domains. MAC tables and customer bridge forwarding remain stable during controlled switchover.

Incorrect Answers

B:

VRRP provides a shared virtual gateway address with an active router and standby candidates. This could matter when an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect. In this case, a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets.

C:

Graceful restart relies on appropriate protocol and neighbor support to retain forwarding through control-plane recovery. That could help when a provider assumes graceful restart will work during a routing process restart without considering neighbor support; here, a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets.

D:

IPv4 and IPv6 route lookups use separate address-family tables. This is applicable when a support engineer runs an IPv4 route lookup for an IPv6 destination and concludes the destination is not advertised; the present condition is that a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets.

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