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.
Question 211
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: An engineer sees only numeric system IDs in IS-IS neighbor and database output after introducing new routers, making incident triage difficult. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect effective level settings at the global, interface and adjacency levels.
- Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB.
- Inspect whether hostname information is advertised and resolvable for the participating IS-IS systems.
- Compare permitted IS-IS levels on both ends and their HELLO PDU categories.
Explanation
Correct Answer
C:Inspect whether hostname information is advertised and resolvable for the participating IS-IS systems. This check examines the decisive condition for IS-IS hostname visibility before any unrelated changes are made. The underlying mechanism is: Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. The confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Incorrect Answers
A: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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
B:Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Question 212
During a customer VPN change window, an HPE Juniper Networking engineer investigates this situation: An engineer sees only numeric system IDs in IS-IS neighbor and database output after introducing new routers, making incident triage difficult. Which routing or service mechanism best explains the reported behavior?
- Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
- The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe.
- IS-IS neighbors need a mutually enabled compatible level to establish adjacency on a link.
- Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs.
Explanation
Correct Answer
D:Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged. The targeted correction is: Enable supported dynamic hostname advertisement and maintain reliable naming inventory.
Incorrect Answers
A: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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
B:The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Question 213
During a core-routing migration rehearsal, an HPE Juniper Networking engineer investigates this situation: An engineer sees only numeric system IDs in IS-IS neighbor and database output after introducing new routers, making incident triage difficult. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
- Operational neighbor state shows only the intended levels after level settings are corrected.
- Unique system IDs produce distinct LSP originators and stable neighbor database entries.
- The intended level's adjacency forms and the route database populates after compatible settings.
Explanation
Correct Answer
A:Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs.
Incorrect Answers
B:Operational neighbor state shows only the intended levels after level settings are corrected. This is a plausible observed evidence for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
C:Unique system IDs produce distinct LSP originators and stable neighbor database entries. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
D: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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Question 214
During a backbone POP acceptance review, an HPE Juniper Networking engineer investigates this situation: An engineer sees only numeric system IDs in IS-IS neighbor and database output after introducing new routers, making incident triage difficult. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Disable the unneeded IS-IS level on the device or interface according to its network role.
- Enable supported dynamic hostname advertisement and maintain reliable naming inventory.
- Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart.
- Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy.
Explanation
Correct Answer
B:Enable supported dynamic hostname advertisement and maintain reliable naming inventory. The change addresses the root behavior described here: Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. Verify success with: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Incorrect Answers
A: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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
C:Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS NET system ID collision. The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
D:Enable narrow L2-to-L1 route leaking for the required service prefix using appropriate policy. This is a plausible configuration or operational fix for a different IS-IS condition, specifically L2-to-L1 route leak. Level 1 routers do not automatically know all L2 route specifics; selected L2 prefixes may require deliberate route leaking. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Question 215
During an overnight NOC investigation, an HPE Juniper Networking engineer investigates this situation: An engineer sees only numeric system IDs in IS-IS neighbor and database output after introducing new routers, making incident triage difficult. Which operational control would best prevent a recurrence of this exact failure mode?
- Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only.
- Enforce system-ID uniqueness checks in provisioning inventories.
- Keep router IDs, system IDs and hostnames mapped in operations documentation.
- Review leak policies for loops and excessive L1 state whenever remote services change.
Explanation
Correct Answer
C:Keep router IDs, system IDs and hostnames mapped in operations documentation. The control limits repetition of the described root condition: Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. During audits, confirm: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Incorrect Answers
A:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
B: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 hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
D: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 IS-IS hostname visibility and the confirming observation is: Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Question 216
During a high-availability validation, an HPE Juniper Networking engineer investigates this situation: Two cloned Junos core routers share the same IS-IS system ID and exhibit inconsistent LSP ownership even though their areas are correct. 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.
- Inspect effective level settings at the global, interface and adjacency levels.
- Compare each router's NET area addresses and the level-specific adjacency state.
- Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB.
Explanation
Correct Answer
D:Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB. This check examines the decisive condition for IS-IS NET system ID collision before any unrelated changes are made. The underlying mechanism is: The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. The confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
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 IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
B: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 IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
C: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 NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
Question 217
During a Junos routing maintenance review, an HPE Juniper Networking engineer investigates this situation: Two cloned Junos core routers share the same IS-IS system ID and exhibit inconsistent LSP ownership even though their areas are correct. Which routing or service mechanism best explains the reported behavior?
- The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe.
- Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing.
- Junos can enable both IS-IS levels by default unless one level is explicitly disabled.
- Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas.
Explanation
Correct Answer
A:The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Unique system IDs produce distinct LSP originators and stable neighbor database entries. The targeted correction is: Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart.
Incorrect Answers
B:Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. This is a plausible protocol explanation for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
C:Junos can enable both IS-IS levels by default unless one level is explicitly disabled. This is a plausible protocol explanation for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
D: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 NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
Question 218
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: Two cloned Junos core routers share the same IS-IS system ID and exhibit inconsistent LSP ownership even though their areas are correct. 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.
- Unique system IDs produce distinct LSP originators and stable neighbor database entries.
- Operational neighbor state shows only the intended levels after level settings are corrected.
- The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
Explanation
Correct Answer
B:Unique system IDs produce distinct LSP originators and stable neighbor database entries. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe.
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 IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
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 IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
D: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 NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
Question 219
During a metro aggregation incident, an HPE Juniper Networking engineer investigates this situation: Two cloned Junos core routers share the same IS-IS system ID and exhibit inconsistent LSP ownership even though their areas are correct. 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.
- Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart.
- Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation.
Explanation
Correct Answer
C:Assign a unique NET system ID to the cloned router and conduct a controlled protocol restart. The change addresses the root behavior described here: The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. Verify success with: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
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 IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
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 IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
D: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 NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
Question 220
During a managed service audit, an HPE Juniper Networking engineer investigates this situation: Two cloned Junos core routers share the same IS-IS system ID and exhibit inconsistent LSP ownership even though their areas are correct. Which operational control would best prevent a recurrence of this exact failure mode?
- 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.
- Keep router IDs, system IDs and hostnames mapped in operations documentation.
- Enforce system-ID uniqueness checks in provisioning inventories.
Explanation
Correct Answer
D:Enforce system-ID uniqueness checks in provisioning inventories. The control limits repetition of the described root condition: The system ID must uniquely identify each IS-IS router; area equality does not make duplicate system IDs safe. During audits, confirm: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
Incorrect Answers
A:Add family iso configuration to validated IS-IS circuit templates. This is a plausible preventive practice for a different IS-IS condition, specifically ISO family omission. Junos IS-IS control frames need ISO family support on participating interfaces independently of IPv4 addressing. In this scenario, however, the distinguishing issue is IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
B:Review level defaults in provisioning templates rather than assuming interfaces start at Level 1 only. This is a plausible preventive practice for a different IS-IS condition, specifically Default dual-level operation. Junos can enable both IS-IS levels by default unless one level is explicitly disabled. In this scenario, however, the distinguishing issue is IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
C:Keep router IDs, system IDs and hostnames mapped in operations documentation. This is a plausible preventive practice for a different IS-IS condition, specifically IS-IS hostname visibility. Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. In this scenario, however, the distinguishing issue is IS-IS NET system ID collision and the confirming observation is: Unique system IDs produce distinct LSP originators and stable neighbor database entries.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests