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 26

Question 250

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?

  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 level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
  4. Inspect the LSP contents and specific reachability TLV type and value at the correct level rather than relying only on generic neighbor status.

Correct answer: B

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 LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.

B.

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.

C.

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.

D.

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.

Question 251

The provider operations team at Silverpeak Data Networks reports: 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. Which implementation decision best corrects the cause?

  1. Inspect the correct IS-IS PDU and Type-Length-Value carrying the intended reachability or metric information, then align compatible wide-metric operation.
  2. Trace IS-IS LSP flooding and database synchronization at the affected level, correcting the propagation or adjacency gap.
  3. Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
  4. Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

Correct answer: D

Explanation of each choice

A.

The other action is relevant when A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. The current case instead requires: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers. The distinction is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

B.

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: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

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: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

D.

Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers. The case-specific reason is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP. A direct acceptance test is: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

Question 252

During a post-change check at Silverpeak Data Networks, the original condition was: 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. What evidence would validate the corrected behavior?

  1. The expected neighbor or prefix TLV is present in current LSPs with the intended metric representation, and SPF results match.
  2. Only approved interlevel prefixes appear in the target Level 1 database and route table, preserving reachability without a wholesale route leak.
  3. The relevant LSP identifiers, sequence numbers and contents match among routers at the same level, and SPF reflects the current topology.
  4. Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

Correct answer: D

Explanation of each choice

A.

The observation confirms a different component's behavior. Its source context is: A parser discards useful IS-IS reachability information because the team mistakes an extended reachability TLV for a Hello timer field. In this case the success criterion is: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

B.

That check proves something else, such as: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. It could pass while the stated problem remains. The targeted evidence here is: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

C.

This would be valid for another situation: A transit core forms stable IS-IS adjacencies but one router's link-state PDU database lacks a refreshed neighbor record. It does not establish that the failing boundary in this scenario works; verify: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

D.

Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation. The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

Question 253

At Silverpeak Data Networks, an engineer is asked to explain this case: 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. Which underlying routing or switching principle accounts for the appropriate solution?

  1. IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently.
  2. IS-IS LSPs encode link-state reachability and are flooded within a level so each participating system calculates from a consistent LSDB.
  3. IS-IS route leaking intentionally advertises selected reachability between Level 2 and Level 1 rather than treating all interarea prefixes as native L1 routes.
  4. IS-IS uses structured TLVs inside PDUs to advertise attributes and reachability; metric encodings and PDU purposes are distinct.

Correct answer: A

Explanation of each choice

A.

IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently. The key distinction is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP. Accordingly the remedy is: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

B.

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: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

C.

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 extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently.

D.

This explains a separate protocol behavior: A provider changes wide metrics in IS-IS but monitoring reads only legacy narrow reachability data and reports no topology effect. In the current facts, the controlling mechanism is: IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently.

Question 254

A risk assessment at Silverpeak Data Networks identifies: 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. Which practical consequence is most specifically tied to this failure?

  1. Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.
  2. The network may misinterpret advertisements and calculate a route inconsistent with the intended metric change.
  3. A stale LSDB can cause transient loops, missing reachability and inconsistent path computation even while some adjacencies remain Up.
  4. Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.

Correct answer: A

Explanation of each choice

A.

Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments. The direct mitigation is: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

B.

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: Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.

C.

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: Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.

D.

It is a risk in another topology or protocol state: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. Here the most direct failure path is: Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.

Question 255

The on-call engineer at Silverpeak Data Networks receives this fault report: 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. What initial check best isolates the actual failing protocol stage?

  1. Inspect level-specific import/export policy and L1 versus L2 routes for the exact prefix before changing interface metric values.
  2. Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
  3. Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
  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 Level 1 branch needs a selected prefix from Level 2 but a restrictive policy leaves it unaware of the destination. The relevant initial check is: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.

B.

This check may help with another root cause, for example: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. It does not test the first failed condition; start with: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.

C.

Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level. The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

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: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.

Question 256

A production change request at Keystone Industrial includes this finding: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. What should the engineer change to address it?

  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. Align the IS-IS interface activation, circuit level and required authentication, and confirm valid IIH exchanges on both ends.
  4. Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

Correct answer: D

Explanation of each choice

A.

This action may apply to a different problem, 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 repair the stated failure boundary. The case-specific reason is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

B.

The other action is relevant when A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. The current case instead requires: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers. The distinction is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

C.

That would address a separate configuration fault: Two IS-IS devices have matching area identifiers but the configured interface level and authentication parameters prevent Hello acceptance. This stem identifies a different cause, corrected by: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

D.

Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers. The case-specific reason is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP. A direct acceptance test is: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

Question 257

After Keystone Industrial applies its proposed fix to this problem — An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. — which observation best proves the specific failure has been resolved?

  1. The relevant LSP identifiers, sequence numbers and contents match among routers at the same level, and SPF reflects the current topology.
  2. IS-IS adjacency moves to Up at the intended level with matching system IDs and Hello acceptance, followed by expected reachability.
  3. Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.
  4. The intended subnet appears with the expected IS-IS advertisement attributes and disallowed connected/static routes remain absent.

Correct answer: C

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: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

B.

The observation confirms a different component's behavior. Its source context is: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. In this case the success criterion is: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

C.

Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation. The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

D.

This would be valid for another situation: A connected service subnet must be injected into IS-IS but is absent even though the router's connected route is active. It does not establish that the failing boundary in this scenario works; verify: Advertised extended reachability metrics match the design and SPF selects the expected lower-cost path without metric truncation.

Question 258

An architecture review at Keystone Industrial examines the following symptom: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. What Junos or protocol mechanism is most directly responsible?

  1. IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently.
  2. IS-IS uses Level 1 for intra-area routing and Level 2 for interarea routing; area matching rules differ by adjacency level.
  3. Junos IS-IS operational views separate Hello adjacency establishment from database flooding and SPF computation.
  4. The IS-IS designated intermediate system represents the shared LAN as a pseudonode; it is not an OSPF DR/BDR pair.

Correct answer: A

Explanation of each choice

A.

IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently. The key distinction is: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP. Accordingly the remedy is: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

B.

The statement can be true when A provider redesigns two areas and loses expected interarea reachability because a border router is no longer participating in Level 2 routing. But it does not explain the reported failure. Here: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

C.

The statement can be true when A provider cannot decide whether IS-IS is losing Hello packets or receiving LSDB updates but failing to process them. But it does not explain the reported failure. Here: The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

D.

That principle belongs to a different service stage: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. The directly relevant mechanism is: IS-IS extended/wide metrics permit larger link cost values and are carried in suitable reachability TLVs; all participating speakers must interpret them consistently.

Question 259

The team at Keystone Industrial defers a fix for this condition: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. What failure is most likely if no targeted control is applied?

  1. Overly broad leaking bloats a constrained L1 area or exposes route reachability contrary to the topology plan.
  2. Incorrect assumptions about DIS operation can hide LAN topology problems or prompt destabilizing changes to a working adjacency.
  3. Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.
  4. Neighbors cannot exchange link-state packets and the core loses alternative paths during topology changes.

Correct answer: C

Explanation of each choice

A.

That consequence is more closely associated with another deficiency, such as: An operator leaks the entire Level 2 table into a small Level 1 area when only a single approved service prefix was required. The described fault instead exposes: Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.

B.

It is a risk in another topology or protocol state: Routers on an IS-IS broadcast LAN show a different designated intermediate system than the operations diagram predicts. Here the most direct failure path is: Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.

C.

Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments. The direct mitigation is: Enable consistent wide-metric support and configure the intended IS-IS interface metrics across participating routers.

D.

That consequence is more closely associated with another deficiency, such as: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. The described fault instead exposes: Path selection may not reflect network engineering intent or can lose reachability across mixed metric deployments.

Question 260

During provider troubleshooting at Keystone Industrial, this symptom is observed: An IS-IS design uses extended metrics on some routers but a legacy metric setting prevents uniform interpretation of path cost. Which targeted inspection should precede remediation?

  1. Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.
  2. Inspect `show isis adjacency` and Hello packet details including level, authentication and interface enablement.
  3. Inspect LAN adjacency detail, DIS identity, priorities and pseudonode LSPs at the affected level.
  4. Compare `show isis database` LSP IDs, sequence values and level-specific flooding status between the affected neighbors.

Correct answer: A

Explanation of each choice

A.

Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level. The mismatch concerns IS-IS metric encoding and SPF cost, not Junos route preference between static and BGP.

B.

The check diagnoses a different layer of service. Its source issue is: An IS-IS point-to-point peer stays down after interface provisioning while interface counters increment and other routed protocols can use the link. The relevant initial check is: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.

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: Inspect configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.

D.

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 configured metric styles, LSP reachability TLVs and computed route costs at the same IS-IS level.

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