Question 30
During production incident triage, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. 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.
- 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.
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Explanation
Correct Answer
A:Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors. In the live production incident, the reported evidence is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The intervention follows the governing fact that LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. Closure requires the corresponding specific confirmation: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
Incorrect Answers
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: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Its governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The narrower applicable remedy is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
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 live production incident being assessed. The present observation is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Its governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The narrower applicable remedy is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
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 live production incident being assessed. The present observation is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Its governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The narrower applicable remedy is: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
Question 31
During production incident triage, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. 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 node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
- Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
Explanation
Correct Answer
C:Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers. In the live production incident, the reported evidence is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The intervention follows the governing fact that SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. Closure requires the corresponding specific confirmation: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
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: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Its governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The narrower applicable remedy is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
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: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Its governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The narrower applicable remedy is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
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 live production incident being assessed. The present observation is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Its governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The narrower applicable remedy is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
Question 32
During production incident triage, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state.
- Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
- Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
- Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
Explanation
Correct Answer
D:Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement. In the live production incident, the reported evidence is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The intervention follows the governing fact that Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. Closure requires the corresponding specific confirmation: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.
Incorrect Answers
A:Align the hello and dead intervals on both OSPF interfaces and confirm stable neighbor state. This action was designed for the separate OSPF hello dead timer mismatch case, not the live production incident being assessed. The present observation is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Its governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The narrower applicable remedy is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
B:Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design. This action was designed for the separate DR priority zero misconception case, not the live production incident being assessed. The present observation is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Its governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The narrower applicable remedy is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
C: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 live production incident being assessed. The present observation is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Its governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The narrower applicable remedy is: Set the LAN interface passive within the relevant OSPF area while retaining the intended prefix advertisement.
Question 33
During production incident triage, engineers observe: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members.
- Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
- Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
- Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
Explanation
Correct Answer
D:Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support. In the live production incident, the reported evidence is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. The intervention follows the governing fact that Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. Closure requires the corresponding specific confirmation: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
Incorrect Answers
A:Align the MSTP region name, revision and VLAN-to-instance mapping across intended region members. This action was designed for the separate MSTP region mismatch case, not the live production incident being assessed. The present observation is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Its governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The narrower applicable remedy is: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
B:Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN. This action was designed for the separate Per-VLAN spanning-tree path case, not the live production incident being assessed. The present observation is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Its governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The narrower applicable remedy is: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
C:Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy. This action was designed for the separate Root bridge election priority case, not the live production incident being assessed. The present observation is: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. Its governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The narrower applicable remedy is: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
Question 34
During production incident triage, engineers observe: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. 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 access port to the approved VLAN and verify logical interface membership and learning.
- 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.
Explanation
Correct Answer
B:Move the access port to the approved VLAN and verify logical interface membership and learning. In the live production incident, the reported evidence is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The intervention follows the governing fact that An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. Closure requires the corresponding specific confirmation: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
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 customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. Its governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The narrower applicable remedy is: Move the access port to the approved VLAN and verify logical interface membership and learning.
C: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 customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. Its governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The narrower applicable remedy is: Move the access port to the approved VLAN and verify logical interface membership and learning.
D: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 customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. Its governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The narrower applicable remedy is: Move the access port to the approved VLAN and verify logical interface membership and learning.
Question 35
During production incident triage, engineers observe: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.
- Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
- 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
D:Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. In the live production incident, the reported evidence is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. The intervention follows the governing fact that An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. Closure requires the corresponding specific confirmation: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.
Incorrect Answers
A:Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs. This action was designed for the separate IS-IS authentication mismatch case, not the live production incident being assessed. The present observation is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. Its governing mechanism is: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The narrower applicable remedy is: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
B:Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. This action was designed for the separate IS-IS route export scope case, not the live production incident being assessed. The present observation is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. Its governing mechanism is: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The narrower applicable remedy is: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
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 live production incident being assessed. The present observation is: A newly restarted provider router is marked overloaded and therefore not used as transit despite an up adjacency; operations incorrectly call it an IP link failure. Its governing mechanism is: An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The narrower applicable remedy is: Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.
Question 36
During production incident triage, 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?
- Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
- 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.
Explanation
Correct Answer
C:Verify FEC route reachability, neighbor label advertisement and the label mapping installed for the specific destination. In the live production incident, 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
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: 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.
B: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: 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: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 live production incident 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 37
During production incident triage, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
- Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
- Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
- Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
Explanation
Correct Answer
C:Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. In the live production incident, the reported evidence is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The intervention follows the governing fact that Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. Closure requires the corresponding specific confirmation: The generated default becomes active with the expected next hop only when the qualifying contributor exists.
Incorrect Answers
A:Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. This action was designed for the separate Aggregate rejection behavior case, not the live production incident being assessed. The present observation is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Its governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The narrower applicable remedy is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Its governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The narrower applicable remedy is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
D: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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Its governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The narrower applicable remedy is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
Question 38
During production incident triage, engineers observe: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.
- 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
C:Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag. In the live production incident, the reported evidence is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The intervention follows the governing fact that Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. Closure requires the corresponding specific confirmation: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
Incorrect Answers
A:Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing. This action was designed for the separate IRB routed gateway missing case, not the live production incident being assessed. The present observation is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. Its governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The narrower applicable remedy is: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
B: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 provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. Its governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The narrower applicable remedy is: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
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-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. Its governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The narrower applicable remedy is: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
Question 39
During production incident triage, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation.
- Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
- Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
- Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
Explanation
Correct Answer
B:Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response. In the live production incident, the reported evidence is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The intervention follows the governing fact that BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. Closure requires the corresponding specific confirmation: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Incorrect Answers
A:Align the member's LACP configuration with the approved peer aggregated Ethernet group and verify partner negotiation. This action was designed for the separate LACP partner mismatch case, not the live production incident being assessed. The present observation is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Its governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The narrower applicable remedy is: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
C:Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy. This action was designed for the separate VRRP master priority failover case, not the live production incident being assessed. The present observation is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Its governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The narrower applicable remedy is: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
D:Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. This action was designed for the separate VRRP preemption oscillation case, not the live production incident being assessed. The present observation is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Its governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The narrower applicable remedy is: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.
Question 40
During production incident triage, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
- Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.
- Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.
- Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required.
Explanation
Correct Answer
A:Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context. In the live production incident, the reported evidence is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. The intervention follows the governing fact that BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. Closure requires the corresponding specific confirmation: The peer exchanges approved IPv6 routes and their next hops resolve into inet6.0 without exposing unintended prefixes.
Incorrect Answers
B:Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it. This action was designed for the separate BGP next-hop inaccessible case, not the live production incident being assessed. The present observation is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. Its governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The narrower applicable remedy is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
C:Use a controlled import policy to assign the desired BGP local preference to the selected exit paths. This action was designed for the separate BGP local preference egress case, not the live production incident being assessed. The present observation is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. Its governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The narrower applicable remedy is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
D:Compare AS paths after confirming earlier selection attributes and adjust only a justified routing policy if a different egress is required. This action was designed for the separate BGP AS-path comparison case, not the live production incident being assessed. The present observation is: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. Its governing mechanism is: BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. The narrower applicable remedy is: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests