JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
During a Junos network change at Oakbend Education, the engineer observes: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. Which remediation most directly fixes the described problem?
This action may apply to a different problem, for example: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. It does not repair the stated failure boundary. The case-specific reason is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
The other action is relevant when A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. The current case instead requires: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding. The distinction is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
That would address a separate configuration fault: A provider intends a protective summary for address space with sparse more-specific destinations but needs unmatched traffic to be dropped predictably rather than looped. This stem identifies a different cause, corrected by: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding. The case-specific reason is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure. A direct acceptance test is: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
The Junos team at Oakbend Education needs a success criterion for this defect: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. Which observed result most precisely confirms the intended repair?
This would be valid for another situation: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. It does not establish that the failing boundary in this scenario works; verify: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
The observation confirms a different component's behavior. Its source context is: An enterprise receives a transit path that should trigger a conditional route of last resort; when that contributor disappears the default must be removed to avoid a blackhole. In this case the success criterion is: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path. This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
This would be valid for another situation: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. It does not establish that the failing boundary in this scenario works; verify: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
While analyzing a service failure at Oakbend Education, the following is observed: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. Which mechanism best explains the underlying control-plane or forwarding behavior?
That principle belongs to a different service stage: An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. The directly relevant mechanism is: A static route remains eligible based on configured next-hop resolution and route preference; dynamic protocols do not automatically repair an incorrectly pinned route.
A static route remains eligible based on configured next-hop resolution and route preference; dynamic protocols do not automatically repair an incorrectly pinned route. The key distinction is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure. Accordingly the remedy is: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
The statement can be true when An edge advertises dozens of customer-specific routes instead of the intended summary, and the operations team wants to reduce external route-table size without creating an unsupported more-specific next hop. But it does not explain the reported failure. Here: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
That principle belongs to a different service stage: A provider's firewall filter counts customer steering matches yet tagged traffic goes to the ordinary next hop because the `then routing-instance` forwarding path was not verified. The directly relevant mechanism is: A static route remains eligible based on configured next-hop resolution and route preference; dynamic protocols do not automatically repair an incorrectly pinned route.
The following provider defect remains uncorrected at Oakbend Education: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. What is the most direct service or security risk of leaving it unresolved?
That consequence is more closely associated with another deficiency, such as: A provider intends a protective summary for address space with sparse more-specific destinations but needs unmatched traffic to be dropped predictably rather than looped. The described fault instead exposes: Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.
Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path. The direct mitigation is: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
The concern could occur elsewhere when A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. For the stated scenario, the immediate risk is: Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.
That consequence is more closely associated with another deficiency, such as: A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. The described fault instead exposes: Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.
A support escalation at Oakbend Education describes: A maintenance circuit has been retired but an old static route still directs a private customer prefix toward its unresponsive next hop, even while a learned backup route exists. Where should the Junos operator look first for decisive evidence?
Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology. This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
The check diagnoses a different layer of service. Its source issue is: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. The relevant initial check is: Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.
This check may help with another root cause, for example: A provider intends a protective summary for address space with sparse more-specific destinations but needs unmatched traffic to be dropped predictably rather than looped. It does not test the first failed condition; start with: Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.
That evidence could be normal while the reported defect persists. It is aimed at: A services router has a valid connected path in the primary instance yet a policy-dependent secondary RIB never receives it after a routing-instance refactor. Instead inspect: Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.
The provider operations team at Northline Communications reports: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. Which implementation decision best corrects the cause?
That would address a separate configuration fault: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. This stem identifies a different cause, corrected by: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
This action may apply to a different problem, for example: Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. It does not repair the stated failure boundary. The case-specific reason is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
The other action is relevant when A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. The current case instead requires: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding. The distinction is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding. The case-specific reason is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure. A direct acceptance test is: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
During a post-change check at Northline Communications, the original condition was: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. What evidence would validate the corrected behavior?
That check proves something else, such as: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. It could pass while the stated problem remains. The targeted evidence here is: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
This would be valid for another situation: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. It does not establish that the failing boundary in this scenario works; verify: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
The observation confirms a different component's behavior. Its source context is: A provider migrates a service into a separate virtual routing instance but tests only inet.0 and falsely concludes that the tenant route is absent. In this case the success criterion is: The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path.
The active route and installed forwarding entry for the affected prefix point toward the reachable intended neighbor, and test traffic succeeds over the selected path. This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
At Northline Communications, an engineer is asked to explain this case: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. Which underlying routing or switching principle accounts for the appropriate solution?
The statement can be true when A provider's firewall filter counts customer steering matches yet tagged traffic goes to the ordinary next hop because the `then routing-instance` forwarding path was not verified. But it does not explain the reported failure. Here: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
A static route remains eligible based on configured next-hop resolution and route preference; dynamic protocols do not automatically repair an incorrectly pinned route. The key distinction is: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure. Accordingly the remedy is: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
This explains a separate protocol behavior: A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. In the current facts, the controlling mechanism is: A static route remains eligible based on configured next-hop resolution and route preference; dynamic protocols do not automatically repair an incorrectly pinned route.
The statement can be true when Two wholesale customers use overlapping IPv4 ranges and route lookups occur in the default table, causing one tenant's prefix to shadow the other's. But it does not explain the reported failure. Here: This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
A risk assessment at Northline Communications identifies: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. Which practical consequence is most specifically tied to this failure?
The concern could occur elsewhere when A provider turns on ECMP routing but the forwarding table still resolves customer flows to just one path and operators mistake RIB entries for per-flow distribution. For the stated scenario, the immediate risk is: Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.
That consequence is more closely associated with another deficiency, such as: An edge should install a conditional default only while a qualifying backbone route is reachable, but an unconditional static default currently hides an upstream outage. The described fault instead exposes: Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.
Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path. The direct mitigation is: Update or remove the stale static route and validate the intended reachable next hop and route preference before restoring forwarding.
The concern could occur elsewhere when A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. For the stated scenario, the immediate risk is: Traffic for the specific prefix continues to follow the dead or incorrect next hop instead of recovering through an available alternate path.
The on-call engineer at Northline Communications receives this fault report: A service edge was renumbered and its manually configured static next hop still points to the former address, blackholing one customer subnet despite healthy dynamic adjacencies. What initial check best isolates the actual failing protocol stage?
This check may help with another root cause, for example: A provider aggregate continues to be advertised when an operator assumes that any configured aggregate is independent of contributing routes, and wants to validate how the summary activates. It does not test the first failed condition; start with: Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.
That evidence could be normal while the reported defect persists. It is aimed at: A provider expects selected interface routes from an underlay RIB to be available in a second table, but the secondary table has no copied routes. Instead inspect: Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.
The check diagnoses a different layer of service. Its source issue is: An enterprise receives a transit path that should trigger a conditional route of last resort; when that contributor disappears the default must be removed to avoid a blackhole. The relevant initial check is: Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology.
Inspect the precise prefix in the routing table and the resolved next-hop/forwarding entry, then compare the active static configuration with the working topology. This is a next-hop and preference issue for a manually specified destination, not a missing BGP community or label-signaling failure.
Please check your mailbox for a message from support@examlabs.com and follow the directions.