Question 560
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
- Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
- Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Explanation
Correct Answer
A:Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. In the controlled acceptance rehearsal, the reported evidence is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The intervention follows the governing fact that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. Closure requires the corresponding specific confirmation: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.
Incorrect Answers
B:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
C:Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. This action was designed for the separate IS-IS Level 1 exit default case, not the controlled acceptance rehearsal being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
D:Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. This action was designed for the separate IS-IS overload-state recovery case, not the controlled acceptance rehearsal being assessed. The present observation is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Its governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The narrower applicable remedy is: Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
Question 561
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
- Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
- Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
- Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
Explanation
Correct Answer
B:Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state. In the controlled acceptance rehearsal, the reported evidence is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The intervention follows the governing fact that OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. Closure requires the corresponding specific confirmation: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Incorrect Answers
A:Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. This action was designed for the separate OSPF metric path preference case, not the controlled acceptance rehearsal being assessed. The present observation is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Its governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The narrower applicable remedy is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
C:Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. This action was designed for the separate OSPF authentication key mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Its governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The narrower applicable remedy is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
D:Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. This action was designed for the separate OSPF export policy omission case, not the controlled acceptance rehearsal being assessed. The present observation is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Its governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The narrower applicable remedy is: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.
Question 562
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
- Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
- Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
Explanation
Correct Answer
B:Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction. In the controlled acceptance rehearsal, the reported evidence is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. The intervention follows the governing fact that A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. Closure requires the corresponding specific confirmation: The observed label stack and forwarding path match the documented shortest path or the specified explicit segment list.
Incorrect Answers
A:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Its governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The narrower applicable remedy is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
C:Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. This action was designed for the separate RSVP reservable bandwidth shortage case, not the controlled acceptance rehearsal being assessed. The present observation is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Its governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The narrower applicable remedy is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
D:Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. This action was designed for the separate RSVP link protection plan case, not the controlled acceptance rehearsal being assessed. The present observation is: An SR-MPLS headend expects node-SID traffic to follow the IGP shortest path, but an operator assumes a node SID can force an arbitrary link sequence without further segments. Its governing mechanism is: A node SID typically steers toward its destination using shortest-path IGP forwarding, while explicit adjacency segments can add finer path constraints. The narrower applicable remedy is: Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
Question 563
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
- Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
- Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction.
- Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
Explanation
Correct Answer
A:Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. In the controlled acceptance rehearsal, the reported evidence is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The intervention follows the governing fact that LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. Closure requires the corresponding specific confirmation: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
Incorrect Answers
B:Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. This action was designed for the separate RSVP link protection plan case, not the controlled acceptance rehearsal being assessed. The present observation is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. Its governing mechanism is: LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. The narrower applicable remedy is: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
C:Use appropriate segment choices or a supported SR policy when explicit path steering is required, rather than treating a node SID as an exact-hop instruction. This action was designed for the separate SR-MPLS node-SID shortest path case, not the controlled acceptance rehearsal being assessed. The present observation is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. Its governing mechanism is: LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. The narrower applicable remedy is: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
D:Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress. This action was designed for the separate Explicit-null forwarding case, not the controlled acceptance rehearsal being assessed. The present observation is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. Its governing mechanism is: LDP maps forwarding equivalence classes to labels learned from the downstream next hop; a session can be up without an applicable mapping for every FEC. The narrower applicable remedy is: Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
Question 564
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
- Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
- Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Explanation
Correct Answer
A:Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design. In the controlled acceptance rehearsal, the reported evidence is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The intervention follows the governing fact that RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. Closure requires the corresponding specific confirmation: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
Incorrect Answers
B:Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls. This action was designed for the separate LDP TCP 646 establishment case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Its governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The narrower applicable remedy is: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
C:Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. This action was designed for the separate Incoming label missing in LFIB case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Its governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The narrower applicable remedy is: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
D:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Its governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The narrower applicable remedy is: Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
Question 565
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub.
- Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
- Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection.
- Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
Explanation
Correct Answer
B:Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions. In the controlled acceptance rehearsal, the reported evidence is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The intervention follows the governing fact that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. Closure requires the corresponding specific confirmation: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.
Incorrect Answers
A:Validate stub-area design and use the intended summary or default-route strategy rather than expecting type-5 LSAs in the stub. This action was designed for the separate Stub area external LSA expectation case, not the controlled acceptance rehearsal being assessed. The present observation is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Its governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The narrower applicable remedy is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
C:Correct the relevant OSPF interface costs in line with the approved traffic-engineering design and validate SPF selection. This action was designed for the separate OSPF metric path preference case, not the controlled acceptance rehearsal being assessed. The present observation is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Its governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The narrower applicable remedy is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
D:Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF. This action was designed for the separate OSPF LSDB discrepancy case, not the controlled acceptance rehearsal being assessed. The present observation is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Its governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The narrower applicable remedy is: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.
Question 566
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design.
- Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes.
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
- Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
Explanation
Correct Answer
D:Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy. In the controlled acceptance rehearsal, the reported evidence is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The intervention follows the governing fact that BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. Closure requires the corresponding specific confirmation: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
Incorrect Answers
A:Validate Junos MED comparison rules and the contributing neighbor AS, then apply an explicit policy only if required by traffic design. This action was designed for the separate BGP MED comparison scope case, not the controlled acceptance rehearsal being assessed. The present observation is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Its governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The narrower applicable remedy is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
B:Apply an export policy that permits precisely the required public prefix to the designated neighbor and rejects unrelated routes. This action was designed for the separate BGP export policy omission case, not the controlled acceptance rehearsal being assessed. The present observation is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Its governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The narrower applicable remedy is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
C:Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes. This action was designed for the separate BGP import policy leak case, not the controlled acceptance rehearsal being assessed. The present observation is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Its governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The narrower applicable remedy is: Inspect negotiated hold time, keepalive behavior and actual packet loss before applying an agreed stable timer policy.
Question 567
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
- Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
- Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
Explanation
Correct Answer
D:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. In the controlled acceptance rehearsal, the reported evidence is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The intervention follows the governing fact that The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. Closure requires the corresponding specific confirmation: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.
Incorrect Answers
A:Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the controlled acceptance rehearsal being assessed. The present observation is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Its governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The narrower applicable remedy is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
B:Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. This action was designed for the separate IS-IS Level 1 exit default case, not the controlled acceptance rehearsal being assessed. The present observation is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Its governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The narrower applicable remedy is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
C:Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. This action was designed for the separate IS-IS LSP lifetime anomaly case, not the controlled acceptance rehearsal being assessed. The present observation is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Its governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The narrower applicable remedy is: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
Question 568
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
- Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
- Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
- Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Explanation
Correct Answer
C:Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone. In the controlled acceptance rehearsal, the reported evidence is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The intervention follows the governing fact that Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. Closure requires the corresponding specific confirmation: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
Incorrect Answers
A:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Its governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The narrower applicable remedy is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
B:Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information. This action was designed for the separate IS-IS LSP lifetime anomaly case, not the controlled acceptance rehearsal being assessed. The present observation is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Its governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The narrower applicable remedy is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
D:Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. This action was designed for the separate IS-IS overload-state recovery case, not the controlled acceptance rehearsal being assessed. The present observation is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Its governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The narrower applicable remedy is: Ensure appropriate L1/L2 router connectivity and default-reachability design toward the Level 2 backbone.
Question 569
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
- Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
- Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
- Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
Explanation
Correct Answer
B:Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. In the controlled acceptance rehearsal, the reported evidence is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. The intervention follows the governing fact that RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. Closure requires the corresponding specific confirmation: The bypass LSP is operational before fault injection and protected traffic follows the bypass after the link is disabled.
Incorrect Answers
A:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Its governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The narrower applicable remedy is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
C:Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress. This action was designed for the separate Explicit-null forwarding case, not the controlled acceptance rehearsal being assessed. The present observation is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Its governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The narrower applicable remedy is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
D:Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers. This action was designed for the separate Segment routing SID advertisement case, not the controlled acceptance rehearsal being assessed. The present observation is: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. Its governing mechanism is: RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. The narrower applicable remedy is: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.
Question 570
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
- Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Explanation
Correct Answer
C:Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. In the controlled acceptance rehearsal, the reported evidence is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The intervention follows the governing fact that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. Closure requires the corresponding specific confirmation: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Incorrect Answers
A:Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. This action was designed for the separate Missing LDP FEC label mapping case, not the controlled acceptance rehearsal being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
B:Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC. This action was designed for the separate Incoming label missing in LFIB case, not the controlled acceptance rehearsal being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
D:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Its governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The narrower applicable remedy is: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests