JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
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.
The provider operations team at Atlas Port Services reports: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. Which implementation decision best corrects the cause?
This action may apply to a different problem, for example: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. It does not repair the stated failure boundary. The case-specific reason is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
The other action is relevant when A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. The current case instead requires: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends. The distinction is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
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: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends. The case-specific reason is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate. A direct acceptance test is: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
During a post-change check at Atlas Port Services, the original condition was: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. What evidence would validate the corrected behavior?
IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability. A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
That check proves something else, such as: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. It could pass while the stated problem remains. The targeted evidence here is: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
That check proves something else, such as: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. It could pass while the stated problem remains. The targeted evidence here is: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
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: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
At Atlas Port Services, an engineer is asked to explain this case: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. The directly relevant mechanism is: IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone.
This explains a separate protocol behavior: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. In the current facts, the controlling mechanism is: IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone.
The statement can be true when A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. But it does not explain the reported failure. Here: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone. The key distinction is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate. Accordingly the remedy is: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
A risk assessment at Atlas Port Services identifies: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. Which practical consequence is most specifically tied to this failure?
That consequence is more closely associated with another deficiency, such as: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. The described fault instead exposes: Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes. The direct mitigation is: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
The concern could occur elsewhere when A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. For the stated scenario, the immediate risk is: Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
That consequence is more closely associated with another deficiency, such as: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. The described fault instead exposes: Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
The on-call engineer at Atlas Port Services receives this fault report: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. What initial check best isolates the actual failing protocol stage?
That evidence could be normal while the reported defect persists. It is aimed at: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. Instead inspect: Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
The check diagnoses a different layer of service. Its source issue is: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. The relevant initial check is: Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement. A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
That evidence could be normal while the reported defect persists. It is aimed at: 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. Instead inspect: Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
A production change request at Clearwater Analytics includes this finding: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. What should the engineer change to address it?
That would address a separate configuration fault: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. This stem identifies a different cause, corrected by: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
This action may apply to a different problem, for example: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. It does not repair the stated failure boundary. The case-specific reason is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends. The case-specific reason is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate. A direct acceptance test is: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
That would address a separate configuration fault: A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. This stem identifies a different cause, corrected by: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
After Clearwater Analytics applies its proposed fix to this problem — Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. — which observation best proves the specific failure has been resolved?
IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability. A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
This would be valid for another situation: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. It does not establish that the failing boundary in this scenario works; verify: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
The observation confirms a different component's behavior. Its source context is: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. In this case the success criterion is: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
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: IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
An architecture review at Clearwater Analytics examines the following symptom: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. What Junos or protocol mechanism is most directly responsible?
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: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
That principle belongs to a different service stage: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. The directly relevant mechanism is: IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone.
IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone. The key distinction is: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate. Accordingly the remedy is: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
The statement can be true when A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. But it does not explain the reported failure. Here: A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
The team at Clearwater Analytics defers a fix for this condition: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. What failure is most likely if no targeted control is applied?
The concern could occur elsewhere when A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. For the stated scenario, the immediate risk is: Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
That consequence is more closely associated with another deficiency, such as: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. The described fault instead exposes: Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
It is a risk in another topology or protocol state: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. Here the most direct failure path is: Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes. The direct mitigation is: Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
During provider troubleshooting at Clearwater Analytics, this symptom is observed: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. Which targeted inspection should precede remediation?
This check may help with another root cause, for example: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. It does not test the first failed condition; start with: Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement. A functioning IP interface does not establish IS-IS neighbor compatibility; IIH acceptance is the first control-plane gate.
The check diagnoses a different layer of service. Its source issue is: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. The relevant initial check is: Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
This check may help with another root cause, for example: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. It does not test the first failed condition; start with: Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
Please check your mailbox for a message from support@examlabs.com and follow the directions.