Pass Juniper JN0-364 Exam in First Attempt Easily
Real Juniper JN0-364 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts

JN0-364 Premium File

  • 69 Questions & Answers
  • Last Update: Nov 4, 2026
$69.99 $76.99

Service Provider Routing and Switching, Specialist (JNCIS-SP) JN0-364 Practice Test 29

Question 280

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?

  1. Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
  2. Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
  3. Inspect the LSP contents and specific reachability TLV type and value at the correct level rather than relying only on generic neighbor status.
  4. Inspect the source route's active state, ordered IS-IS policy terms, and the advertised prefix in local and remote IS-IS tables.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 281

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?

  1. Trace IS-IS LSP flooding and database synchronization at the affected level, correcting the propagation or adjacency gap.
  2. 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.
  3. Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
  4. Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 282

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?

  1. The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.
  2. The expected neighbor or prefix TLV is present in current LSPs with the intended metric representation, and SPF results match.
  3. One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
  4. The relevant LSP identifiers, sequence numbers and contents match among routers at the same level, and SPF reflects the current topology.

Correct answer: A

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 283

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?

  1. IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
  2. IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone.
  3. Junos IS-IS export policy controls origination or redistribution of selected route sources into IS-IS advertisements.
  4. Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 284

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?

  1. Cross-area prefixes can disappear or traffic can follow an unavailable default when L1/L2 boundaries are incorrectly configured.
  2. A stale LSDB can cause transient loops, missing reachability and inconsistent path computation even while some adjacencies remain Up.
  3. Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
  4. Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 285

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?

  1. Compare `show isis database` LSP IDs, sequence values and level-specific flooding status between the affected neighbors.
  2. Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
  3. Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
  4. Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.

Correct answer: C

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 286

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?

  1. Collect adjacency state, protocol trace, interface error/MTU information and LSP database comparisons, then correct the component that fails first.
  2. Implement a narrowly scoped IS-IS interlevel route-leaking policy and validate that selected prefixes are advertised in the intended area and level.
  3. Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
  4. Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

Correct answer: A

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 287

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?

  1. The relevant LSP identifiers, sequence numbers and contents match among routers at the same level, and SPF reflects the current topology.
  2. The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.
  3. Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.
  4. The measured first failing state is corrected and neighbor stability, LSP synchronization and resulting routes recover under a repeatable test.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 288

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?

  1. IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
  2. The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair.
  3. Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
  4. IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently.

Correct answer: C

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 289

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?

  1. Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
  2. Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.
  3. Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
  4. Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.

Correct answer: A

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 290

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?

  1. Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
  2. Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
  3. Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
  4. Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.

Correct answer: A

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports