JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
Before changing configuration at Canal City University, an engineer investigates: 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. Which first diagnostic most directly tests the suspected cause?
Inspect contributor activity, the generate configuration and generated default in the RIB while deliberately withdrawing and restoring the qualifying contributor. Generated route activation is conditional on route contribution; merely raising an OSPF interface metric does not enforce the required default-route condition.
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 contributor activity, the generate configuration and generated default in the RIB while deliberately withdrawing and restoring the qualifying contributor.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect contributor activity, the generate configuration and generated default in the RIB while deliberately withdrawing and restoring the qualifying contributor.
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: Inspect contributor activity, the generate configuration and generated default in the RIB while deliberately withdrawing and restoring the qualifying contributor.
At Bridgeway Cloud, a service provider router shows this failure: 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. What is the best targeted configuration or operations action?
Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix. The case-specific reason is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric. A direct acceptance test is: The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
The other action is relevant when An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. The current case instead requires: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix. The distinction is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix.
This action may apply to a different problem, for example: 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. It does not repair the stated failure boundary. The case-specific reason is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
A change auditor at Bridgeway Cloud must validate remediation of this finding: 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. Which test outcome is the strongest acceptance evidence?
This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space. Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
That check proves something else, 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. It could pass while the stated problem remains. The targeted evidence here is: The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
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 route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
The operations training team at Bridgeway Cloud discusses this issue: 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. Which technical explanation matches the intended correction?
Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences. The key distinction is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric. Accordingly the remedy is: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix.
This explains a separate protocol behavior: 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. In the current facts, the controlling mechanism is: Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences.
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: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
That principle belongs to a different service stage: 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. The directly relevant mechanism is: Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences.
At Bridgeway Cloud, a service acceptance review considers the unresolved issue: 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. Which operational exposure follows most directly?
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: Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
It is a risk in another topology or protocol state: 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. Here the most direct failure path is: Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review. The direct mitigation is: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix.
That consequence is more closely associated with another deficiency, such as: An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. The described fault instead exposes: Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
Before changing configuration at Bridgeway Cloud, an engineer investigates: 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. Which first diagnostic most directly tests the suspected cause?
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.
The check diagnoses a different layer of service. Its source issue is: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. The relevant initial check is: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.
This check may help with another root cause, for example: 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 test the first failed condition; start with: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.
Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy. Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
During a Junos network change at Crestpoint Research, the engineer observes: 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. Which remediation most directly fixes the described problem?
Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix. The case-specific reason is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric. A direct acceptance test is: The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
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: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix. The distinction is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
That would address a separate configuration fault: A packet class identified by source address needs to use a dedicated service routing table, but packets still follow the global destination-based path. This stem identifies a different cause, corrected by: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix.
The Junos team at Crestpoint Research needs a success criterion for this defect: 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. Which observed result most precisely confirms the intended repair?
That check proves something else, such as: Two route sources advertise an identical subnet; engineers compare IGP metric values while ignoring Junos inter-protocol preference. It could pass while the stated problem remains. The targeted evidence here is: The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space. Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
The observation confirms a different component's behavior. Its source context is: 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. In this case the success criterion is: The route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
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 route is treated according to the documented martian policy, and normal unicast routing is not unintentionally established for reserved or prohibited address space.
While analyzing a service failure at Crestpoint Research, the following is observed: 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. Which mechanism best explains the underlying control-plane or forwarding behavior?
The statement can be true when 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. But it does not explain the reported failure. Here: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
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: Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences.
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: Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences.
Martian addresses are prefixes considered invalid for ordinary routing and can be rejected independently of normal policy attribute preferences. The key distinction is: Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric. Accordingly the remedy is: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix.
The following provider defect remains uncorrected at Crestpoint Research: 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. What is the most direct service or security risk of leaving it unresolved?
The concern could occur elsewhere when An operations runbook treats discard and reject forwarding actions as interchangeable and fails to explain the expected behavior for unmatched packets. For the stated scenario, the immediate risk is: Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
That consequence is more closely associated with another deficiency, 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. The described fault instead exposes: Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review. The direct mitigation is: Inspect the Junos martian route configuration and classification and block or deliberately document any exception before accepting the questionable prefix.
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: Invalid or reserved prefixes can pollute routing tables and create unexpected forwarding or route-leak behavior if exceptions are added without review.
A support escalation at Crestpoint Research describes: 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. Where should the Junos operator look first for decisive evidence?
This check may help with another root cause, for example: 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 does not test the first failed condition; start with: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.
The check diagnoses a different layer of service. Its source issue is: 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. The relevant initial check is: Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy.
Check the prefix classification, `show route` reason/state and martian configuration before changing protocol preference or BGP export policy. Martian filtering precedes ordinary best-path preference and cannot be corrected by simply setting a lower route metric.
Please check your mailbox for a message from support@examlabs.com and follow the directions.