cert
cert-1
cert-2

Pass Juniper JN0-664 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
JN0-664 Exam - Verified By Experts
JN0-664 Premium File

JN0-664 Premium File

$69.99
$76.99
  • Premium File 96 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 20 downloads in the last 7 days
block-screenshots
Juniper JN0-664 Practice Test 13

Question 120

A Junos service-provider routing engineer investigates this service-provider network scenario. A route-leak adjustment causes an internal loop between two L1/L2 exits after one site uses stale summary and attached-bit assumptions. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.
  2. Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access.
  3. Review show isis interface detail, LAN priority, circuit level, elected DIS, neighbor states and pseudonode LSP records.
  4. Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
  5. Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability.

Explanation

Correct Answers

A:

The direct discriminating observation is: Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.

E:

The case-specific routing and services action is: Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability. The governing Junos routing/service principle is: An L1 network may rely on attached/default routing toward L1/L2 routers; deliberate interlevel leaking or summarization can expose selected routes without making every area full Level 2. Verify the decision through: Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.

Incorrect Answers

B:

This alternative proposes: Implement intended full-mesh or hub-and-spoke VPN reachability with precise route-target and policy behavior, including explicitly approved Internet access. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue IS-IS Level 2 to Level 1 route leaking and summaries.

C:

This alternative proposes: Review show isis interface detail, LAN priority, circuit level, elected DIS, neighbor states and pseudonode LSP records. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue IS-IS Level 2 to Level 1 route leaking and summaries in the stated situation (A route-leak adjustment causes an internal loop between two L1/L2 exits after one site uses stale summary and attached-bit assumptions.). A better case-specific check is: Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.

D:

This alternative proposes: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue IS-IS Level 2 to Level 1 route leaking and summaries.

Question 121

A Junos service-provider routing engineer investigates the following routing and service incident: After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.
  2. Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability.
  3. Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP.
  4. Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs.

Explanation

Correct Answer

A:

IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors.

Incorrect Answers

B:

This alternative proposes: Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

C:

This alternative proposes: Separate Level 1 intra-area and Level 2 inter-area IS-IS forwarding responsibilities when building a multi-area service-provider IGP. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: Trace an LDP Layer 2 circuit end to end using neighbor signaling, pseudowire identifiers and operational connection state before changing customer VLANs. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 122

A provider routing design review considers this situation. After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up. A colleague proposes: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP. Which technical principle BEST supports that action? Select ONE best answer.

  1. IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.
  2. An L1 network may rely on attached/default routing toward L1/L2 routers; deliberate interlevel leaking or summarization can expose selected routes without making every area full Level 2.
  3. Level 1 routers know their local IS-IS area, Level 2 routers maintain interarea connectivity, and L1/L2 systems can provide area exits with suitable reachability and attached signaling.
  4. BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters.

Explanation

Correct Answer

A:

The relevant Junos service-provider networking principle is: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. In the described provider-network case (After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up.), it supports the planned action: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

Incorrect Answers

B:

This alternative proposes: An L1 network may rely on attached/default routing toward L1/L2 routers; deliberate interlevel leaking or summarization can expose selected routes without making every area full Level 2. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

C:

This alternative proposes: Level 1 routers know their local IS-IS area, Level 2 routers maintain interarea connectivity, and L1/L2 systems can provide area exits with suitable reachability and attached signaling. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 123

A Juniper service-provider engineer needs decisive verification evidence for this situation. After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Compare protocol mode on all transit interfaces, show pim interfaces/neighbors, joins or pruning state, multicast flow and CPU/link exposure.
  2. Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.
  3. Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors.
  4. Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs.

Explanation

Correct Answer

C:

The direct discriminating observation is: Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors. In the stated situation (After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up.), the intended acceptance outcome is: Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit.

Incorrect Answers

A:

This alternative proposes: Compare protocol mode on all transit interfaces, show pim interfaces/neighbors, joins or pruning state, multicast flow and CPU/link exposure. It concerns a different Junos engineering issue PIM dense mode versus sparse mode interface deployment, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

B:

This alternative proposes: Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 124

A service-provider acceptance team reviews the result of a provider-service change. After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up. The intended verification is: Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors. Which outcome BEST demonstrates success? Select ONE best answer.

  1. Access routers learn only authorized leaked routes, continue using their correct area exit and do not create interlevel routing loops.
  2. Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit.
  3. Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
  4. All site prefixes move between areas without routing loops, and the proposed backbone topology survives its agreed failure test.

Explanation

Correct Answer

B:

The verified success outcome is: Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit. Confirm this by: Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors.

Incorrect Answers

A:

That option concerns IS-IS Level 2 to Level 1 route leaking and summaries. The related controlled intervention is: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

C:

This alternative proposes: Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

That option concerns OSPF multi-area backbone connectivity and virtual-link limitations. The related controlled intervention is: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

Question 125

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. After a maintenance event, a Junos Level 1 neighbor shows Area Mismatch although the Ethernet interface remains link Up. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability.
  2. Treat an IS-IS DIS as permanently paired with a mandatory BDR and declare the broadcast domain broken when a backup election is not shown.
  3. Assume every inter-provider VPN can be connected by advertising raw customer private addresses on an unsecured global peering session with no labels or VPN policy.
  4. Leak the entire provider table into every small Level 1 access area and assert this cannot affect memory, scale or path choices.

Explanation

Correct Answer

A:

The directly relevant unsafe assumption is: Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability. That conflicts with the edge-to-cloud principle: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.

Incorrect Answers

B:

This alternative proposes: Treat an IS-IS DIS as permanently paired with a mandatory BDR and declare the broadcast domain broken when a backup election is not shown. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

C:

This alternative proposes: Assume every inter-provider VPN can be connected by advertising raw customer private addresses on an unsecured global peering session with no labels or VPN policy. It concerns a different Junos engineering issue Interprovider Layer 3 VPN options and carrier of carriers, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: Leak the entire provider table into every small Level 1 access area and assert this cannot affect memory, scale or path choices. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 126

A Junos service-provider routing engineer investigates the following routing and service incident: An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.
  2. Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm.
  3. Inspect broadcast-network DR and BDR election state and interface priority before attempting to control database exchange behavior on an Ethernet shared segment.
  4. Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability.

Explanation

Correct Answer

A:

The case-specific routing and services action is: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP. The governing Junos routing/service principle is: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.

Incorrect Answers

B:

This alternative proposes: Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

C:

This alternative proposes: Inspect broadcast-network DR and BDR election state and interface priority before attempting to control database exchange behavior on an Ethernet shared segment. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 127

A provider routing design review considers this situation. An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication. A colleague proposes: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP. Which technical principle BEST supports that action? Select ONE best answer.

  1. IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
  2. IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.
  3. Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered.
  4. IS-IS wide metrics support extended values and modern topology use cases, but cost selection depends on configured interface metrics and supported protocol behavior.

Explanation

Correct Answer

B:

The relevant Junos service-provider networking principle is: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. In the described provider-network case (An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication.), it supports the planned action: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

Incorrect Answers

A:

This alternative proposes: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

C:

This alternative proposes: Pseudowire transport can impose encapsulation overhead and require compatible payload/MTU or control-word behavior; signaling Up does not guarantee all customer frame sizes are successfully delivered. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: IS-IS wide metrics support extended values and modern topology use cases, but cost selection depends on configured interface metrics and supported protocol behavior. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 128

A Juniper service-provider engineer needs decisive verification evidence for this situation. An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors.
  2. Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
  3. Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
  4. Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits.

Explanation

Correct Answer

A:

The direct discriminating observation is: Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors. In the stated situation (An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication.), the intended acceptance outcome is: Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit.

Incorrect Answers

B:

This alternative proposes: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

C:

This alternative proposes: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Question 129

A service-provider acceptance team reviews the result of a provider-service change. An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication. The intended verification is: Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors. Which outcome BEST demonstrates success? Select ONE best answer.

  1. Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
  2. After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.
  3. Each subscriber region reaches its own internal endpoints and approved destinations through the selected L1/L2 border systems without losing its default path.
  4. Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit.

Explanation

Correct Answer

D:

The verified success outcome is: Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit. Confirm this by: Run show isis adjacency extensive, inspect down reason, show isis interface, interface errors, NET area values, hello parameters and authentication state on both neighbors. The related controlled intervention is: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

Incorrect Answers

A:

This alternative proposes: Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations. It concerns a different Junos engineering issue IS-IS link-state packet flooding and database consistency, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

B:

That option concerns BGP flap damping penalties and recovery. The related controlled intervention is: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

C:

That option concerns IS-IS level one level two hierarchy and area boundaries. The related controlled intervention is: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

Question 130

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured.
  2. Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path.
  3. Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability.
  4. Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.

Explanation

Correct Answer

C:

The directly relevant unsafe assumption is: Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability. That conflicts with the edge-to-cloud principle: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. Apply instead: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.

Incorrect Answers

A:

This alternative proposes: Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

B:

This alternative proposes: Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

D:

This alternative proposes: Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.

Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests