JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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?
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.
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.
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.
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.
The provider operations team at Cascade Hosting reports: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. Which implementation decision best corrects the cause?
That would address a separate configuration fault: An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. This stem identifies a different cause, corrected by: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
This action may apply to a different problem, for example: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. It does not repair the stated failure boundary. The case-specific reason is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
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: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover. The distinction is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover. The case-specific reason is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR. A direct acceptance test is: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
During a post-change check at Cascade Hosting, the original condition was: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. What evidence would validate the corrected behavior?
This would be valid for another situation: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. It does not establish that the failing boundary in this scenario works; verify: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
This would be valid for another situation: An access device bundles ports into one aggregated interface while the remote peer places one port into a different aggregation group. It does not establish that the failing boundary in this scenario works; verify: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand. Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
That check proves something else, such as: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. It could pass while the stated problem remains. The targeted evidence here is: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
At Cascade Hosting, an engineer is asked to explain this case: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. The directly relevant mechanism is: 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.
That principle belongs to a different service stage: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. The directly relevant mechanism is: 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.
This explains a separate protocol behavior: Customer hosts use a shared default gateway IP but lose reachability when the primary router fails because no backup gateway assumes the virtual address. In the current facts, the controlling mechanism is: 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.
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. The key distinction is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR. Accordingly the remedy is: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
A risk assessment at Cascade Hosting identifies: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. Which practical consequence is most specifically tied to this failure?
The concern could occur elsewhere when An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. For the stated scenario, the immediate risk is: Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
That consequence is more closely associated with another deficiency, such as: An operator mistakes routing-engine switchover forwarding preservation for a guarantee that peers will retain protocol routes through restart. The described fault instead exposes: Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation. The direct mitigation is: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
The concern could occur elsewhere when An access device bundles ports into one aggregated interface while the remote peer places one port into a different aggregation group. For the stated scenario, the immediate risk is: Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
The on-call engineer at Cascade Hosting receives this fault report: A redundant-engine router forwards packets during a switchover but routing protocol sessions still reset because only GRES is configured. What initial check best isolates the actual failing protocol stage?
That evidence could be normal while the reported defect persists. It is aimed at: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. Instead inspect: Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover. Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
A production change request at Brookport Finance includes this finding: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. What should the engineer change to address it?
The other action is relevant when A customer changes its physical router while preserving endpoint configurations; the VRRP backup never becomes master due to incompatible group settings or priorities. The current case instead requires: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover. The distinction is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
That would address a separate configuration fault: A two-link provider uplink is configured as a LAG, but one member is out of synchronization and only a single link forwards. This stem identifies a different cause, corrected by: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover. The case-specific reason is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR. A direct acceptance test is: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
After Brookport Finance applies its proposed fix to this problem — A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. — which observation best proves the specific failure has been resolved?
That check proves something else, such as: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. It could pass while the stated problem remains. The targeted evidence here is: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand. Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
The observation confirms a different component's behavior. Its source context is: An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. In this case the success criterion is: Forwarding and relevant routing adjacencies remain stable under the documented NSR/GRES switchover test, with backup protocol state synchronized beforehand.
An architecture review at Brookport Finance examines the following symptom: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. What Junos or protocol mechanism is most directly responsible?
The statement can be true when A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. But it does not explain the reported failure. Here: Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
The statement can be true when A two-link provider uplink is configured as a LAG, but one member is out of synchronization and only a single link forwards. But it does not explain the reported failure. Here: Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
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. The key distinction is: Preserving the data plane with GRES is not the same as preserving the control plane with NSR. Accordingly the remedy is: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
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: 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.
The team at Brookport Finance defers a fix for this condition: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. What failure is most likely if no targeted control is applied?
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: Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
The concern could occur elsewhere when A two-link provider uplink is configured as a LAG, but one member is out of synchronization and only a single link forwards. For the stated scenario, the immediate risk is: Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation. The direct mitigation is: Enable supported GRES plus nonstop active routing with proper synchronization and validate routing-protocol continuity across a controlled switchover.
It is a risk in another topology or protocol state: An OSPF or BGP route stays installed for too long after an indirect forwarding failure because normal protocol hold timers have not expired. Here the most direct failure path is: Traffic may continue briefly but route adjacencies reset and reconverge if GRES alone is mistaken for full routing-protocol nonstop operation.
During provider troubleshooting at Brookport Finance, this symptom is observed: A provider requires preserved BGP and IGP adjacency state during a Routing Engine failure on supported hardware, not just uninterrupted interfaces. Which targeted inspection should precede remediation?
Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover. Preserving the data plane with GRES is not the same as preserving the control plane with NSR.
That evidence could be normal while the reported defect persists. It is aimed at: A server-only switchport repeatedly transitions through unnecessary topology states when the connected endpoint restarts. Instead inspect: Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
That evidence could be normal while the reported defect persists. It is aimed at: An access device bundles ports into one aggregated interface while the remote peer places one port into a different aggregation group. Instead inspect: Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
The check diagnoses a different layer of service. Its source issue is: A routing process restarts on one provider router and a neighboring router immediately withdraws otherwise usable forwarding paths despite both supporting graceful restart. The relevant initial check is: Inspect chassis redundancy and NSR status, backup routing process synchronization, and neighbor sessions during an approved switchover.
Please check your mailbox for a message from support@examlabs.com and follow the directions.