Question 170
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: Routers on a shared IS-IS Ethernet link see neighbors but topology calculations omit a network link when the LAN's pseudonode advertisement is missing. Which operational control would best prevent a recurrence of this exact failure mode?
- Add family iso configuration to validated IS-IS circuit templates.
- Monitor pseudonode LSP aging during DIS changes.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Keep router IDs, system IDs and hostnames mapped in operations documentation.
Explanation
Correct Answer
B:Monitor pseudonode LSP aging during DIS changes. The control limits repetition of the described root condition: The DIS represents a multi-access LAN through a pseudonode LSP that helps other routers build the same graph. During audits, confirm: The pseudonode LSP is present and shortest-path calculations include the shared segment.
Incorrect Answers
A: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 pseudonode LSP missing and the confirming observation is: The pseudonode LSP is present and shortest-path calculations include the shared segment.
C: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 IS-IS pseudonode LSP missing and the confirming observation is: The pseudonode LSP is present and shortest-path calculations include the shared segment.
D:Keep router IDs, system IDs and hostnames mapped in operations documentation. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS hostname visibility. Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. In this scenario, however, the distinguishing issue is IS-IS pseudonode LSP missing and the confirming observation is: The pseudonode LSP is present and shortest-path calculations include the shared segment.
Question 171
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: A network engineer expects Level 1 detailed topology changes in one area to appear directly as Level 1 LSPs in another area. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain.
- Trace reachability from the L1 island to a Level 2-capable border device and inspect L2 adjacencies.
- Inspect L1 and L2 link-state databases separately at each area boundary.
- Compare effective IS-IS LSP authentication settings and the rollover schedule on adjacent routers.
Explanation
Correct Answer
C:Inspect L1 and L2 link-state databases separately at each area boundary. This check examines the decisive condition for LSP flooding scope at levels before any unrelated changes are made. The underlying mechanism is: Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. The confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Incorrect Answers
A:Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain. This is a plausible diagnostic check for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
B: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 LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
D:Compare effective IS-IS LSP authentication settings and the rollover schedule on adjacent routers. This is a plausible diagnostic check for a different IS-IS condition, specifically LSP authentication disagreement. Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Question 172
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: A network engineer expects Level 1 detailed topology changes in one area to appear directly as Level 1 LSPs in another area. Which routing or service mechanism best explains the reported behavior?
- Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking.
- Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization.
- Frequent link-state database changes trigger recalculation work across routers that share the level's topology.
- Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information.
Explanation
Correct Answer
D:Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology. The targeted correction is: Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability.
Incorrect Answers
A:Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. This is a plausible protocol explanation for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
B:Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. This is a plausible protocol explanation for a different IS-IS condition, specifically LSP authentication disagreement. Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
C:Frequent link-state database changes trigger recalculation work across routers that share the level's topology. This is a plausible protocol explanation 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 LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Question 173
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: A network engineer expects Level 1 detailed topology changes in one area to appear directly as Level 1 LSPs in another area. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
- The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
- Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
- After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
Explanation
Correct Answer
A:The remote area learns approved summarized prefixes without importing the source area's complete L1 topology. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information.
Incorrect Answers
B:The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized. This is a plausible observed evidence for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
C:Authentication failure counters drop to zero and matching LSPs are accepted on the affected level. This is a plausible observed evidence for a different IS-IS condition, specifically LSP authentication disagreement. Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
D:After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes. This is a plausible observed evidence 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 LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Question 174
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: A network engineer expects Level 1 detailed topology changes in one area to appear directly as Level 1 LSPs in another area. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy.
- Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability.
- Restore a Level 1/Level 2 boundary and maintain connected Level 2 routing between sites.
- Coordinate the key profile and change order to preserve protocol compatibility during rotation.
Explanation
Correct Answer
B:Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability. The change addresses the root behavior described here: Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. Verify success with: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Incorrect Answers
A:Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy. This is a plausible configuration or operational fix for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
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 LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
D:Coordinate the key profile and change order to preserve protocol compatibility during rotation. This is a plausible configuration or operational fix for a different IS-IS condition, specifically LSP authentication disagreement. Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Question 175
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A network engineer expects Level 1 detailed topology changes in one area to appear directly as Level 1 LSPs in another area. Which operational control would best prevent a recurrence of this exact failure mode?
- Review leak policies for loops and excessive L1 state whenever remote services change.
- Include removal of each L1/L2 border router in resilience exercises.
- Document protocol-level and area boundaries for each advertised prefix.
- Test adjacency and LSP acceptance across both IS-IS levels before retiring earlier keys.
Explanation
Correct Answer
C:Document protocol-level and area boundaries for each advertised prefix. The control limits repetition of the described root condition: Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. During audits, confirm: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Incorrect Answers
A:Review leak policies for loops and excessive L1 state whenever remote services change. This is a plausible preventive practice for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
B: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 LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
D:Test adjacency and LSP acceptance across both IS-IS levels before retiring earlier keys. This is a plausible preventive practice for a different IS-IS condition, specifically LSP authentication disagreement. Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. In this scenario, however, the distinguishing issue is LSP flooding scope at levels and the confirming observation is: The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Question 176
During a service-provider escalation, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Correlate interface flaps, LSP update timestamps and SPF execution counters.
- Trace the route against ordered policy terms and identify the first terminating match.
- Inspect the presence of family iso under both logical interfaces and count incoming IS-IS PDUs.
- Check wide-metric enablement and effective LSP metric encoding throughout the relevant area.
Explanation
Correct Answer
D:Check wide-metric enablement and effective LSP metric encoding throughout the relevant area. This check examines the decisive condition for IS-IS wide metric requirement before any unrelated changes are made. The underlying mechanism is: Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. The confirming observation is: The advertised link metric matches the design and the calculated path preference changes accordingly.
Incorrect Answers
A:Correlate interface flaps, LSP update timestamps and SPF execution counters. This is a plausible diagnostic check 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:Trace the route against ordered policy terms and identify the first terminating match. This is a plausible diagnostic check 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:Inspect the presence of family iso under both logical interfaces and count incoming IS-IS PDUs. This is a plausible diagnostic check 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 177
During a new PE-router service turn-up, 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 routing or service mechanism best explains the reported behavior?
- Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain.
- Frequent link-state database changes trigger recalculation work across routers that share the level's topology.
- Policy evaluation order can make a broad accept term preempt a later specific deny match.
- Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing.
Explanation
Correct Answer
A:Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS 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 advertised link metric matches the design and the calculated path preference changes accordingly. The targeted correction is: Apply compatible wide-metric operation and the validated cost on all affected routers.
Incorrect Answers
B:Frequent link-state database changes trigger recalculation work across routers that share the level's topology. This is a plausible protocol explanation 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.
C:Policy evaluation order can make a broad accept term preempt a later specific deny match. This is a plausible protocol explanation 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.
D:Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. This is a plausible protocol explanation 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 178
During a customer VPN change window, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
- The advertised link metric matches the design and the calculated path preference changes accordingly.
- The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
- The interface accepts IS-IS Hello PDUs and the expected neighbor appears after ISO family is enabled.
Explanation
Correct Answer
B:The advertised link metric matches the design and the calculated path preference changes accordingly. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain.
Incorrect Answers
A:After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes. This is a plausible observed evidence 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.
C:The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected. This is a plausible observed evidence 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.
D:The interface accepts IS-IS Hello PDUs and the expected neighbor appears after ISO family is enabled. This is a plausible observed evidence 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 179
During a core-routing migration rehearsal, 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 response or focused corrective action best addresses this situation without changing unrelated components?
- Correct the flapping circuit and apply supported SPF pacing only after identifying the physical cause.
- Put restrictive or more-specific route handling before broad accept behavior.
- Apply compatible wide-metric operation and the validated cost on all affected routers.
- Enable family iso and the intended protocol interface settings on the transit link.
Explanation
Correct Answer
C:Apply compatible wide-metric operation and the validated cost on all affected routers. The change addresses the root behavior described here: Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. Verify success with: The advertised link metric matches the design and the calculated path preference changes accordingly.
Incorrect Answers
A:Correct the flapping circuit and apply supported SPF pacing only after identifying the physical cause. This is a plausible configuration or operational fix 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:Put restrictive or more-specific route handling before broad accept behavior. This is a plausible configuration or operational fix 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.
D:Enable family iso and the intended protocol interface settings on the transit link. This is a plausible configuration or operational fix 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 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?
- Monitor link error counters and SPF activity together instead of masking faults with large delays.
- Run policy simulation against positive and negative test prefixes on every change.
- Add family iso configuration to validated IS-IS circuit templates.
- 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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests