Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

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

Question 760

A support escalation at Eastvale MetroNet describes: An access device bundles ports into one aggregated interface while the remote peer places one port into a different aggregation group. Where should the Junos operator look first for decisive evidence?

  1. Check BFD peer state and negotiated intervals/multipliers, then correlate detection timestamps with routing-neighbor and route changes.
  2. Inspect LACP actor/partner state, physical member association and ae interface operational details on both neighbors.
  3. Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
  4. Inspect VRRP group state, priority, virtual address and advertisements on both routers and measure default-gateway traffic during failover.

Correct answer: B

Explanation of each choice

A.

This check may help with another root cause, for example: A provider wants quicker detection of a path fault when the Ethernet link stays physically Up, but changing application retry timers would not fix routing convergence. It does not test the first failed condition; start with: Inspect LACP actor/partner state, physical member association and ae interface operational details on both neighbors.

B.

Inspect LACP actor/partner state, physical member association and ae interface operational details on both neighbors. A link's physical Up state is not equivalent to synchronized membership in the intended aggregated Ethernet bundle.

C.

The check diagnoses a different layer of service. Its source issue is: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. The relevant initial check is: Inspect LACP actor/partner state, physical member association and ae interface operational details on both neighbors.

D.

This check may help with another root cause, for example: Customer hosts use a shared default gateway IP but lose reachability when the primary router fails because no backup gateway assumes the virtual address. It does not test the first failed condition; start with: Inspect LACP actor/partner state, physical member association and ae interface operational details on both neighbors.

Question 761

During a Junos network change at Ironcrest Payments, the engineer observes: A routing process restarts on one provider router and a neighboring router immediately withdraws otherwise usable forwarding paths despite both supporting graceful restart. Which remediation most directly fixes the described problem?

  1. Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.
  2. Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
  3. Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.
  4. Correct compatible LAG member association and LACP configuration at both ends, then verify active members and per-member forwarding state.

Correct answer: C

Explanation of each choice

A.

That would address a separate configuration fault: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. This stem identifies a different cause, corrected by: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

B.

That would address a separate configuration fault: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. This stem identifies a different cause, corrected by: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

C.

Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart. The case-specific reason is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally. A direct acceptance test is: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

D.

The other action is relevant when An access device bundles ports into one aggregated interface while the remote peer places one port into a different aggregation group. The current case instead requires: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart. The distinction is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

Question 762

The Junos team at Ironcrest Payments needs a success criterion for this defect: A routing process restarts on one provider router and a neighboring router immediately withdraws otherwise usable forwarding paths despite both supporting graceful restart. Which observed result most precisely confirms the intended repair?

  1. Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.
  2. During a controlled master failure, the backup assumes the virtual gateway role and hosts continue to reach the same default-gateway IP through the surviving router.
  3. A simulated forwarding-path loss causes BFD state to fail and the associated routing adjacency or path to react faster than ordinary hold timers.
  4. Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.

Correct answer: A

Explanation of each choice

A.

Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns. GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

B.

That check proves something else, such as: A customer changes its physical router while preserving endpoint configurations; the VRRP backup never becomes master due to incompatible group settings or priorities. It could pass while the stated problem remains. The targeted evidence here is: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

C.

This would be valid for another situation: An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. It does not establish that the failing boundary in this scenario works; verify: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

D.

The observation confirms a different component's behavior. Its source context is: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. In this case the success criterion is: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

Question 763

While analyzing a service failure at Ironcrest Payments, the following is observed: A routing process restarts on one provider router and a neighboring router immediately withdraws otherwise usable forwarding paths despite both supporting graceful restart. Which mechanism best explains the underlying control-plane or forwarding behavior?

  1. Bidirectional Forwarding Detection uses short independent liveness packets to tell a routing protocol when bidirectional forwarding has failed.
  2. GRES preserves interface/kernel forwarding state; NSR additionally preserves routing protocol state on a backup engine and requires GRES. Nonstop bridging (NSB) addresses related Layer 2 bridging state continuity.
  3. Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.
  4. VRRP provides a virtual first-hop gateway with master/backup election, distinct from physical interface IPs or dynamic routing best paths.

Correct answer: C

Explanation of each choice

A.

This explains a separate protocol behavior: An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. In the current facts, the controlling mechanism is: Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.

B.

The statement can be true when A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. But it does not explain the reported failure. Here: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

C.

Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR. The key distinction is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally. Accordingly the remedy is: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

D.

This explains a separate protocol behavior: A customer changes its physical router while preserving endpoint configurations; the VRRP backup never becomes master due to incompatible group settings or priorities. In the current facts, the controlling mechanism is: Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.

Question 764

The following provider defect remains uncorrected at Ironcrest Payments: A routing process restarts on one provider router and a neighboring router immediately withdraws otherwise usable forwarding paths despite both supporting graceful restart. What is the most direct service or security risk of leaving it unresolved?

  1. Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
  2. A silent forwarding fault can blackhole traffic until long routing-protocol timers expire, delaying use of an available backup path.
  3. Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.
  4. An unprotected gateway failure disconnects local subnet clients even when upstream core routes remain available.

Correct answer: C

Explanation of each choice

A.

It is a risk in another topology or protocol state: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. Here the most direct failure path is: Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.

B.

The concern could occur elsewhere when A provider wants quicker detection of a path fault when the Ethernet link stays physically Up, but changing application retry timers would not fix routing convergence. For the stated scenario, the immediate risk is: Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.

C.

Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers. The direct mitigation is: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

D.

It is a risk in another topology or protocol state: A customer changes its physical router while preserving endpoint configurations; the VRRP backup never becomes master due to incompatible group settings or priorities. Here the most direct failure path is: Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.

Question 765

A support escalation at Ironcrest Payments describes: A routing process restarts on one provider router and a neighboring router immediately withdraws otherwise usable forwarding paths despite both supporting graceful restart. Where should the Junos operator look first for decisive evidence?

  1. Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.
  2. Check BFD peer state and negotiated intervals/multipliers, then correlate detection timestamps with routing-neighbor and route changes.
  3. Inspect VRRP group state, priority, virtual address and advertisements on both routers and measure default-gateway traffic during failover.
  4. Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.

Correct answer: A

Explanation of each choice

A.

Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise. GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

B.

This check may help with another root cause, for example: A provider wants quicker detection of a path fault when the Ethernet link stays physically Up, but changing application retry timers would not fix routing convergence. It does not test the first failed condition; start with: Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

C.

That evidence could be normal while the reported defect persists. It is aimed at: Customer hosts use a shared default gateway IP but lose reachability when the primary router fails because no backup gateway assumes the virtual address. Instead inspect: Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

D.

The check diagnoses a different layer of service. Its source issue is: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. The relevant initial check is: Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

Question 766

The provider operations team at Westhaven Software reports: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. Which implementation decision best corrects the cause?

  1. Designate only genuinely host-facing ports as appropriate RSTP edge ports and enable protections against receiving unexpected BPDUs.
  2. Align and validate VRRP group, virtual IP, interface membership and priority/preemption policy on the primary and backup gateways.
  3. Configure supported BFD sessions for the intended routing peers with realistic negotiated detection intervals and validate the resulting routing response.
  4. Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

Correct answer: D

Explanation of each choice

A.

The other action is relevant when A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. The current case instead requires: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart. The distinction is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

B.

The other action is relevant when Customer hosts use a shared default gateway IP but lose reachability when the primary router fails because no backup gateway assumes the virtual address. The current case instead requires: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart. The distinction is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

C.

That would address a separate configuration fault: A provider wants quicker detection of a path fault when the Ethernet link stays physically Up, but changing application retry timers would not fix routing convergence. This stem identifies a different cause, corrected by: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

D.

Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart. The case-specific reason is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally. A direct acceptance test is: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

Question 767

During a post-change check at Westhaven Software, the original condition was: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. What evidence would validate the corrected behavior?

  1. Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
  2. Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.
  3. Both intended links show synchronized collecting/distributing membership and the aggregated interface carries traffic with expected redundancy.
  4. During a controlled master failure, the backup assumes the virtual gateway role and hosts continue to reach the same default-gateway IP through the surviving router.

Correct answer: B

Explanation of each choice

A.

This would be valid for another situation: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. It does not establish that the failing boundary in this scenario works; verify: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

B.

Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns. GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

C.

That check proves something else, such as: An access device bundles ports into one aggregated interface while the remote peer places one port into a different aggregation group. It could pass while the stated problem remains. The targeted evidence here is: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

D.

This would be valid for another situation: Customer hosts use a shared default gateway IP but lose reachability when the primary router fails because no backup gateway assumes the virtual address. It does not establish that the failing boundary in this scenario works; verify: Neighbors temporarily retain permissible stale forwarding routes during the restart window and converge correctly when the control plane returns.

Question 768

At Westhaven Software, an engineer is asked to explain this case: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. Which underlying routing or switching principle accounts for the appropriate solution?

  1. RSTP edge-port treatment shortens convergence for a host attachment but must not be applied to a link that connects another bridge.
  2. Link aggregation presents multiple physical Ethernet members as one logical link when both peers agree on aggregation and LACP state.
  3. Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.
  4. Bidirectional Forwarding Detection uses short independent liveness packets to tell a routing protocol when bidirectional forwarding has failed.

Correct answer: C

Explanation of each choice

A.

This explains a separate protocol behavior: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. In the current facts, the controlling mechanism is: Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.

B.

This explains a separate protocol behavior: A two-link provider uplink is configured as a LAG, but one member is out of synchronization and only a single link forwards. In the current facts, the controlling mechanism is: Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.

C.

Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR. The key distinction is: GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally. Accordingly the remedy is: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

D.

That principle belongs to a different service stage: An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. The directly relevant mechanism is: Graceful restart uses protocol extensions and neighbor cooperation to preserve forwarding during supported control-plane restarts; it is distinct from stateful NSR.

Question 769

A risk assessment at Westhaven Software identifies: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. Which practical consequence is most specifically tied to this failure?

  1. Mislabeling a switch-to-switch link as edge can permit a transient loop, while no edge setting causes avoidable endpoint startup delay.
  2. Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.
  3. An unprotected gateway failure disconnects local subnet clients even when upstream core routes remain available.
  4. Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.

Correct answer: B

Explanation of each choice

A.

It is a risk in another topology or protocol state: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. Here the most direct failure path is: Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.

B.

Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers. The direct mitigation is: Configure compatible supported graceful-restart behavior between routing peers and verify helper participation during a controlled routing-process restart.

C.

The concern could occur elsewhere when A customer changes its physical router while preserving endpoint configurations; the VRRP backup never becomes master due to incompatible group settings or priorities. For the stated scenario, the immediate risk is: Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.

D.

That consequence is more closely associated with another deficiency, such as: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. The described fault instead exposes: Without restart assistance, peers may immediately withdraw routes and cause traffic interruption while the restarting router recovers.

Question 770

The on-call engineer at Westhaven Software receives this fault report: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. What initial check best isolates the actual failing protocol stage?

  1. Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
  2. Inspect LACP actor/partner state, physical member association and ae interface operational details on both neighbors.
  3. Inspect VRRP group state, priority, virtual address and advertisements on both routers and measure default-gateway traffic during failover.
  4. Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

Correct answer: D

Explanation of each choice

A.

That evidence could be normal while the reported defect persists. It is aimed at: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. Instead inspect: Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

B.

The check diagnoses a different layer of service. Its source issue is: A two-link provider uplink is configured as a LAG, but one member is out of synchronization and only a single link forwards. The relevant initial check is: Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

C.

This check may help with another root cause, for example: A customer changes its physical router while preserving endpoint configurations; the VRRP backup never becomes master due to incompatible group settings or priorities. It does not test the first failed condition; start with: Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise.

D.

Inspect negotiated graceful-restart capability and restart/helper state and capture neighbor route behavior during a controlled exercise. GR relies on helper-peer behavior and timers, whereas NSR maintains routing-protocol state on the backup Routing Engine locally.

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

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports