Question 240
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: A Junos device returns from restart and begins attracting heavy transit traffic before all services and forwarding state have recovered. Which operational control would best prevent a recurrence of this exact failure mode?
- Validate NET area IDs and system-ID uniqueness during site changes.
- Alert on low remaining LSP lifetime and repeated originator refresh failures.
- Precheck per-interface level disable statements on both endpoints.
- Review maintenance timers versus real convergence evidence, including routing table and FIB readiness.
Explanation
Correct Answer
D:Review maintenance timers versus real convergence evidence, including routing table and FIB readiness. The control limits repetition of the described root condition: Overload-bit control can keep the node from being selected as a transit until the control and forwarding planes are ready. During audits, confirm: Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
Incorrect Answers
A: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 after startup and the confirming observation is: Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
B: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 after startup and the confirming observation is: Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
C:Precheck per-interface level disable statements on both endpoints. This is a plausible preventive practice for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is IS-IS overload after startup and the confirming observation is: Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
Question 241
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: IS-IS Level 2 IPv4 prefixes are exchanged successfully while expected IPv6 route advertisements never appear after enabling IPv6 on access links. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs.
- Compare IS-IS LAN priorities and the elected DIS at each supported level.
- Review export policy terms and the active route's protocol and prefix properties.
- Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator.
Explanation
Correct Answer
A:Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs. This check examines the decisive condition for IPv6 IS-IS reachability absent before any unrelated changes are made. The underlying mechanism is: A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. The confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Incorrect Answers
B: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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
C:Review export policy terms and the active route's protocol and prefix properties. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS external route policy. Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
D:Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Question 242
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: IS-IS Level 2 IPv4 prefixes are exchanged successfully while expected IPv6 route advertisements never appear after enabling IPv6 on access links. 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.
- A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised.
- Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence.
- IS-IS link-state reachability requires periodic refresh before remaining lifetime expires.
Explanation
Correct Answer
B:A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured. The targeted correction is: Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops.
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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
C:Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS external route policy. Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
D: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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Question 243
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: IS-IS Level 2 IPv4 prefixes are exchanged successfully while expected IPv6 route advertisements never appear after enabling IPv6 on access links. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable.
- The intended source route passes the policy and appears as reachability in neighboring L2 LSPs.
- The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
- The originator resumes refreshing its LSP and remote databases retain current route information.
Explanation
Correct Answer
C:The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised.
Incorrect Answers
A: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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
B:The intended source route passes the policy and appears as reachability in neighboring L2 LSPs. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS external route policy. Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
D: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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Question 244
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: IS-IS Level 2 IPv4 prefixes are exchanged successfully while expected IPv6 route advertisements never appear after enabling IPv6 on access links. 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.
- Restore a narrow approved export term for the service prefix and source protocol.
- Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB.
- Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops.
Explanation
Correct Answer
D:Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops. The change addresses the root behavior described here: A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. Verify success with: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
B:Restore a narrow approved export term for the service prefix and source protocol. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS external route policy. Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
C:Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Question 245
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: IS-IS Level 2 IPv4 prefixes are exchanged successfully while expected IPv6 route advertisements never appear after enabling IPv6 on access links. Which operational control would best prevent a recurrence of this exact failure mode?
- Track IPv4 and IPv6 reachability independently during routing expansions.
- Test policy term ordering and accidental external redistribution during each update.
- Audit pseudonode LSP origin after LAN membership changes.
- Alert on low remaining LSP lifetime and repeated originator refresh failures.
Explanation
Correct Answer
A:Track IPv4 and IPv6 reachability independently during routing expansions. The control limits repetition of the described root condition: A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. During audits, confirm: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Incorrect Answers
B:Test policy term ordering and accidental external redistribution during each update. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS external route policy. Junos IS-IS advertisement of selected non-IS-IS routes depends on explicit matching export policy rather than arbitrary inet.0 presence. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
C: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 IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
D:Alert on low remaining LSP lifetime and repeated originator refresh failures. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IPv6 IS-IS reachability absent and the confirming observation is: The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
Question 246
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: During a transient control-plane outage, a remote LSP ages out and prefixes disappear despite transit data links remaining active. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the overload bit in the router's IS-IS LSP and the configured maintenance state.
- Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator.
- Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs.
- Inspect the L1/L2 border prefix export and summarization behavior into Level 2.
Explanation
Correct Answer
B:Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator. This check examines the decisive condition for IS-IS LSP lifetime expiry before any unrelated changes are made. The underlying mechanism is: IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. The confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
Incorrect Answers
A: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 IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
C:Inspect enabled IS-IS address-family reachability and the IPv6 TLVs in LSPs. This is a plausible diagnostic check for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
D:Inspect the L1/L2 border prefix export and summarization behavior into Level 2. This is a plausible diagnostic check for a different IS-IS condition, specifically L1-to-L2 route summarization. L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
Question 247
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: During a transient control-plane outage, a remote LSP ages out and prefixes disappear despite transit data links remaining active. 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.
- A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised.
- IS-IS link-state reachability requires periodic refresh before remaining lifetime expires.
- L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain.
Explanation
Correct Answer
C:IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The originator resumes refreshing its LSP and remote databases retain current route information. The targeted correction is: Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB.
Incorrect Answers
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 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 IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
B:A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. This is a plausible protocol explanation for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
D:L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. This is a plausible protocol explanation for a different IS-IS condition, specifically L1-to-L2 route summarization. L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
Question 248
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: During a transient control-plane outage, a remote LSP ages out and prefixes disappear despite transit data links remaining active. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The node is absent from selected transit paths while the overload state is asserted, then returns when cleared.
- The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured.
- The L2 route database contains the intended aggregate rather than all approved component specifics.
- The originator resumes refreshing its LSP and remote databases retain current route information.
Explanation
Correct Answer
D:The originator resumes refreshing its LSP and remote databases retain current route information. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: IS-IS link-state reachability requires periodic refresh before remaining lifetime expires.
Incorrect Answers
A: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 IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
B:The neighboring L2 LSDB and IPv6 RIB contain the approved IPv6 prefixes once support is configured. This is a plausible observed evidence for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
C:The L2 route database contains the intended aggregate rather than all approved component specifics. This is a plausible observed evidence for a different IS-IS condition, specifically L1-to-L2 route summarization. L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
Question 249
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: During a transient control-plane outage, a remote LSP ages out and prefixes disappear despite transit data links remaining active. 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.
- Use the overload state deliberately during maintenance and clear it only after forwarding readiness checks.
- Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops.
- Configure bounded summary export at the correct L1/L2 device and verify coverage.
Explanation
Correct Answer
A:Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB. The change addresses the root behavior described here: IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. Verify success with: The originator resumes refreshing its LSP and remote databases retain current route information.
Incorrect Answers
B: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 IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
C:Enable compatible IPv6 IS-IS reachability for the intended level and check end-to-end next hops. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IPv6 IS-IS reachability absent. A healthy IS-IS adjacency for one protocol does not itself prove the relevant IPv6 reachability TLVs are being advertised. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
D:Configure bounded summary export at the correct L1/L2 device and verify coverage. This is a plausible configuration or operational fix for a different IS-IS condition, specifically L1-to-L2 route summarization. L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
Question 250
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: During a transient control-plane outage, a remote LSP ages out and prefixes disappear despite transit data links remaining active. Which operational control would best prevent a recurrence of this exact failure mode?
- Pair overload-bit deployment with a documented recovery criterion.
- Alert on low remaining LSP lifetime and repeated originator refresh failures.
- Maintain summary constituent route inventories and test withdrawal conditions.
- Track IPv4 and IPv6 reachability independently during routing expansions.
Explanation
Correct Answer
B:Alert on low remaining LSP lifetime and repeated originator refresh failures. The control limits repetition of the described root condition: IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. During audits, confirm: The originator resumes refreshing its LSP and remote databases retain current route information.
Incorrect Answers
A: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 IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
C:Maintain summary constituent route inventories and test withdrawal conditions. This is a plausible preventive practice for a different IS-IS condition, specifically L1-to-L2 route summarization. L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain. In this scenario, however, the distinguishing issue is IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
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 IS-IS LSP lifetime expiry and the confirming observation is: The originator resumes refreshing its LSP and remote databases retain current route information.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests