JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Redleaf Airports describes: 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. Where should the Junos operator look first for decisive evidence?
Verify filter term counters and `then routing-instance`, ingress placement, and a matching route plus resolved next hop in the target table. A filter counter increment does not show that the forwarding lookup moved into the correct table and found a viable route.
The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Verify filter term counters and `then routing-instance`, ingress placement, and a matching route plus resolved next hop in the target table.
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: Verify filter term counters and `then routing-instance`, ingress placement, and a matching route plus resolved next hop in the target table.
That evidence could be normal while the reported defect persists. It is aimed at: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. Instead inspect: Verify filter term counters and `then routing-instance`, ingress placement, and a matching route plus resolved next hop in the target table.
During a Junos network change at Firthbank Medical, the engineer observes: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. Which remediation most directly fixes the described problem?
Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection. The case-specific reason is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route. A direct acceptance test is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
This action may apply to a different problem, for example: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. It does not repair the stated failure boundary. The case-specific reason is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
The other action is relevant 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. The current case instead requires: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection. The distinction is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection.
The Junos team at Firthbank Medical needs a success criterion for this defect: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. Which observed result most precisely confirms the intended repair?
That check proves something else, such as: 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. It could pass while the stated problem remains. The targeted evidence here is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop. Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
The observation confirms a different component's behavior. Its source context is: 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. In this case the success criterion is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
That check proves something else, 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. It could pass while the stated problem remains. The targeted evidence here is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
While analyzing a service failure at Firthbank Medical, the following is observed: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. Which mechanism best explains the underlying control-plane or forwarding behavior?
The statement can be true 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. But it does not explain the reported failure. Here: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
That principle belongs to a different service stage: 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 directly relevant mechanism is: Between competing route sources for an identical destination, Junos normally prefers the route with the lower route-preference value before forwarding installation.
Between competing route sources for an identical destination, Junos normally prefers the route with the lower route-preference value before forwarding installation. The key distinction is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route. Accordingly the remedy is: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection.
The statement can be true 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. But it does not explain the reported failure. Here: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
The following provider defect remains uncorrected at Firthbank Medical: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. What is the most direct service or security risk of leaving it unresolved?
The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance.
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance.
The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance. The direct mitigation is: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection.
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: The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance.
A support escalation at Firthbank Medical describes: A static route and OSPF route cover the identical prefix; the active path is the static one even though the team expected OSPF to win. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: A routing policy change appears to accept a reserved loopback or multicast source as an ordinary Internet destination, and the team needs to separate policy bugs from invalid route treatment. It does not test the first failed condition; start with: Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons.
The check diagnoses a different layer of service. Its source issue is: 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 relevant initial check is: Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons.
Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons. Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
The provider operations team at Cascade Hosting reports: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. Which implementation decision best corrects the cause?
The other action is relevant when 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 current case instead requires: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection. The distinction is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection. The case-specific reason is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route. A direct acceptance test is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
This action may apply to a different problem, for example: 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. It does not repair the stated failure boundary. The case-specific reason is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
The other action is relevant 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. The current case instead requires: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection. The distinction is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
During a post-change check at Cascade Hosting, the original condition was: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. What evidence would validate the corrected behavior?
The observation confirms a different component's behavior. Its source context is: 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 this case the success criterion is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
That check proves something else, such as: 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 could pass while the stated problem remains. The targeted evidence here is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop. Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
The observation confirms a different component's behavior. Its source context is: 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. In this case the success criterion is: The active route for the exact prefix uses the intended source with the expected lower Junos preference and corresponding forwarding next hop.
At Cascade Hosting, an engineer is asked to explain this case: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. Which underlying routing or switching principle accounts for the appropriate solution?
Between competing route sources for an identical destination, Junos normally prefers the route with the lower route-preference value before forwarding installation. The key distinction is: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route. Accordingly the remedy is: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection.
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: Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
That principle belongs to a different service stage: 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 directly relevant mechanism is: Between competing route sources for an identical destination, Junos normally prefers the route with the lower route-preference value before forwarding installation.
This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: Between competing route sources for an identical destination, Junos normally prefers the route with the lower route-preference value before forwarding installation.
A risk assessment at Cascade Hosting identifies: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. Which practical consequence is most specifically tied to this failure?
It is a risk in another topology or protocol state: 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. Here the most direct failure path is: The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance.
The concern could occur elsewhere 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. For the stated scenario, the immediate risk is: The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance.
That consequence is more closely associated with another deficiency, such as: A peer presents a route for an address block treated as martian by the platform; engineers mistakenly troubleshoot export communities rather than the fundamental invalid-prefix classification. The described fault instead exposes: The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance.
The unintended route stays active and can override a healthier dynamic path during failure recovery or maintenance. The direct mitigation is: Review and adjust route preference or remove the unwanted route source, while preserving route reachability and the intended administrative selection.
The on-call engineer at Cascade Hosting receives this fault report: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. What initial check best isolates the actual failing protocol stage?
The check diagnoses a different layer of service. Its source issue is: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. The relevant initial check is: Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons.
Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons. Inter-protocol preference is different from metrics within an IGP; tuning an OSPF interface metric may not defeat a more preferred static route.
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: Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons.
The check diagnoses a different layer of service. Its source issue is: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. The relevant initial check is: Use `show route <prefix> extensive` to compare both candidate route sources, preference values and active/inactive reasons.
Please check your mailbox for a message from support@examlabs.com and follow the directions.