JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
During provider troubleshooting at Brookport Finance, this symptom is observed: A team is attempting to trace redistributed external routes but checks only router and network LSAs inside the local area. Which targeted inspection should precede remediation?
The check diagnoses a different layer of service. Its source issue is: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. The relevant initial check is: Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy. LSA types carry different topology and reachability semantics; a missing interarea summary is not diagnosed solely from Hello timers.
That evidence could be normal while the reported defect persists. It is aimed at: A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. Instead inspect: Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
The check diagnoses a different layer of service. Its source issue is: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. The relevant initial check is: Inspect LSA type, advertising-router ID and originating role for the missing prefix, plus the area database and redistribution policy.
A production change request at Briarfield Healthcare includes this finding: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. What should the engineer change to address it?
This action may apply to a different problem, for example: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. It does not repair the stated failure boundary. The case-specific reason is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
The other action is relevant when A bandwidth upgrade does not change OSPF path selection because configured interface costs still favor the legacy circuit. The current case instead requires: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source. The distinction is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source. The case-specific reason is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency. A direct acceptance test is: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
This action may apply to a different problem, for example: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. It does not repair the stated failure boundary. The case-specific reason is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
After Briarfield Healthcare applies its proposed fix to this problem — An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. — which observation best proves the specific failure has been resolved?
Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB. Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
The observation confirms a different component's behavior. Its source context is: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. In this case the success criterion is: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
That check proves something else, such as: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. It could pass while the stated problem remains. The targeted evidence here is: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
This would be valid for another situation: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. It does not establish that the failing boundary in this scenario works; verify: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
An architecture review at Briarfield Healthcare examines the following symptom: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. What Junos or protocol mechanism is most directly responsible?
That principle belongs to a different service stage: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. The directly relevant mechanism is: Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery. The key distinction is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency. Accordingly the remedy is: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
The statement can be true when A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. But it does not explain the reported failure. Here: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
That principle belongs to a different service stage: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. The directly relevant mechanism is: Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
The team at Briarfield Healthcare defers a fix for this condition: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. What failure is most likely if no targeted control is applied?
It is a risk in another topology or protocol state: A dual-homed router has inconsistent OSPF identity following a replacement Routing Engine, with LSDB conflicts despite working interface IP addresses. Here the most direct failure path is: An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
It is a risk in another topology or protocol state: A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. Here the most direct failure path is: An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
The concern could occur elsewhere when Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. For the stated scenario, the immediate risk is: An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability. The direct mitigation is: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
During provider troubleshooting at Briarfield Healthcare, this symptom is observed: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. Which targeted inspection should precede remediation?
That evidence could be normal while the reported defect persists. It is aimed at: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. Instead inspect: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
The check diagnoses a different layer of service. Its source issue is: A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. The relevant initial check is: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
This check may help with another root cause, for example: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. It does not test the first failed condition; start with: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs. Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
At Cloverbank Mobile, a service provider router shows this failure: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. What is the best targeted configuration or operations action?
Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source. The case-specific reason is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency. A direct acceptance test is: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
This action may apply to a different problem, for example: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. It does not repair the stated failure boundary. The case-specific reason is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
The other action is relevant when An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. The current case instead requires: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source. The distinction is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
That would address a separate configuration fault: An area has stable OSPF neighbors but one router computes an unexpected path because its LSDB is missing a current advertisement. This stem identifies a different cause, corrected by: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
A change auditor at Cloverbank Mobile must validate remediation of this finding: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. Which test outcome is the strongest acceptance evidence?
That check proves something else, such as: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. It could pass while the stated problem remains. The targeted evidence here is: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
This would be valid for another situation: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. It does not establish that the failing boundary in this scenario works; verify: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB. Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
That check proves something else, such as: On a broadcast multiaccess segment, engineers expect every pair of routers to form Full adjacencies and incorrectly diagnose normal two-way states. It could pass while the stated problem remains. The targeted evidence here is: Approved external prefixes are originated with the correct external attributes and prohibited ones are absent from the neighbor LSDB.
The operations training team at Cloverbank Mobile discusses this issue: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. Which technical explanation matches the intended correction?
Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery. The key distinction is: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency. Accordingly the remedy is: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
That principle belongs to a different service stage: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. The directly relevant mechanism is: Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
This explains a separate protocol behavior: An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. In the current facts, the controlling mechanism is: Junos OSPF routing policy controls external-route origination/redistribution; it does not replace normal OSPF link-state interface discovery.
The statement can be true when An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. But it does not explain the reported failure. Here: Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
At Cloverbank Mobile, a service acceptance review considers the unresolved issue: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. Which operational exposure follows most directly?
The concern could occur elsewhere when An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. For the stated scenario, the immediate risk is: An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
That consequence is more closely associated with another deficiency, such as: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. The described fault instead exposes: An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
It is a risk in another topology or protocol state: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. Here the most direct failure path is: An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability.
An overly broad export rule can leak internal routes, while a missing accept term can withhold legitimate external reachability. The direct mitigation is: Tighten and validate the Junos OSPF export policy for the exact allowed and denied prefixes and the intended redistribution source.
Before changing configuration at Cloverbank Mobile, an engineer investigates: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. Which first diagnostic most directly tests the suspected cause?
Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs. Redistribution is controlled by export policy and valid source routes, not by changing the cost of an unrelated existing OSPF adjacency.
That evidence could be normal while the reported defect persists. It is aimed at: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. Instead inspect: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
The check diagnoses a different layer of service. Its source issue is: A team is attempting to trace redistributed external routes but checks only router and network LSAs inside the local area. The relevant initial check is: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
This check may help with another root cause, for example: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. It does not test the first failed condition; start with: Check source-route activity, ordered OSPF export policy terms, and whether the ASBR originates the expected external LSAs.
Please check your mailbox for a message from support@examlabs.com and follow the directions.