JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
The provider operations team at Northshore Utilities reports: 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. Which implementation decision best corrects the cause?
Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations. The case-specific reason is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting. A direct acceptance test is: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
The other action is relevant when 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. The current case instead requires: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations. The distinction is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
During a post-change check at Northshore Utilities, the original condition was: 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. What evidence would validate the corrected behavior?
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: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified. The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
That check proves something else, such as: 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 could pass while the stated problem remains. The targeted evidence here is: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
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: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
At Northshore Utilities, an engineer is asked to explain this case: 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. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. The directly relevant mechanism is: A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics.
This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics.
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: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics. The key distinction is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting. Accordingly the remedy is: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
A risk assessment at Northshore Utilities identifies: 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. Which practical consequence is most specifically tied to this failure?
Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly. The direct mitigation is: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
It is a risk in another topology or protocol state: 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. Here the most direct failure path is: Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
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: Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
That consequence is more closely associated with another deficiency, such as: 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 described fault instead exposes: Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
The on-call engineer at Northshore Utilities receives this fault report: 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. What initial check best isolates the actual failing protocol stage?
Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary. The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
The check diagnoses a different layer of service. Its source issue 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. The relevant initial check is: Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary.
This check may help with another root cause, for example: 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. It does not test the first failed condition; start with: Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary.
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 protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary.
A production change request at Brightwood Public Works includes this finding: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. What should the engineer change to address it?
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations. The case-specific reason is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting. A direct acceptance test is: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
The other action is relevant 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. The current case instead requires: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations. The distinction is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
That would address a separate configuration fault: Traffic to one equal-cost destination uses only a single next hop despite two active parallel paths and an approved traffic-sharing requirement. This stem identifies a different cause, corrected by: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
After Brightwood Public Works applies its proposed fix to this problem — An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. — which observation best proves the specific failure has been resolved?
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: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
This would be valid for another situation: 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. It does not establish that the failing boundary in this scenario works; verify: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
The observation confirms a different component's behavior. Its source context is: 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. In this case the success criterion is: Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified.
Traffic matching real more-specific routes is forwarded normally and packets matching only the protective summary are dropped or rejected as explicitly specified. The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
An architecture review at Brightwood Public Works examines the following symptom: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. What Junos or protocol mechanism is most directly responsible?
The statement can be true 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. But it does not explain the reported failure. Here: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
That principle belongs to a different service stage: 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 directly relevant mechanism is: A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics.
This explains a separate protocol behavior: 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 the current facts, the controlling mechanism is: A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics.
A discard route silently drops packets; a reject route drops them while sending an unreachable response when supported, and longest-prefix matching still favors specifics. The key distinction is: The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting. Accordingly the remedy is: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
The team at Brightwood Public Works defers a fix for this condition: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. What failure is most likely if no targeted control is applied?
The concern could occur elsewhere when 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. For the stated scenario, the immediate risk is: Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly. The direct mitigation is: Select and document the intended discard versus reject next-hop behavior on the protective route, while preserving active more-specific routes for legitimate destinations.
It is a risk in another topology or protocol state: 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. Here the most direct failure path is: Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
The concern could occur elsewhere 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. For the stated scenario, the immediate risk is: Unmatched traffic can loop or provoke inappropriate error traffic if the route's terminal next-hop behavior is not designed explicitly.
During provider troubleshooting at Brightwood Public Works, this symptom is observed: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. Which targeted inspection should precede remediation?
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary.
That evidence could be normal while the reported defect persists. It is aimed at: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. Instead inspect: Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary.
Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary. The problem is terminal forwarding action on an address aggregate, not a BGP path-selection attribute or LAG hashing setting.
This check may help with another root cause, for example: 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. It does not test the first failed condition; start with: Inspect the protective route's next-hop type and run tests for both a known more-specific destination and an unmatched address in the summary.
Please check your mailbox for a message from support@examlabs.com and follow the directions.