Question 90
During production incident triage, 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?
- Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
- Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
- Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
Explanation
Correct Answer
A:Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. In the live production incident, 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
B:Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. This action was designed for the separate IS-IS level-one area mismatch case, not the live production incident 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:Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design. This action was designed for the separate IS-IS level capability mismatch case, not the live production incident 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.
D: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 live production incident 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 91
During production incident triage, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
- Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
- Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
- Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.
Explanation
Correct Answer
B:Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. In the live production incident, the reported evidence is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The intervention follows the governing fact that An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. Closure requires the corresponding specific confirmation: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Incorrect Answers
A:Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. This action was designed for the separate IS-IS IPv6 reachability TLVs case, not the live production incident being assessed. The present observation is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Its governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The narrower applicable remedy is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
C:Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. This action was designed for the separate IPv6 over IPv4 transit tunnel case, not the live production incident being assessed. The present observation is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Its governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The narrower applicable remedy is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
D:Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. This action was designed for the separate ICMPv6 packet-too-big handling case, not the live production incident being assessed. The present observation is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Its governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The narrower applicable remedy is: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.
Question 92
During production incident triage, engineers observe: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. 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.
- Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
- Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.
Explanation
Correct Answer
C:Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design. In the live production incident, the reported evidence is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The intervention follows the governing fact that IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. Closure requires the corresponding specific confirmation: The session establishes using the intended loopback source and destination and stays up after a physical link fails.
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 live production incident being assessed. The present observation is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Its governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The narrower applicable remedy is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
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 live production incident being assessed. The present observation is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Its governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The narrower applicable remedy is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
D: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 live production incident being assessed. The present observation is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Its governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The narrower applicable remedy is: Configure a consistent local BGP source address and ensure both loopbacks are reachable through the IGP or static routing design.
Question 93
During production incident triage, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
- Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.
- Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
- Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
Explanation
Correct Answer
B:Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path. In the live production incident, the reported evidence is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. The intervention follows the governing fact that Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. Closure requires the corresponding specific confirmation: The chosen route becomes active and the forwarding table points to its resolved next hop; an end-to-end trace follows that path.
Incorrect Answers
A:Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. This action was designed for the separate Per-flow hash expectation case, not the live production incident being assessed. The present observation is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Its governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The narrower applicable remedy is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.
C:Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the live production incident being assessed. The present observation is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Its governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The narrower applicable remedy is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.
D:Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design. This action was designed for the separate Administrative preference overrides static case, not the live production incident being assessed. The present observation is: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. Its governing mechanism is: Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. The narrower applicable remedy is: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected path.
Question 94
During production incident triage, engineers observe: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.
- Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
- Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
- Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff.
Explanation
Correct Answer
B:Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. In the live production incident, the reported evidence is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. The intervention follows the governing fact that A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. Closure requires the corresponding specific confirmation: Initial flooding is VLAN-scoped, then subsequent frames to the learned MAC use the correct specific egress port.
Incorrect Answers
A:Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design. This action was designed for the separate MAC move instability case, not the live production incident being assessed. The present observation is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. Its governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The narrower applicable remedy is: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
C:Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. This action was designed for the separate Virtual switch instance membership case, not the live production incident being assessed. The present observation is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. Its governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The narrower applicable remedy is: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
D:Align service-provider outer VLAN tags and preserve the customer's intended inner VLAN identifiers through the Q-in-Q handoff. This action was designed for the separate Q-in-Q outer tag mismatch case, not the live production incident being assessed. The present observation is: A newly connected CE sends traffic to a destination MAC not yet learned in its VLAN, and operators mistake the initial flooding for a routing loop. Its governing mechanism is: A bridge floods unknown unicast within the broadcast domain until it learns the destination MAC's location from source traffic. The narrower applicable remedy is: Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
Question 95
During production incident triage, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
- Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
- Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
- Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port.
Explanation
Correct Answer
B:Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership. In the live production incident, the reported evidence is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. The intervention follows the governing fact that Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. Closure requires the corresponding specific confirmation: The customer MAC and VLAN appear in the correct virtual-switch instance with no leakage into default bridging context.
Incorrect Answers
A:Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. This action was designed for the separate Native VLAN mismatch case, not the live production incident being assessed. The present observation is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. Its governing mechanism is: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The narrower applicable remedy is: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
C:Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag. This action was designed for the separate Flexible VLAN tagging logical units case, not the live production incident being assessed. The present observation is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. Its governing mechanism is: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The narrower applicable remedy is: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
D:Verify unknown-unicast flooding within the VLAN, then confirm MAC learning limits later traffic to the learned egress port. This action was designed for the separate Unknown unicast flooding behavior case, not the live production incident being assessed. The present observation is: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. Its governing mechanism is: Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. The narrower applicable remedy is: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
Question 96
During production incident triage, 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?
- Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
- Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
- Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
- Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design.
Explanation
Correct Answer
D:Provision and verify a separate return LSP or alternate reverse forwarding mechanism consistent with the service design. In the live production incident, 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
A:Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. This action was designed for the separate MPLS interface not enabled case, not the live production incident 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.
B:Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. This action was designed for the separate LDP discovery and IGP mismatch case, not the live production incident 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: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 live production incident 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 97
During production incident triage, engineers observe: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
- Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
- Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
- Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
Explanation
Correct Answer
D:Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. In the live production incident, the reported evidence is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. The intervention follows the governing fact that Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. Closure requires the corresponding specific confirmation: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
Incorrect Answers
A:Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP. This action was designed for the separate Equal-cost multipath eligibility case, not the live production incident being assessed. The present observation is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Its governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The narrower applicable remedy is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
B:Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change. This action was designed for the separate Per-flow hash expectation case, not the live production incident being assessed. The present observation is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Its governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The narrower applicable remedy is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
C:Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the live production incident being assessed. The present observation is: An infrastructure route is present in inet.0 but absent from a secondary table whose applications depend on that route, and operators assume all tables automatically share entries. Its governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The narrower applicable remedy is: Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.
Question 98
During production incident triage, engineers observe: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
- Permit and verify LDP TCP 646 between the approved transport endpoints while retaining other filter controls.
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
Explanation
Correct Answer
C:Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. In the live production incident, the reported evidence is: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. The intervention follows the governing fact that Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. Closure requires the corresponding specific confirmation: The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.
Incorrect Answers
A:Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. This action was designed for the separate LDP discovery and IGP mismatch case, not the live production incident being assessed. The present observation is: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. Its governing mechanism is: Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. The narrower applicable remedy is: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
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 live production incident being assessed. The present observation is: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. Its governing mechanism is: Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. The narrower applicable remedy is: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
D: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 live production incident being assessed. The present observation is: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. Its governing mechanism is: Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. The narrower applicable remedy is: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Question 99
During production incident triage, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
- Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
- Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
Explanation
Correct Answer
A:Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. In the live production incident, the reported evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The intervention follows the governing fact that IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. Closure requires the corresponding specific confirmation: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
Incorrect Answers
B:Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. This action was designed for the separate IS-IS level-one area mismatch case, not the live production incident being assessed. The present observation is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Its governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The narrower applicable remedy is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
C:Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. This action was designed for the separate Duplicate IS-IS system ID case, not the live production incident being assessed. The present observation is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Its governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The narrower applicable remedy is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
D: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 live production incident being assessed. The present observation is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Its governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The narrower applicable remedy is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
Question 100
During production incident triage, 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?
- Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.
- Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination.
- 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.
Explanation
Correct Answer
D:Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. In the live production incident, 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:Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path. This action was designed for the separate MPLS interface not enabled case, not the live production incident 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.
B: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 live production incident 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: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 live production incident 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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests