Question 140
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: Two IS-IS routers in the same site unexpectedly form both Level 1 and Level 2 adjacencies after only their interface names were added to the protocol. 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.
- Add family iso configuration to validated IS-IS circuit templates.
- Enforce system-ID uniqueness checks in provisioning inventories.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
Explanation
Correct Answer
D:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. The control limits repetition of the described root condition: Junos can enable both IS-IS levels by default unless one level is explicitly disabled. During audits, confirm: Operational neighbor state shows only the intended levels after level settings are corrected.
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 Default dual-level operation and the confirming observation is: Operational neighbor state shows only the intended levels after level settings are corrected.
B: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 Default dual-level operation and the confirming observation is: Operational neighbor state shows only the intended levels after level settings are corrected.
C:Enforce system-ID uniqueness checks in provisioning inventories. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is Default dual-level operation and the confirming observation is: Operational neighbor state shows only the intended levels after level settings are corrected.
Question 141
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: Two IS-IS routers use a common Ethernet transit but Level 1 adjacency never forms; Level 2 neighbor status is available and their NET areas differ. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare each router's NET area addresses and the level-specific adjacency state.
- Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB.
- Inspect effective level settings at the global, interface and adjacency levels.
- Inspect the overload bit in the router's IS-IS LSP and the configured maintenance state.
Explanation
Correct Answer
A:Compare each router's NET area addresses and the level-specific adjacency state. This check examines the decisive condition for Level 1 area-address mismatch before any unrelated changes are made. The underlying mechanism is: Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. The confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Incorrect Answers
B:Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
C: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 Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
D:Inspect the overload bit in the router's IS-IS LSP and the configured maintenance state. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS overload bit maintenance. Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Question 142
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: Two IS-IS routers use a common Ethernet transit but Level 1 adjacency never forms; Level 2 neighbor status is available and their NET areas differ. Which routing or service mechanism best explains the reported behavior?
- The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe.
- Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas.
- Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
- Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance.
Explanation
Correct Answer
B:Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area. The targeted correction is: Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation.
Incorrect Answers
A:The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
C: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 Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
D:Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS overload bit maintenance. Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Question 143
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: Two IS-IS routers use a common Ethernet transit but Level 1 adjacency never forms; Level 2 neighbor status is available and their NET areas differ. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Unique system IDs produce distinct LSP originators and stable neighbor database entries.
- Operational neighbor state shows only the intended levels after level settings are corrected.
- The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
- The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Explanation
Correct Answer
C:The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas.
Incorrect Answers
A:Unique system IDs produce distinct LSP originators and stable neighbor database entries. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
B: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 Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
D:The node is absent from selected transit paths while the overload state is asserted, then returns when cleared. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS overload bit maintenance. Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Question 144
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: Two IS-IS routers use a common Ethernet transit but Level 1 adjacency never forms; Level 2 neighbor status is available and their NET areas differ. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart.
- Disable the unneeded IS-IS level on the device or interface according to its network role.
- Use the overload state deliberately during maintenance and clear it only after forwarding readiness checks.
- Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation.
Explanation
Correct Answer
D:Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation. The change addresses the root behavior described here: Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. Verify success with: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Incorrect Answers
A:Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
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 Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
C:Use the overload state deliberately during maintenance and clear it only after forwarding readiness checks. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS overload bit maintenance. Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Question 145
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: Two IS-IS routers use a common Ethernet transit but Level 1 adjacency never forms; Level 2 neighbor status is available and their NET areas differ. Which operational control would best prevent a recurrence of this exact failure mode?
- Validate NET area IDs and system-ID uniqueness during site changes.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Pair overload-bit deployment with a documented recovery criterion.
- Track IPv4 and IPv6 reachability independently during routing expansions.
Explanation
Correct Answer
A:Validate NET area IDs and system-ID uniqueness during site changes. The control limits repetition of the described root condition: Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. During audits, confirm: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Incorrect Answers
B: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 Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
C:Pair overload-bit deployment with a documented recovery criterion. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS overload bit maintenance. Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. In this scenario, however, the distinguishing issue is Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
D: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 Level 1 area-address mismatch and the confirming observation is: The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Question 146
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An IS-IS Level 1 island learns all local subnets but cannot reach another area's servers after its final Level 1/Level 2 router was removed. 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 directed IS-IS link metrics in both routers' advertisements and recompute SPF independently.
Explanation
Correct Answer
B:Trace reachability from the L1 island to a Level 2-capable border device and inspect L2 adjacencies. This check examines the decisive condition for Level 2 backbone continuity before any unrelated changes are made. The underlying mechanism is: Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. The confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
C: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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
D:Compare directed IS-IS link metrics in both routers' advertisements and recompute SPF independently. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS metric directionality. Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Question 147
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An IS-IS Level 1 island learns all local subnets but cannot reach another area's servers after its final Level 1/Level 2 router was removed. 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.
- Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes.
- Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability.
- Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain.
Explanation
Correct Answer
C:Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: A valid L2 connection restores reachability to prefixes outside the local Level 1 area. The targeted correction is: Restore a Level 1/Level 2 boundary and maintain connected Level 2 routing between sites.
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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
B:Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS metric directionality. Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
D:Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Question 148
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: An IS-IS Level 1 island learns all local subnets but cannot reach another area's servers after its final Level 1/Level 2 router was removed. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The authorized service prefix appears in the L1 routing table with correct reachability while other L2 routes remain summarized.
- The advertised link metric matches the design and the calculated path preference changes accordingly.
- Calculated forward and reverse next hops match the directional metric graph.
- A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Explanation
Correct Answer
D:A valid L2 connection restores reachability to prefixes outside the local Level 1 area. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability.
Incorrect Answers
A: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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
B:The advertised link metric matches the design and the calculated path preference changes accordingly. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
C:Calculated forward and reverse next hops match the directional metric graph. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS metric directionality. Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Question 149
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: An IS-IS Level 1 island learns all local subnets but cannot reach another area's servers after its final Level 1/Level 2 router was removed. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore a Level 1/Level 2 boundary and maintain connected Level 2 routing between sites.
- 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.
- Apply compatible wide-metric operation and the validated cost on all affected routers.
Explanation
Correct Answer
A:Restore a Level 1/Level 2 boundary and maintain connected Level 2 routing between sites. The change addresses the root behavior described here: Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. Verify success with: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Incorrect Answers
B: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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
C: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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
D:Apply compatible wide-metric operation and the validated cost on all affected routers. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Question 150
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An IS-IS Level 1 island learns all local subnets but cannot reach another area's servers after its final Level 1/Level 2 router was removed. 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.
- Audit metric encoding and path calculation before importing large traffic-engineering costs.
Explanation
Correct Answer
B:Include removal of each L1/L2 border router in resilience exercises. The control limits repetition of the described root condition: Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. During audits, confirm: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
C: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 Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
D:Audit metric encoding and path calculation before importing large traffic-engineering costs. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS wide metric requirement. Wide metrics allow a broader metric range and require compatible advertisement/interpretation in an IS-IS domain. In this scenario, however, the distinguishing issue is Level 2 backbone continuity and the confirming observation is: A valid L2 connection restores reachability to prefixes outside the local Level 1 area.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests