JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Stonebridge Hospitality describes: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. Where should the Junos operator look first for decisive evidence?
The check diagnoses a different layer of service. Its source issue is: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The relevant initial check is: Inspect the LSP contents and specific reachability TLV type and value at the correct level rather than relying only on generic neighbor status.
Inspect the LSP contents and specific reachability TLV type and value at the correct level rather than relying only on generic neighbor status. A TLV inside an LSP conveys link-state attributes; it is not interchangeable with an IIH PDU's neighbor-discovery role.
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: Inspect the LSP contents and specific reachability TLV type and value at the correct level rather than relying only on generic neighbor status.
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: Inspect the LSP contents and specific reachability TLV type and value at the correct level rather than relying only on generic neighbor status.
During a Junos network change at Keystone Industrial, the engineer observes: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Which remediation most directly fixes the described problem?
Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment. The case-specific reason is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers. A direct acceptance test is: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
The other action is relevant when An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. The current case instead requires: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment. The distinction is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
That would address a separate configuration fault: 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. This stem identifies a different cause, corrected by: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment.
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: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
The Junos team at Keystone Industrial needs a success criterion for this defect: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Which observed result most precisely confirms the intended repair?
The observation confirms a different component's behavior. Its source context is: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. In this case the success criterion is: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly. IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
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: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
This would be valid for another situation: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. It does not establish that the failing boundary in this scenario works; verify: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
While analyzing a service failure at Keystone Industrial, the following is observed: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Which mechanism best explains the underlying control-plane or forwarding behavior?
The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair. The key distinction is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers. Accordingly the remedy is: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment.
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: The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair.
The statement can be true when A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. But it does not explain the reported failure. Here: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
That principle belongs to a different service stage: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. The directly relevant mechanism is: The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair.
The following provider defect remains uncorrected at Keystone Industrial: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. What is the most direct service or security risk of leaving it unresolved?
Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency. The direct mitigation is: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment.
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: Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
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: Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
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: Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
A support escalation at Keystone Industrial describes: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Where should the Junos operator look first for decisive evidence?
That evidence could be normal while the reported defect persists. It is aimed at: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. Instead inspect: Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level. IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
This check may help with another root cause, for example: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. It does not test the first failed condition; start with: Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
That evidence could be normal while the reported defect persists. It is aimed at: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. Instead inspect: Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
The provider operations team at Summit Logistics reports: 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. Which implementation decision best corrects the cause?
That would address a separate configuration fault: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. This stem identifies a different cause, corrected by: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment.
This action may apply to a different problem, for example: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. It does not repair the stated failure boundary. The case-specific reason is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
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: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment. The distinction is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment. The case-specific reason is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers. A direct acceptance test is: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
During a post-change check at Summit Logistics, the original condition was: 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. What evidence would validate the corrected behavior?
That check proves something else, such as: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. It could pass while the stated problem remains. The targeted evidence here is: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly. IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
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: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
That check proves something else, such as: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. It could pass while the stated problem remains. The targeted evidence here is: One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
At Summit Logistics, an engineer is asked to explain this case: 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. Which underlying routing or switching principle accounts for the appropriate solution?
The statement can be true when An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. But it does not explain the reported failure. Here: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
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: The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair.
The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair. The key distinction is: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers. Accordingly the remedy is: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment.
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: IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
A risk assessment at Summit Logistics identifies: 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. Which practical consequence is most specifically tied to this failure?
The concern could occur elsewhere when A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. For the stated scenario, the immediate risk is: Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
That consequence is more closely associated with another deficiency, such as: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. The described fault instead exposes: Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency. The direct mitigation is: Check IS-IS LAN priority/system identifiers and verify the correct DIS and pseudonode LSP behavior on that shared segment.
The concern could occur elsewhere when A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. For the stated scenario, the immediate risk is: Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
The on-call engineer at Summit Logistics receives this fault report: 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. What initial check best isolates the actual failing protocol stage?
This check may help with another root cause, for example: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. It does not test the first failed condition; start with: Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level. IS-IS DIS election and pseudonode behavior differ from OSPF's separate designated and backup routers.
The check diagnoses a different layer of service. Its source issue is: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The relevant initial check is: Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
This check may help with another root cause, for example: A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. It does not test the first failed condition; start with: Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
Please check your mailbox for a message from support@examlabs.com and follow the directions.