JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
A support escalation at Ironcrest Payments describes: A policy change accidentally distributes infrastructure static routes into IS-IS and expands the link-state database beyond approved scope. Where should the Junos operator look first for decisive evidence?
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 the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
That evidence could be normal while the reported defect persists. It is aimed at: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Instead inspect: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
The check diagnoses a different layer of service. Its source issue is: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. The relevant initial check is: Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.
Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables. Redistributing a connected or static route is an export-policy decision; a healthy adjacency alone does not originate every RIB entry.
During a Junos network change at Brightwood Public Works, the engineer observes: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. Which remediation most directly fixes the described problem?
That would address a separate configuration fault: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. This stem identifies a different cause, corrected by: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
That would address a separate configuration fault: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. This stem identifies a different cause, corrected by: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
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: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first. The case-specific reason is: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue. A direct acceptance test is: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
The Junos team at Brightwood Public Works needs a success criterion for this defect: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. Which observed result most precisely confirms the intended repair?
The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test. A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
That check proves something else, such as: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. It could pass while the stated problem remains. The targeted evidence here is: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
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: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
The observation confirms a different component's behavior. Its source context is: An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. In this case the success criterion is: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
While analyzing a service failure at Brightwood Public Works, the following is observed: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. Which mechanism best explains the underlying control-plane or forwarding behavior?
This explains a separate protocol behavior: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. In the current facts, the controlling mechanism is: Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
The statement can be true when Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. But it does not explain the reported failure. Here: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
That principle belongs to a different service stage: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. The directly relevant mechanism is: Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation. The key distinction is: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue. Accordingly the remedy is: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
The following provider defect remains uncorrected at Brightwood Public Works: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. What is the most direct service or security risk of leaving it unresolved?
It is a risk in another topology or protocol state: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. Here the most direct failure path is: Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
The concern could occur elsewhere when An access-area router continues to calculate an obsolete SPF route because its LSP sequence version differs from adjacent routers after a change. For the stated scenario, the immediate risk is: Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
That consequence is more closely associated with another deficiency, such as: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. The described fault instead exposes: Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages. The direct mitigation is: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
A support escalation at Brightwood Public Works describes: A remote system appears reachable by IP but intermittent IS-IS adjacency loss correlates with wrong MTU or mismatched circuit configuration. Where should the Junos operator look first for decisive evidence?
The check diagnoses a different layer of service. Its source issue is: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. The relevant initial check is: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
This check may help with another root cause, for example: A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. It does not test the first failed condition; start with: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence. A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
The check diagnoses a different layer of service. Its source issue is: 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. The relevant initial check is: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
The provider operations team at Copperwick Markets reports: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. Which implementation decision best corrects the cause?
Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first. The case-specific reason is: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue. A direct acceptance test is: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
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: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first. The distinction is: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
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: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
During a post-change check at Copperwick Markets, the original condition was: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. What evidence would validate the corrected behavior?
This would be valid for another situation: 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 establish that the failing boundary in this scenario works; verify: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
The observation confirms a different component's behavior. Its source context is: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. In this case the success criterion is: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
That check proves something else, such as: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. It could pass while the stated problem remains. The targeted evidence here is: The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test. A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
At Copperwick Markets, an engineer is asked to explain this case: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. Which underlying routing or switching principle accounts for the appropriate solution?
That principle belongs to a different service stage: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The directly relevant mechanism is: Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
This explains a separate protocol behavior: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. In the current facts, the controlling mechanism is: Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation. The key distinction is: A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue. Accordingly the remedy is: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
That principle belongs to a different service stage: 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. The directly relevant mechanism is: Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
A risk assessment at Copperwick Markets identifies: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. Which practical consequence is most specifically tied to this failure?
Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages. The direct mitigation is: Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
It is a risk in another topology or protocol state: 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. Here the most direct failure path is: Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
The concern could occur elsewhere when An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. For the stated scenario, the immediate risk is: Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
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: Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
The on-call engineer at Copperwick Markets receives this fault report: A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. What initial check best isolates the actual failing protocol stage?
Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence. A staged diagnostic distinguishes neighbor establishment, LSP flooding and SPF instead of treating every IS-IS reachability loss as a metric issue.
The check diagnoses a different layer of service. Its source issue is: Two core routers join different IS-IS areas but are expected to exchange Level 1 routes directly as if they share an area identifier. The relevant initial check is: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
This check may help with another root cause, for example: 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 test the first failed condition; start with: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
That evidence could be normal while the reported defect persists. It is aimed at: A Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. Instead inspect: Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
Please check your mailbox for a message from support@examlabs.com and follow the directions.