JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
At Northline Communications, a service provider router shows this failure: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. What is the best targeted configuration or operations action?
The other action is relevant when After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. The current case instead requires: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
That would address a separate configuration fault: A newly attached router with high priority fails to preempt an existing designated router, and the design team assumes priority alone forces immediate re-election. This stem identifies a different cause, corrected by: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The case-specific reason is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. A direct acceptance test is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
The other action is relevant when An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. The current case instead requires: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
A change auditor at Northline Communications must validate remediation of this finding: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which test outcome is the strongest acceptance evidence?
The observation confirms a different component's behavior. Its source context is: A neighbor reaches ExStart and repeatedly restarts database exchange because control-plane packet handling differs across the two ends. In this case the success criterion is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
That check proves something else, such as: A redistribution policy suppresses one approved connected network, while operators attempt to fix the route with interface metric changes. It could pass while the stated problem remains. The targeted evidence here is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
This would be valid for another situation: After adding a second OSPF area, a service prefix appears on the wrong area-facing interface and downstream reachability is intermittent. It does not establish that the failing boundary in this scenario works; verify: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
The operations training team at Northline Communications discusses this issue: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which technical explanation matches the intended correction?
This explains a separate protocol behavior: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. In the current facts, the controlling mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery. The key distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. Accordingly the remedy is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
That principle belongs to a different service stage: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. The directly relevant mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
This explains a separate protocol behavior: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. In the current facts, the controlling mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
At Northline Communications, a service acceptance review considers the unresolved issue: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which operational exposure follows most directly?
It is a risk in another topology or protocol state: Two routers share an Ethernet segment and can exchange pings but never form an OSPF adjacency; their configured Hello/dead timers differ. Here the most direct failure path is: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
The concern could occur elsewhere when A topology change appears on one router's LSDB but not another's despite successful neighbor Hellos and identical advertised areas. For the stated scenario, the immediate risk is: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
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: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity. The direct mitigation is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
Before changing configuration at Northline Communications, an engineer investigates: A point-to-point OSPF link remains in ExStart after a transport migration changed the effective interface MTU, while IPv4 pings still succeed. Which first diagnostic most directly tests the suspected cause?
This check may help with another root cause, for example: An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. It does not test the first failed condition; start with: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
This check may help with another root cause, for example: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. It does not test the first failed condition; start with: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
That evidence could be normal while the reported defect persists. It is aimed at: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. Instead inspect: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
During a Junos network change at Briarfield Healthcare, the engineer observes: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Which remediation most directly fixes the described problem?
Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The case-specific reason is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. A direct acceptance test is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
The other action is relevant when An area has stable OSPF neighbors but one router computes an unexpected path because its LSDB is missing a current advertisement. The current case instead requires: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent. The distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
That would address a separate configuration fault: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. This stem identifies a different cause, corrected by: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
This action may apply to a different problem, for example: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. It does not repair the stated failure boundary. The case-specific reason is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
The Junos team at Briarfield Healthcare needs a success criterion for this defect: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Which observed result most precisely confirms the intended repair?
This would be valid for another situation: An interface moved to a new routing zone still participates in its former OSPF area despite updated IP addressing. It does not establish that the failing boundary in this scenario works; verify: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
The observation confirms a different component's behavior. Its source context is: An OSPF router unexpectedly uses a duplicate Router ID after a staged configuration copy and one neighbor refuses to establish correct database synchronization. In this case the success criterion is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
That check proves something else, such as: A team is attempting to trace redistributed external routes but checks only router and network LSAs inside the local area. It could pass while the stated problem remains. The targeted evidence here is: The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information.
The peers pass database-description exchange without MTU-related resets, reach Full and exchange the expected LSDB information. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
While analyzing a service failure at Briarfield Healthcare, the following is observed: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Which mechanism best explains the underlying control-plane or forwarding behavior?
That principle belongs to a different service stage: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. The directly relevant mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
This explains a separate protocol behavior: An OSPF edge imports an unintended static customer route as an external advertisement after a broad export-policy change. In the current facts, the controlling mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery. The key distinction is: An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect. Accordingly the remedy is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
That principle belongs to a different service stage: An area has stable OSPF neighbors but one router computes an unexpected path because its LSDB is missing a current advertisement. The directly relevant mechanism is: OSPF database description negotiation uses interface MTU information, and a mismatch can stall adjacency even after Hello-based discovery.
The following provider defect remains uncorrected at Briarfield Healthcare: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. What is the most direct service or security risk of leaving it unresolved?
That consequence is more closely associated with another deficiency, such as: An operator sees Hello packets and assumes OSPF LSAs have been synchronized; database-description and request traffic never completes. The described fault instead exposes: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity. The direct mitigation is: Identify and correct the actual MTU or adjacency negotiation mismatch on the participating interfaces while keeping necessary link encapsulation consistent.
The concern could occur elsewhere when A newly attached router with high priority fails to preempt an existing designated router, and the design team assumes priority alone forces immediate re-election. For the stated scenario, the immediate risk is: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
That consequence is more closely associated with another deficiency, such as: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. The described fault instead exposes: Routing state may fail to synchronize across the link, leaving expected prefixes unreachable despite basic link-level connectivity.
A support escalation at Briarfield Healthcare describes: A new OSPF neighbor oscillates between Exchange and ExStart when a carrier's encapsulation overhead makes the two ends advertise different allowable packet sizes. Where should the Junos operator look first for decisive evidence?
Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes. An ExStart/Exchange failure with asymmetric MTU is a database negotiation problem, not a route export policy or DR election defect.
The check diagnoses a different layer of service. Its source issue is: A downstream area does not learn an interarea network after an ABR policy change, and staff mistake network LSAs for summary propagation. The relevant initial check is: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
This check may help with another root cause, for example: An OSPF peer alternates between down and init after an interface migration while packet captures reveal Hello parameters inconsistent on the two ends. It does not test the first failed condition; start with: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
That evidence could be normal while the reported defect persists. It is aimed at: Traffic prefers a slow OSPF path despite a faster link because manual interface costs reverse the intended SPF ranking. Instead inspect: Inspect neighbor states, DD packet MTU fields and both logical/physical interface MTU settings before trying authentication or policy changes.
Please check your mailbox for a message from support@examlabs.com and follow the directions.