Question 230
During a multisite network cutover, an HPE Juniper Networking engineer investigates this situation: Link instability causes repeated IS-IS LSP changes and high CPU usage on every router in one large routing level. 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.
- Monitor link error counters and SPF activity together instead of masking faults with large delays.
- Document protocol-level and area boundaries for each advertised prefix.
- Add family iso configuration to validated IS-IS circuit templates.
Explanation
Correct Answer
B:Monitor link error counters and SPF activity together instead of masking faults with large delays. The control limits repetition of the described root condition: Frequent link-state database changes trigger recalculation work across routers that share the level's topology. During audits, confirm: After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
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 IS-IS SPF recalculation load and the confirming observation is: After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
C:Document protocol-level and area boundaries for each advertised prefix. This is a plausible preventive practice for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is IS-IS SPF recalculation load and the confirming observation is: After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
D: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 SPF recalculation load and the confirming observation is: After physical stability and appropriate SPF pacing, route convergence occurs without repeated CPU spikes.
Question 231
During a network architecture troubleshooting workshop, an HPE Juniper Networking engineer investigates this situation: A route from one core POP to another takes different intermediate paths depending on traffic direction after asymmetric metrics were deployed. Which targeted check most directly distinguishes the likely cause before a configuration change?
- Compare IS-IS LAN priorities and the elected DIS at each supported level.
- Inspect L1 and L2 link-state databases separately at each area boundary.
- Compare directed IS-IS link metrics in both routers' advertisements and recompute SPF independently.
- Inspect the L1/L2 border prefix export and summarization behavior into Level 2.
Explanation
Correct Answer
C:Compare directed IS-IS link metrics in both routers' advertisements and recompute SPF independently. This check examines the decisive condition for IS-IS metric directionality before any unrelated changes are made. The underlying mechanism is: Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. The confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
Incorrect Answers
A:Compare IS-IS LAN priorities and the elected DIS at each supported level. This is a plausible diagnostic check for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
B:Inspect L1 and L2 link-state databases separately at each area boundary. This is a plausible diagnostic check for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
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 metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
Question 232
During an inter-POP failover test, an HPE Juniper Networking engineer investigates this situation: A route from one core POP to another takes different intermediate paths depending on traffic direction after asymmetric metrics were deployed. Which routing or service mechanism best explains the reported behavior?
- IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior.
- Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information.
- L1/L2 boundaries are the appropriate place to reduce detailed area-prefix reachability exported into the L2 domain.
- Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes.
Explanation
Correct Answer
D:Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Calculated forward and reverse next hops match the directional metric graph. The targeted correction is: Align directional costs if symmetry is required or explicitly validate the resulting asymmetric service path.
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 IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
B:Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. This is a plausible protocol explanation for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
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 IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
Question 233
During a control-plane reliability review, an HPE Juniper Networking engineer investigates this situation: A route from one core POP to another takes different intermediate paths depending on traffic direction after asymmetric metrics were deployed. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- Calculated forward and reverse next hops match the directional metric graph.
- The attached-bit signaling and the L1 default route track the intended L2 reachability.
- The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable.
- The remote area learns approved summarized prefixes without importing the source area's complete L1 topology.
Explanation
Correct Answer
A:Calculated forward and reverse next hops match the directional metric graph. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes.
Incorrect Answers
B:The attached-bit signaling and the L1 default route track the intended L2 reachability. This is a plausible observed evidence for a different IS-IS condition, specifically L1/L2 ATT default direction. The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
C:The expected DIS originates the pseudonode LSP and the LAN neighbor set is stable. This is a plausible observed evidence for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
D:The remote area learns approved summarized prefixes without importing the source area's complete L1 topology. This is a plausible observed evidence for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
Question 234
During a service-provider escalation, an HPE Juniper Networking engineer investigates this situation: A route from one core POP to another takes different intermediate paths depending on traffic direction after asymmetric metrics were deployed. Which response or focused corrective action best addresses this situation without changing unrelated components?
- Correct the L1/L2 area exit and attached-bit advertisement conditions rather than injecting unrelated host routes.
- Align directional costs if symmetry is required or explicitly validate the resulting asymmetric service path.
- Set the intended LAN DIS priority consistently for the planned level and verify election state.
- Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability.
Explanation
Correct Answer
B:Align directional costs if symmetry is required or explicitly validate the resulting asymmetric service path. The change addresses the root behavior described here: Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. Verify success with: Calculated forward and reverse next hops match the directional metric graph.
Incorrect Answers
A:Correct the L1/L2 area exit and attached-bit advertisement conditions rather than injecting unrelated host routes. This is a plausible configuration or operational fix for a different IS-IS condition, specifically L1/L2 ATT default direction. The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
C:Set the intended LAN DIS priority consistently for the planned level and verify election state. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Designated IS election on LAN. IS-IS elects a DIS to represent the LAN as a pseudonode, with priority and tie-breaking rules that differ from OSPF DR behavior. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
D:Use L1/L2 routing and explicit prefix leaking or summaries for needed interarea reachability. This is a plausible configuration or operational fix for a different IS-IS condition, specifically LSP flooding scope at levels. Level 1 LSPs are flooded within their area while Level 2 routing carries interarea reachability information. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
Question 235
During a new PE-router service turn-up, an HPE Juniper Networking engineer investigates this situation: A route from one core POP to another takes different intermediate paths depending on traffic direction after asymmetric metrics were deployed. Which operational control would best prevent a recurrence of this exact failure mode?
- Include removal of each L1/L2 border router in resilience exercises.
- Monitor attached-bit and default-route behavior when L2 isolation is simulated.
- Model both travel directions in planned metric policy reviews.
- Audit pseudonode LSP origin after LAN membership changes.
Explanation
Correct Answer
C:Model both travel directions in planned metric policy reviews. The control limits repetition of the described root condition: Shortest-path calculation uses each router's advertised outbound link metrics, so intentionally asymmetric metrics can yield asymmetric routes. During audits, confirm: Calculated forward and reverse next hops match the directional metric graph.
Incorrect Answers
A:Include removal of each L1/L2 border router in resilience exercises. This is a plausible preventive practice for a different IS-IS condition, specifically Level 2 backbone continuity. Level 1 routers depend on Level 1/Level 2 routers and the Level 2 topology for off-area reachability. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
B:Monitor attached-bit and default-route behavior when L2 isolation is simulated. This is a plausible preventive practice for a different IS-IS condition, specifically L1/L2 ATT default direction. The IS-IS attached bit advertises that an L1/L2 router can provide exit reachability for an L1 area when conditions are met. In this scenario, however, the distinguishing issue is IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
D: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 IS-IS metric directionality and the confirming observation is: Calculated forward and reverse next hops match the directional metric graph.
Question 236
During a backbone POP acceptance review, 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 targeted check most directly distinguishes the likely cause before a configuration change?
- Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator.
- Compare each router's NET area addresses and the level-specific adjacency state.
- Compare the six-byte system-ID portions of each router's ISO NET and origin IDs in the LSDB.
- Inspect startup overload-bit behavior and readiness criteria for transit use.
Explanation
Correct Answer
D:Inspect startup overload-bit behavior and readiness criteria for transit use. This check examines the decisive condition for IS-IS overload after startup before any unrelated changes are made. The underlying mechanism is: Overload-bit control can keep the node from being selected as a transit until the control and forwarding planes are ready. The confirming observation is: Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
Incorrect Answers
A:Inspect LSP lifetime, refresh timing and the absence of new fragments from the originator. This is a plausible diagnostic check for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IS-IS overload 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:Compare each router's NET area addresses and the level-specific adjacency state. This is a plausible diagnostic check for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload 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: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 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 237
During an overnight NOC investigation, 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 routing or service mechanism best explains the reported behavior?
- Overload-bit control can keep the node from being selected as a transit until the control and forwarding planes are ready.
- IS-IS link-state reachability requires periodic refresh before remaining lifetime expires.
- Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas.
- Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs.
Explanation
Correct Answer
A:Overload-bit control can keep the node from being selected as a transit until the control and forwarding planes are ready. This is the causal rule that fits the observed state, not just a correlated symptom. To distinguish it from other failures, look for: Traffic avoids the node while overload is set and uses it only after the readiness condition is met. The targeted correction is: Apply a bounded startup overload policy and remove it after validated forwarding readiness.
Incorrect Answers
B:IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. This is a plausible protocol explanation for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IS-IS overload 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:Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. This is a plausible protocol explanation for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload 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.
D:Dynamic hostname information can provide human-readable identifiers, but protocol reachability still uses system IDs. This is a plausible protocol explanation 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 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 238
During a customer service restoration, 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. After the appropriate response, which observation would best confirm that the stated service condition is handled correctly?
- The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area.
- Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
- The originator resumes refreshing its LSP and remote databases retain current route information.
- Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged.
Explanation
Correct Answer
B:Traffic avoids the node while overload is set and uses it only after the readiness condition is met. This observation directly tests the fault hypothesis rather than simply showing that a session or interface exists. The underlying reason is: Overload-bit control can keep the node from being selected as a transit until the control and forwarding planes are ready.
Incorrect Answers
A:The Level 1 state comes up when compatible area identifiers are configured for routers expected to share an area. This is a plausible observed evidence for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload 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:The originator resumes refreshing its LSP and remote databases retain current route information. This is a plausible observed evidence for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IS-IS overload 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.
D:Neighbor output maps each system ID to the expected device name while link-state convergence remains unchanged. This is a plausible observed evidence 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 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 239
During an edge-to-core 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 response or focused corrective action best addresses this situation without changing unrelated components?
- Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation.
- Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB.
- Apply a bounded startup overload policy and remove it after validated forwarding readiness.
- Coordinate the key profile and change order to preserve protocol compatibility during rotation.
Explanation
Correct Answer
C:Apply a bounded startup overload policy and remove it after validated forwarding readiness. The change addresses the root behavior described here: Overload-bit control can keep the node from being selected as a transit until the control and forwarding planes are ready. Verify success with: Traffic avoids the node while overload is set and uses it only after the readiness condition is met.
Incorrect Answers
A:Align the area portion of the NET for intended Level 1 neighbors or keep only correct interarea Level 2 operation. This is a plausible configuration or operational fix for a different IS-IS condition, specifically Level 1 area-address mismatch. Level 1 adjacencies require compatible common area identity, while Level 2 supports connectivity between areas. In this scenario, however, the distinguishing issue is IS-IS overload 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:Restore reliable LSP generation and flooding rather than pinning obsolete routes in the RIB. This is a plausible configuration or operational fix for a different IS-IS condition, specifically IS-IS LSP lifetime expiry. IS-IS link-state reachability requires periodic refresh before remaining lifetime expires. In this scenario, however, the distinguishing issue is IS-IS overload 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.
D:Coordinate the key profile and change order to preserve protocol compatibility during rotation. This is a plausible configuration or operational fix for a different IS-IS condition, specifically LSP authentication disagreement. Incompatible authentication for IS-IS protocol data units can prevent trusted link-state database synchronization. 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 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.
Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests