Pass Your Juniper JN0-664 Exam Easy!

Juniper JN0-664 Exam Questions & Answers, Accurate & Verified By IT Experts

Instant Download, Free Fast Updates, 99.6% Pass Rate

JN0-664 Premium VCE File

Juniper JN0-664 Premium File

96 Questions & Answers

Last Update: Oct 12, 2026

$69.99

JN0-664 Bundle gives you unlimited access to "JN0-664" files. However, this does not replace the need for a .vce exam simulator. To download VCE exam simulator click here
JN0-664 Premium VCE File
Juniper JN0-664 Premium File

96 Questions & Answers

Last Update: Oct 12, 2026

$69.99

Juniper JN0-664 Exam Bundle gives you unlimited access to "JN0-664" files. However, this does not replace the need for a .vce exam simulator. To download your .vce exam simulator click here

Juniper JN0-664 Practice Test 19

Question 180

During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: A link's intended high IS-IS cost cannot be represented correctly using the narrow-metric model selected on an aging configuration. Which operational control would best prevent a recurrence of this exact failure mode?

  1. Monitor link error counters and SPF activity together instead of masking faults with large delays.
  2. Run policy simulation against positive and negative test prefixes on every change.
  3. Add family iso configuration to validated IS-IS circuit templates.
  4. Audit metric encoding and path calculation before importing large traffic-engineering costs.

Explanation

Correct Answer

D:

Audit metric encoding and path calculation before importing large traffic-engineering costs. The control limits repetition of the described root condition: Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. During audits, confirm: The advertised link metric matches the design and the calculated path preference changes accordingly.

Incorrect Answers

A:

Monitor link error counters and SPF activity together instead of masking faults with large delays. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS SPF recalculation load. Frequent link-state database changes trigger recalculation work across routers that share the level's topology. In this scenario, however, the distinguishing issue is IS-IS wide metric requirement and the confirming observation is: The advertised link metric matches the design and the calculated path preference changes accordingly.

B:

Run policy simulation against positive and negative test prefixes on every change. This is a plausible preventive practice for a different IS-IS condition, specifically Route-policy term ordering. Policy evaluation order can make a broad accept term preempt a later specific deny match. In this scenario, however, the distinguishing issue is IS-IS wide metric requirement and the confirming observation is: The advertised link metric matches the design and the calculated path preference changes accordingly.

C:

Add family iso configuration to validated IS-IS circuit templates. This is a plausible preventive practice for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is IS-IS wide metric requirement and the confirming observation is: The advertised link metric matches the design and the calculated path preference changes accordingly.

Question 181

During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: A core Level 2 LSDB is flooded with thousands of specific prefixes from one Level 1 access area despite an aggregation objective. Which targeted check most directly distinguishes the likely cause before a configuration change?

  1. Inspect the L1/L2 border prefix export and summarization behavior into Level 2.
  2. Compare permitted IS-IS levels on both ends and their HELLO PDU categories.
  3. Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs.
  4. Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator.

Explanation

Correct Answer

A:

Inspect the L1/L2 border prefix export and summarization behavior into Level 2. This check examines the decisive condition for L1-to-L2 route summarization before any unrelated changes are made. The underlying mechanism is: L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. The confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

Incorrect Answers

B:

Compare permitted IS-IS levels on both ends and their HELLO PDU categories. This is a plausible diagnostic check for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

C:

Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs. This is a plausible diagnostic check for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

D:

Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

Question 182

During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A core Level 2 LSDB is flooded with thousands of specific prefixes from one Level 1 access area despite an aggregation objective. Which routing or service mechanism best explains the reported behavior?

  1. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link.
  2. L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain.
  3. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires.
  4. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised.

Explanation

Correct Answer

B:

L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The L2 route database contains the intended aggregate rather than all approved component specifics. The targeted correction is: Configure bounded summary export at the correct L1/L2 device and verify coverage.

Incorrect Answers

A:

IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. This is a plausible protocol explanation for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

C:

IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

D:

A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. This is a plausible protocol explanation for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

Question 183

During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A core Level 2 LSDB is flooded with thousands of specific prefixes from one Level 1 access area despite an aggregation objective. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?

  1. The intended level's adjacency forms and the route database populates after compatible settings.
  2. The originator resumes refreshing its LSP and remote databases retain current route information.
  3. The L2 route database contains the intended aggregate rather than all approved component specifics.
  4. The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.

Explanation

Correct Answer

C:

The L2 route database contains the intended aggregate rather than all approved component specifics. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain.

Incorrect Answers

A:

The intended level's adjacency forms and the route database populates after compatible settings. This is a plausible observed evidence for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

B:

The originator resumes refreshing its LSP and remote databases retain current route information. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

D:

The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured. This is a plausible observed evidence for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

Question 184

During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A core Level 2 LSDB is flooded with thousands of specific prefixes from one Level 1 access area despite an aggregation objective. Which response or focused corrective action best addresses this situation without changing unrelated components?

  1. Enable the matching level on both peer interfaces according to the topology.
  2. Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops.
  3. Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB.
  4. Configure bounded summary export at the correct L1/L2 device and verify coverage.

Explanation

Correct Answer

D:

Configure bounded summary export at the correct L1/L2 device and verify coverage. The change addresses the root behavior described here: L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. Verify success with: The L2 route database contains the intended aggregate rather than all approved component specifics.

Incorrect Answers

A:

Enable the matching level on both peer interfaces according to the topology. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

B:

Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

C:

Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

Question 185

During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A core Level 2 LSDB is flooded with thousands of specific prefixes from one Level 1 access area despite an aggregation objective. Which operational control would best prevent a recurrence of this exact failure mode?

  1. Maintain summary constituent route inventories and test withdrawal conditions.
  2. Precheck per-interface level disable statements on both endpoints.
  3. Track IPv4 and IPv6 reachability independently during routing expansions.
  4. Alert on low remaining LSP lifetime and repeated originator refresh failures.

Explanation

Correct Answer

A:

Maintain summary constituent route inventories and test withdrawal conditions. The control limits repetition of the described root condition: L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. During audits, confirm: The L2 route database contains the intended aggregate rather than all approved component specifics.

Incorrect Answers

B:

Precheck per-interface level disable statements on both endpoints. This is a plausible preventive practice for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

C:

Track IPv4 and IPv6 reachability independently during routing expansions. This is a plausible preventive practice for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

D:

Alert on low remaining LSP lifetime and repeated originator refresh failures. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is L1-to-L2 route summarization and the confirming observation is: The L2 route database contains the intended aggregate rather than all approved component specifics.

Question 186

During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A Level 1 router cannot use a required specific service prefix from another area because the site accepts only an attached default route. Which targeted check most directly distinguishes the likely cause before a configuration change?

  1. Inspect effective level settings at the global, interface and adjacency levels.
  2. Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain.
  3. Trace reachability from the L1 island to a Level 2-capable border device and inspect L2 adjacencies.
  4. Inspect L1 and L2 link-state databases separately at each area boundary.

Explanation

Correct Answer

B:

Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain. This check examines the decisive condition for L2-to-L1 route leak before any unrelated changes are made. The underlying mechanism is: Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. The confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Incorrect Answers

A:

Inspect effective level settings at the global, interface and adjacency levels. This is a plausible diagnostic check for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

C:

Trace reachability from the L1 island to a Level 2-capable border device and inspect L2 adjacencies. This is a plausible diagnostic check for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

D:

Inspect L1 and L2 link-state databases separately at each area boundary. This is a plausible diagnostic check for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Question 187

During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A Level 1 router cannot use a required specific service prefix from another area because the site accepts only an attached default route. Which routing or service mechanism best explains the reported behavior?

  1. Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
  2. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability.
  3. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking.
  4. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information.

Explanation

Correct Answer

C:

Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized. The targeted correction is: Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy.

Incorrect Answers

A:

Junos can enable both IS-IS levels by default unless one level is explicitly disabled. This is a plausible protocol explanation for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

B:

Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. This is a plausible protocol explanation for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

D:

Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. This is a plausible protocol explanation for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Question 188

During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A Level 1 router cannot use a required specific service prefix from another area because the site accepts only an attached default route. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?

  1. Operational neighbor state shows only the intended levels after level settings are corrected.
  2. A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
  3. The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
  4. The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Explanation

Correct Answer

D:

The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking.

Incorrect Answers

A:

Operational neighbor state shows only the intended levels after level settings are corrected. This is a plausible observed evidence for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

B:

A valid L2 connection restores reachability to prefixes outside the local Level 1 area. This is a plausible observed evidence for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

C:

The remote area learns approved summarized prefixes without importing the source area's complete L1 topology. This is a plausible observed evidence for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Question 189

During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A Level 1 router cannot use a required specific service prefix from another area because the site accepts only an attached default route. Which response or focused corrective action best addresses this situation without changing unrelated components?

  1. Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy.
  2. Disable the unneeded IS-IS level on the device or interface according to its network role.
  3. Restore a Level 1/Level 2 boundary and maintain connected Level 2 routing between sites.
  4. Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability.

Explanation

Correct Answer

A:

Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy. The change addresses the root behavior described here: Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. Verify success with: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Incorrect Answers

B:

Disable the unneeded IS-IS level on the device or interface according to its network role. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

C:

Restore a Level 1/Level 2 boundary and maintain connected Level 2 routing between sites. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

D:

Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability. This is a plausible configuration or operational fix for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Question 190

During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: A Level 1 router cannot use a required specific service prefix from another area because the site accepts only an attached default route. Which operational control would best prevent a recurrence of this exact failure mode?

  1. Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
  2. Review leak policies for loops and excessive L1 state whenever remote services change.
  3. Include removal of each L1/L2 border router in resilience exercises.
  4. Document protocol-level and area boundaries for each advertised prefix.

Explanation

Correct Answer

B:

Review leak policies for loops and excessive L1 state whenever remote services change. The control limits repetition of the described root condition: Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. During audits, confirm: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

Incorrect Answers

A:

Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

C:

Include removal of each L1/L2 border router in resilience exercises. This is a plausible preventive practice for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.

D:

Document protocol-level and area boundaries for each advertised prefix. This is a plausible preventive practice for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is L2-to-L1 route leak and the confirming observation is: The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.


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

Purchase Individually

JN0-664 Premium File

Premium File
JN0-664 Premium File
96 Q&A
$76.99$69.99

Site Search:

 

VISA, MasterCard, AmericanExpress, UnionPay

SPECIAL OFFER: GET 10% OFF

ExamCollection Premium

ExamCollection Premium Files

Pass your Exam with ExamCollection's PREMIUM files!

  • ExamCollection Certified Safe Files
  • Guaranteed to have ACTUAL Exam Questions
  • Up-to-Date Exam Study Material - Verified by Experts
  • Instant Downloads
Enter Your Email Address to Receive Your 10% Off Discount Code
A Confirmation Link will be sent to this email address to verify your login
We value your privacy. We will not rent or sell your email address

SPECIAL OFFER: GET 10% OFF

Use Discount Code:

MIN10OFF

A confirmation link was sent to your e-mail.
Please check your mailbox for a message from support@examcollection.com and follow the directions.

Next

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

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

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.