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.
Question 151
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A pure Level 1 access node is missing its route toward remote IS-IS areas although the nearest Level 1/Level 2 router still has valid remote routes. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare IS-IS LAN priorities and the elected DIS at each supported level.
- Inspect the leaking policy for selected Level 2 reachability into the local Level 1 domain.
- Inspect the ATT indication and default-route behavior originating from the L1/L2 boundary.
- Compare permitted IS-IS levels on both ends and their HELLO PDU categories.
Explanation
Correct Answer
C:Inspect the ATT indication and default-route behavior originating from the L1/L2 boundary. This check examines the decisive condition for L1/L2 ATT default direction before any unrelated changes are made. The underlying mechanism is: The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. The confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Incorrect Answers
A:Compare IS-IS LAN priorities and the elected DIS at each supported level. This is a plausible diagnostic check for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
B: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 L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
D: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/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Question 152
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A pure Level 1 access node is missing its route toward remote IS-IS areas although the nearest Level 1/Level 2 router still has valid remote routes. Which routing or service mechanism best explains the reported behavior?
- IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior.
- Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking.
- IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link.
- The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met.
Explanation
Correct Answer
D:The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The attached-bit signaling and the L1 default route track the intended L2 reachability. The targeted correction is: Correct the L1/L2 area exit and attached-bit advertisement conditions rather than injecting unrelated host routes.
Incorrect Answers
A:IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. This is a plausible protocol explanation for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
B: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 L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
C: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/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Question 153
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A pure Level 1 access node is missing its route toward remote IS-IS areas although the nearest Level 1/Level 2 router still has valid remote routes. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The attached-bit signaling and the L1 default route track the intended L2 reachability.
- The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable.
- Calculated forward and reverse next hops match the directional metric graph.
- The pseudonode LSP is present and shortest-path calculations include the shared segment.
Explanation
Correct Answer
A:The attached-bit signaling and the L1 default route track the intended L2 reachability. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met.
Incorrect Answers
B:The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable. This is a plausible observed evidence for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
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 L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
D:The pseudonode LSP is present and shortest-path calculations include the shared segment. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS pseudonode LSP missing. The DIS represents a multi-access LAN through a pseudonode LSP that helps other routers build the same graph. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Question 154
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A pure Level 1 access node is missing its route toward remote IS-IS areas although the nearest Level 1/Level 2 router still has valid remote routes. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Set the intended LAN DIS priority consistently for the planned level and verify election state.
- Correct the L1/L2 area exit and attached-bit advertisement conditions rather than injecting unrelated host routes.
- Align directional costs if symmetry is required or explicitly validate the resulting asymmetric service path.
- Restore healthy DIS LSP generation and synchronization before modifying metric policy.
Explanation
Correct Answer
B:Correct the L1/L2 area exit and attached-bit advertisement conditions rather than injecting unrelated host routes. The change addresses the root behavior described here: The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. Verify success with: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Incorrect Answers
A:Set the intended LAN DIS priority consistently for the planned level and verify election state. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
C:Align directional costs if symmetry is required or explicitly validate the resulting asymmetric service path. This is a plausible configuration or operational fix 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 L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
D:Restore healthy DIS LSP generation and synchronization before modifying metric policy. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS pseudonode LSP missing. The DIS represents a multi-access LAN through a pseudonode LSP that helps other routers build the same graph. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Question 155
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A pure Level 1 access node is missing its route toward remote IS-IS areas although the nearest Level 1/Level 2 router still has valid remote routes. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit pseudonode LSP origin after LAN membership changes.
- Model both travel directions in planned metric policy reviews.
- Monitor attached-bit and default-route behavior when L2 isolation is simulated.
- Monitor pseudonode LSP aging during DIS changes.
Explanation
Correct Answer
C:Monitor attached-bit and default-route behavior when L2 isolation is simulated. The control limits repetition of the described root condition: The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. During audits, confirm: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Incorrect Answers
A:Audit pseudonode LSP origin after LAN membership changes. This is a plausible preventive practice for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
B:Model both travel directions in planned metric policy reviews. This is a plausible preventive practice 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 L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
D:Monitor pseudonode LSP aging during DIS changes. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS pseudonode LSP missing. The DIS represents a multi-access LAN through a pseudonode LSP that helps other routers build the same graph. In this scenario, however, the distinguishing issue is L1/L2 ATT default direction and the confirming observation is: The attached-bit signaling and the L1 default route track the intended L2 reachability.
Question 156
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: During an upgrade, a Junos router's links are physically up but other routers deliberately avoid using it as a transit node. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator.
- Compare each router's NET area addresses and the level-specific adjacency state.
- Check wide-metric enablement and effective LSP metric encoding throughout the relevant area.
- Inspect the overload bit in the router's IS-IS LSP and the configured maintenance state.
Explanation
Correct Answer
D:Inspect the overload bit in the router's IS-IS LSP and the configured maintenance state. This check examines the decisive condition for IS-IS overload bit maintenance before any unrelated changes are made. The underlying mechanism is: Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. The confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Incorrect Answers
A: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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
B:Compare each router's NET area addresses and the level-specific adjacency state. This is a plausible diagnostic check for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
C:Check wide-metric enablement and effective LSP metric encoding throughout the relevant area. This is a plausible diagnostic check 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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Question 157
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: During an upgrade, a Junos router's links are physically up but other routers deliberately avoid using it as a transit node. Which routing or service mechanism best explains the reported behavior?
- Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance.
- IS-IS link-state reachability requires periodic refresh before remaining lifetime expires.
- Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas.
- IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior.
Explanation
Correct Answer
A:Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared. The targeted correction is: Use the overload state deliberately during maintenance and clear it only after forwarding readiness checks.
Incorrect Answers
B: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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
C:Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. This is a plausible protocol explanation for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
D:IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. This is a plausible protocol explanation for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Question 158
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: During an upgrade, a Junos router's links are physically up but other routers deliberately avoid using it as a transit node. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The originator resumes refreshing its LSP and remote databases retain current route information.
- The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
- The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
- The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable.
Explanation
Correct Answer
B:The node is absent from selected transit paths while the overload state is asserted, then returns when cleared. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance.
Incorrect Answers
A: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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
C:The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area. This is a plausible observed evidence for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
D:The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable. This is a plausible observed evidence for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Question 159
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: During an upgrade, a Junos router's links are physically up but other routers deliberately avoid using it as a transit node. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB.
- Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation.
- Use the overload state deliberately during maintenance and clear it only after forwarding readiness checks.
- Set the intended LAN DIS priority consistently for the planned level and verify election state.
Explanation
Correct Answer
C:Use the overload state deliberately during maintenance and clear it only after forwarding readiness checks. The change addresses the root behavior described here: Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. Verify success with: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Incorrect Answers
A: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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
B:Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
D:Set the intended LAN DIS priority consistently for the planned level and verify election state. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Question 160
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: During an upgrade, a Junos router's links are physically up but other routers deliberately avoid using it as a transit node. Which operational control would best prevent a recurrence of this exact failure mode?
- Alert on low remaining LSP lifetime and repeated originator refresh failures.
- Validate NET area IDs and system-ID uniqueness during site changes.
- Enforce system-ID uniqueness checks in provisioning inventories.
- Pair overload-bit deployment with a documented recovery criterion.
Explanation
Correct Answer
D:Pair overload-bit deployment with a documented recovery criterion. The control limits repetition of the described root condition: Setting the overload bit tells other routers not to use the node as a transit while maintaining some reachability during planned maintenance. During audits, confirm: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Incorrect Answers
A: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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
B:Validate NET area IDs and system-ID uniqueness during site changes. This is a plausible preventive practice for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
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 IS-IS overload bit maintenance and the confirming observation is: The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests