Question 200
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A Junos IS-IS export policy accepts a wide aggregate ahead of a specific rejection term, unexpectedly leaking a sensitive more-specific prefix. Which operational control would best prevent a recurrence of this exact failure mode?
- Audit metric encoding and path calculation before importing large traffic-engineering costs.
- Review leak policies for loops and excessive L1 state whenever remote services change.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Run policy simulation against positive and negative test prefixes on every change.
Explanation
Correct Answer
D:Run policy simulation against positive and negative test prefixes on every change. The control limits repetition of the described root condition: Policy evaluation order can make a broad accept term preempt a later specific deny match. During audits, confirm: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Incorrect Answers
A: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 Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
B: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 Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
C:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Route-policy term ordering and the confirming observation is: The sensitive prefix no longer appears in IS-IS LSP reachability after term order is corrected.
Question 201
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: An access uplink physically passes traffic but the local interface permits only IS-IS Level 1 while the remote-facing core side permits only Level 2. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare permitted IS-IS levels on both ends and their HELLO PDU categories.
- Inspect the presence of family iso under both logical interfaces and count incoming IS-IS PDUs.
- Inspect the L1/L2 border prefix export and summarization behavior into Level 2.
- Inspect effective level settings at the global, interface and adjacency levels.
Explanation
Correct Answer
A:Compare permitted IS-IS levels on both ends and their HELLO PDU categories. This check examines the decisive condition for Level-specific adjacency mismatch before any unrelated changes are made. The underlying mechanism is: IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. The confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
Incorrect Answers
B:Inspect the presence of family iso under both logical interfaces and count incoming IS-IS PDUs. This is a plausible diagnostic check for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
C: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 Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
D: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-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
Question 202
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An access uplink physically passes traffic but the local interface permits only IS-IS Level 1 while the remote-facing core side permits only Level 2. Which routing or service mechanism best explains the reported behavior?
- Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing.
- IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link.
- L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain.
- Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
Explanation
Correct Answer
B:IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: The intended level's adjacency forms and the route database populates after compatible settings. The targeted correction is: Enable the matching level on both peer interfaces according to the topology.
Incorrect Answers
A:Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. This is a plausible protocol explanation for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
C: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 Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
D: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-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
Question 203
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An access uplink physically passes traffic but the local interface permits only IS-IS Level 1 while the remote-facing core side permits only Level 2. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The interface accepts IS-IS Hello PDUs and the expected neighbor appears after ISO family is enabled.
- The L2 route database contains the intended aggregate rather than all approved component specifics.
- The intended level's adjacency forms and the route database populates after compatible settings.
- Operational neighbor state shows only the intended levels after level settings are corrected.
Explanation
Correct Answer
C:The intended level's adjacency forms and the route database populates after compatible settings. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link.
Incorrect Answers
A:The interface accepts IS-IS Hello PDUs and the expected neighbor appears after ISO family is enabled. This is a plausible observed evidence for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
B: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 Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
D: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-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
Question 204
During a customer service restoration, an HPE Juniper Networking engineer investigates this situation: An access uplink physically passes traffic but the local interface permits only IS-IS Level 1 while the remote-facing core side permits only Level 2. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Enable family iso and the intended protocol interface settings on the transit link.
- Disable the unneeded IS-IS level on the device or interface according to its network role.
- Configure bounded summary export at the correct L1/L2 device and verify coverage.
- Enable the matching level on both peer interfaces according to the topology.
Explanation
Correct Answer
D:Enable the matching level on both peer interfaces according to the topology. The change addresses the root behavior described here: IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. Verify success with: The intended level's adjacency forms and the route database populates after compatible settings.
Incorrect Answers
A:Enable family iso and the intended protocol interface settings on the transit link. This is a plausible configuration or operational fix for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
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-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
C: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 Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
Question 205
During an edge-to-core validation, an HPE Juniper Networking engineer investigates this situation: An access uplink physically passes traffic but the local interface permits only IS-IS Level 1 while the remote-facing core side permits only Level 2. Which operational control would best prevent a recurrence of this exact failure mode?
- Precheck per-interface level disable statements on both endpoints.
- Add family iso configuration to validated IS-IS circuit templates.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Maintain summary constituent route inventories and test withdrawal conditions.
Explanation
Correct Answer
A:Precheck per-interface level disable statements on both endpoints. The control limits repetition of the described root condition: IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. During audits, confirm: The intended level's adjacency forms and the route database populates after compatible settings.
Incorrect Answers
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 Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
C:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
D: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 Level-specific adjacency mismatch and the confirming observation is: The intended level's adjacency forms and the route database populates after compatible settings.
Question 206
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: An IS-IS adjacency became unstable during a key rollover; received LSPs are rejected while interface counters show traffic. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect the presence of family iso under both logical interfaces and count incoming IS-IS PDUs.
- Compare effective IS-IS LSP authentication settings and the rollover schedule on adjacent routers.
- Compare permitted IS-IS levels on both ends and their HELLO PDU categories.
- Compare each router's NET area addresses and the level-specific adjacency state.
Explanation
Correct Answer
B:Compare effective IS-IS LSP authentication settings and the rollover schedule on adjacent routers. This check examines the decisive condition for LSP authentication disagreement before any unrelated changes are made. The underlying mechanism is: Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. The confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Incorrect Answers
A:Inspect the presence of family iso under both logical interfaces and count incoming IS-IS PDUs. This is a plausible diagnostic check for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
C: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
D: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Question 207
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: An IS-IS adjacency became unstable during a key rollover; received LSPs are rejected while interface counters show traffic. Which routing or service mechanism best explains the reported behavior?
- Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing.
- IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link.
- Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization.
- Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
Explanation
Correct Answer
C:Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level. The targeted correction is: Coordinate the key profile and change order to preserve protocol compatibility during rotation.
Incorrect Answers
A:Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. This is a plausible protocol explanation for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
B: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
D: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Question 208
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: An IS-IS adjacency became unstable during a key rollover; received LSPs are rejected while interface counters show traffic. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The interface accepts IS-IS Hello PDUs and the expected neighbor appears after ISO family is enabled.
- The intended level's adjacency forms and the route database populates after compatible settings.
- Operational neighbor state shows only the intended levels after level settings are corrected.
- Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Explanation
Correct Answer
D:Authentication failure counters drop to zero and matching LSPs are accepted on the affected level. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization.
Incorrect Answers
A:The interface accepts IS-IS Hello PDUs and the expected neighbor appears after ISO family is enabled. This is a plausible observed evidence for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
B:The intended level's adjacency forms and the route database populates after compatible settings. This is a plausible observed evidence for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
C: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Question 209
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: An IS-IS adjacency became unstable during a key rollover; received LSPs are rejected while interface counters show traffic. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Coordinate the key profile and change order to preserve protocol compatibility during rotation.
- Enable family iso and the intended protocol interface settings on the transit link.
- Enable the matching level on both peer interfaces according to the topology.
- Disable the unneeded IS-IS level on the device or interface according to its network role.
Explanation
Correct Answer
A:Coordinate the key profile and change order to preserve protocol compatibility during rotation. The change addresses the root behavior described here: Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. Verify success with: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Incorrect Answers
B:Enable family iso and the intended protocol interface settings on the transit link. This is a plausible configuration or operational fix for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
C:Enable the matching level on both peer interfaces according to the topology. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Level-specific adjacency mismatch. IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
D: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Question 210
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: An IS-IS adjacency became unstable during a key rollover; received LSPs are rejected while interface counters show traffic. Which operational control would best prevent a recurrence of this exact failure mode?
- Add family iso configuration to validated IS-IS circuit templates.
- Test adjacency and LSP acceptance across both IS-IS levels before retiring earlier keys.
- Precheck per-interface level disable statements on both endpoints.
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
Explanation
Correct Answer
B:Test adjacency and LSP acceptance across both IS-IS levels before retiring earlier keys. The control limits repetition of the described root condition: Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. During audits, confirm: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Incorrect Answers
A:Add family iso configuration to validated IS-IS circuit templates. This is a plausible preventive practice for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
D: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 LSP authentication disagreement and the confirming observation is: Authentication failure counters drop to zero and matching LSPs are accepted on the affected level.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests