JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
During a Junos network change at Maple Coast Retail, the engineer observes: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. Which remediation most directly fixes the described problem?
That would address a separate configuration fault: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. This stem identifies a different cause, corrected by: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability. The case-specific reason is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting. A direct acceptance test is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
The other action is relevant when A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. The current case instead requires: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability. The distinction is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
That would address a separate configuration fault: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. This stem identifies a different cause, corrected by: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
The Junos team at Maple Coast Retail needs a success criterion for this defect: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. Which observed result most precisely confirms the intended repair?
Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area. The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
This would be valid for another situation: A new higher-priority router joins an IS-IS LAN but the team expects OSPF's DR/BDR rules and cannot explain the pseudonode origin. It does not establish that the failing boundary in this scenario works; verify: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
The observation confirms a different component's behavior. Its source context is: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. In this case the success criterion is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
That check proves something else, such as: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. It could pass while the stated problem remains. The targeted evidence here is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
While analyzing a service failure at Maple Coast Retail, the following is observed: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. Which mechanism best explains the underlying control-plane or forwarding behavior?
The statement can be true when A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. But it does not explain the reported failure. Here: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level. The key distinction is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting. Accordingly the remedy is: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
This explains a separate protocol behavior: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. In the current facts, the controlling mechanism is: IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
The statement can be true when An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. But it does not explain the reported failure. Here: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
The following provider defect remains uncorrected at Maple Coast Retail: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. What is the most direct service or security risk of leaving it unresolved?
The concern could occur elsewhere when A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. For the stated scenario, the immediate risk is: Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured. The direct mitigation is: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
It is a risk in another topology or protocol state: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. Here the most direct failure path is: Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
The concern could occur elsewhere when A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. For the stated scenario, the immediate risk is: Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
A support escalation at Maple Coast Retail describes: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. Where should the Junos operator look first for decisive evidence?
Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence. The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
That evidence could be normal while the reported defect persists. It is aimed at: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. Instead inspect: Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
The check diagnoses a different layer of service. Its source issue is: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. The relevant initial check is: Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
This check may help with another root cause, for example: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. It does not test the first failed condition; start with: Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
The provider operations team at Harborline Transit reports: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. Which implementation decision best corrects the cause?
Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability. The case-specific reason is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting. A direct acceptance test is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
That would address a separate configuration fault: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. This stem identifies a different cause, corrected by: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
This action may apply to a different problem, for example: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. It does not repair the stated failure boundary. The case-specific reason is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
The other action is relevant when A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. The current case instead requires: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability. The distinction is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
During a post-change check at Harborline Transit, the original condition was: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. What evidence would validate the corrected behavior?
The observation confirms a different component's behavior. Its source context is: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. In this case the success criterion is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
That check proves something else, such as: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. It could pass while the stated problem remains. The targeted evidence here is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area. The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
The observation confirms a different component's behavior. Its source context is: A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. In this case the success criterion is: Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
At Harborline Transit, an engineer is asked to explain this case: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. Which underlying routing or switching principle accounts for the appropriate solution?
This explains a separate protocol behavior: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. In the current facts, the controlling mechanism is: IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level. The key distinction is: The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting. Accordingly the remedy is: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
That principle belongs to a different service stage: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. The directly relevant mechanism is: IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
This explains a separate protocol behavior: A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. In the current facts, the controlling mechanism is: IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
A risk assessment at Harborline Transit identifies: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. Which practical consequence is most specifically tied to this failure?
It is a risk in another topology or protocol state: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. Here the most direct failure path is: Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
The concern could occur elsewhere when A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. For the stated scenario, the immediate risk is: Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured. The direct mitigation is: Correct the IS-IS level and area design so Level 1 adjacency occurs only between common-area routers and Level 2 connectivity carries interarea reachability.
It is a risk in another topology or protocol state: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. Here the most direct failure path is: Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
The on-call engineer at Harborline Transit receives this fault report: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. What initial check best isolates the actual failing protocol stage?
The check diagnoses a different layer of service. Its source issue is: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. The relevant initial check is: Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
This check may help with another root cause, for example: A new high-capacity transit link stays unattractive in IS-IS despite the physical upgrade because an oversized intended metric cannot be represented in the current metric style. It does not test the first failed condition; start with: Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
That evidence could be normal while the reported defect persists. It is aimed at: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. Instead inspect: Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence. The key defect is IS-IS level/area design rather than an OSPF ABR or BGP MED setting.
Please check your mailbox for a message from support@examlabs.com and follow the directions.