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 22

Question 210

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?

  1. Start with `show isis adjacency`, per-level database and relevant interface counters or traceoptions to locate the first divergence.
  2. Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
  3. Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
  4. Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 211

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?

  1. 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.
  2. Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
  3. Trace IS-IS LSP flooding and database synchronization at the affected level, correcting the propagation or adjacency gap.
  4. Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 212

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?

  1. IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
  2. The relevant LSP identifiers, sequence numbers and contents match among routers at the same level, and SPF reflects the current topology.
  3. Level 1 neighbors share the intended area identity and Level 2 adjacencies form where required, with valid routes available beyond each local area.
  4. One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.

Correct answer: A

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 213

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?

  1. Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
  2. IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
  3. IS-IS LSPs encode link-state reachability and are flooded within a level so each participating system calculates from a consistent LSDB.
  4. IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 214

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?

  1. Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
  2. Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.
  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: B

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 215

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?

  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. Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
  4. Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.

Correct answer: C

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 216

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?

  1. Correct and constrain the relevant IS-IS export policy to originate only approved non-IS-IS route sources with valid active contributors.
  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. Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
  4. Inspect the correct IS-IS PDU and Type-Length-Value carrying the intended reachability or metric information, then align compatible wide-metric operation.

Correct answer: C

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 217

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?

  1. IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
  2. One appropriate DIS is elected with the expected pseudonode LSP, and level-specific LAN neighbors synchronize correctly.
  3. Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.
  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.

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.

B.

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.

C.

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.

D.

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.

Question 218

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?

  1. IS-IS LSPs encode link-state reachability and are flooded within a level so each participating system calculates from a consistent LSDB.
  2. IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
  3. IS-IS Hello PDUs establish neighbor relationships using circuit parameters and level/authentication compatibility rather than IP neighbor discovery alone.
  4. IS-IS uses structured TLVs inside PDUs to advertise attributes and reachability; metric encodings and PDU purposes are distinct.

Correct answer: C

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 219

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?

  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. Changing route metrics without identifying the failing control-plane stage can leave intermittent packet loss and reconvergence outages.
  4. Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.

Correct answer: D

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

Question 220

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?

  1. Compare `show isis database` LSP IDs, sequence values and level-specific flooding status between the affected neighbors.
  2. Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
  3. Check each router's NET/area and IS-IS level capabilities, plus adjacency level and Level 2 route presence.
  4. Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.

Correct answer: B

Explanation of each choice

A.

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.

B.

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.

C.

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.

D.

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.

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