Question 10
During production incident triage, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. 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.
- Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.
- Set the correct point-to-point OSPF interface type where supported and aligned at both ends.
- Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
Explanation
Correct Answer
D:Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover. In the live production incident, the reported evidence is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The intervention follows the governing fact that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. Closure requires the corresponding specific confirmation: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.
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 live production incident being assessed. The present observation is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Its governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The narrower applicable remedy is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
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: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Its governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The narrower applicable remedy is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
C:Set the correct point-to-point OSPF interface type where supported and aligned at both ends. This action was designed for the separate Point-to-point OSPF network type case, not the live production incident being assessed. The present observation is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Its governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The narrower applicable remedy is: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
Question 11
During production incident triage, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
- 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.
- Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
Explanation
Correct Answer
A:Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress. In the live production incident, the reported evidence is: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The intervention follows the governing fact that Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. Closure requires the corresponding specific confirmation: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.
Incorrect Answers
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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Its governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The narrower applicable remedy is: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Its governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The narrower applicable remedy is: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Its governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The narrower applicable remedy is: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.
Question 12
During production incident triage, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
- Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.
- Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
- Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
Explanation
Correct Answer
A:Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. In the live production incident, the reported evidence is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. The intervention follows the governing fact that A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. Closure requires the corresponding specific confirmation: The aggregate appears as an active route with contributing prefixes shown, and the permitted summary is advertised to the intended peer.
Incorrect Answers
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: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Its governing mechanism is: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The narrower applicable remedy is: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
C:Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. This action was designed for the separate Filter-based forwarding classification case, not the live production incident being assessed. The present observation is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Its governing mechanism is: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The narrower applicable remedy is: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
D:Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. This action was designed for the separate Filter policy overmatch case, not the live production incident being assessed. The present observation is: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. Its governing mechanism is: A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. The narrower applicable remedy is: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
Question 13
During production incident triage, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. 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.
- Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
- Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
Explanation
Correct Answer
A:Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. In the live production incident, the reported evidence is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. The intervention follows the governing fact that IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. Closure requires the corresponding specific confirmation: The relevant IPv6 reachability TLVs are present and remote IPv6 prefixes become active in inet6.0.
Incorrect Answers
B:Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable. This action was designed for the separate IPv6 static link-local next hop case, not the live production incident being assessed. The present observation is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Its governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The narrower applicable remedy is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
C:Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. This action was designed for the separate IPv6 BGP NLRI family omitted case, not the live production incident being assessed. The present observation is: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Its governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The narrower applicable remedy is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
D: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: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. Its governing mechanism is: IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. The narrower applicable remedy is: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
Question 14
During production incident triage, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. 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.
- Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.
- Move the access port to the approved VLAN and verify logical interface membership and learning.
- Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
Explanation
Correct Answer
D:Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. In the live production incident, the reported evidence is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. The intervention follows the governing fact that Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. Closure requires the corresponding specific confirmation: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
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: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. Its governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The narrower applicable remedy is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
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: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. Its governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The narrower applicable remedy is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
C:Move the access port to the approved VLAN and verify logical interface membership and learning. This action was designed for the separate Access VLAN membership case, not the live production incident being assessed. The present observation is: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. Its governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The narrower applicable remedy is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.
Question 15
During production incident triage, engineers observe: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. 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.
- Set a lower appropriate bridge priority for the approved root switch and validate the redundant root hierarchy.
- Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.
- Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
Explanation
Correct Answer
D:Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition. In the live production incident, the reported evidence is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. The intervention follows the governing fact that RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. Closure requires the corresponding specific confirmation: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
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 redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Its governing mechanism is: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The narrower applicable remedy is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
B: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 redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Its governing mechanism is: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The narrower applicable remedy is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
C:Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted. This action was designed for the separate Root protection against rogue core case, not the live production incident being assessed. The present observation is: A redundant link should resume traffic when the active path fails, but the switch stays blocked because engineers confuse RSTP alternate and edge port roles. Its governing mechanism is: RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The narrower applicable remedy is: Validate RSTP root and alternate port roles and point-to-point link conditions before testing rapid alternate-port transition.
Question 16
During production incident triage, engineers observe: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. 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.
- Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.
- Check VRRP virtual-address and group consistency, effective priority and owner/preemption conditions, then restore the intended priority policy.
- Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
Explanation
Correct Answer
D:Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. In the live production incident, the reported evidence is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. The intervention follows the governing fact that GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. Closure requires the corresponding specific confirmation: A controlled RE switchover maintains data-plane forwarding and routing neighbor continuity according to the selected supported feature set.
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 dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. Its governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The narrower applicable remedy is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
B:Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity. This action was designed for the separate LAG member imbalance after failure case, not the live production incident being assessed. The present observation is: A dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. Its governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The narrower applicable remedy is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
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 dual-Routing-Engine chassis sustains packet forwarding during a switchover with GRES but some routing adjacencies reset; operators expected GRES alone to preserve protocol state. Its governing mechanism is: GRES preserves interface and kernel forwarding state across Routing Engine switchover but does not by itself preserve routing protocol sessions. The narrower applicable remedy is: Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
Question 17
During production incident triage, engineers observe: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. 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.
- Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.
- Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.
- Correct the actual transport MTU mismatch across the link, then validate database description exchange.
Explanation
Correct Answer
D:Correct the actual transport MTU mismatch across the link, then validate database description exchange. In the live production incident, the reported evidence is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. The intervention follows the governing fact that OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. Closure requires the corresponding specific confirmation: Both sides report compatible MTU and move through Exchange to Full with a synchronized LSDB.
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: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. Its governing mechanism is: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The narrower applicable remedy is: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
B: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: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. Its governing mechanism is: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The narrower applicable remedy is: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
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 live production incident being assessed. The present observation is: Two routers become OSPF neighbors but repeatedly remain in ExStart or Exchange after a transport change that reduced interface MTU on one end. Its governing mechanism is: OSPF database description negotiation checks interface compatibility; mismatched MTU can prevent the adjacency from progressing to Full. The narrower applicable remedy is: Correct the actual transport MTU mismatch across the link, then validate database description exchange.
Question 18
During production incident triage, engineers observe: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.
- Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.
- 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.
Explanation
Correct Answer
C:Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN. In the live production incident, the reported evidence is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The intervention follows the governing fact that VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. Closure requires the corresponding specific confirmation: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.
Incorrect Answers
A:Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment. This action was designed for the separate Unexpected BPDU on edge port case, not the live production incident being assessed. The present observation is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Its governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The narrower applicable remedy is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
B:Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support. This action was designed for the separate Loop protection after BPDU loss case, not the live production incident being assessed. The present observation is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Its governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The narrower applicable remedy is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
D: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: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Its governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The narrower applicable remedy is: Choose and configure an appropriate supported per-VLAN STP approach with documented root assignment for each VLAN.
Question 19
During production incident triage, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation.
- Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
- Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
- Investigate LSP flooding and neighbor stability, repairing the actual control-plane loss and refreshing current topology information.
Explanation
Correct Answer
C:Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state. In the live production incident, the reported evidence is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. The intervention follows the governing fact that IS-IS relies on a unique system ID to identify LSP originators and topology nodes. Closure requires the corresponding specific confirmation: The nodes appear with distinct system IDs and no repeated conflicting LSP originator entries in the database.
Incorrect Answers
A:Enable the supported ISO protocol family on the participating Junos interface and validate IS-IS neighbor formation. This action was designed for the separate IS-IS ISO family missing case, not the live production incident being assessed. The present observation is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Its governing mechanism is: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The narrower applicable remedy is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
B: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: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Its governing mechanism is: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The narrower applicable remedy is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
D: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 live production incident being assessed. The present observation is: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. Its governing mechanism is: IS-IS relies on a unique system ID to identify LSP originators and topology nodes. The narrower applicable remedy is: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.
Question 20
During production incident triage, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?
- Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
- Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.
- Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.
- Validate both route metrics and platform multipath configuration so that two intended next hops are eligible for ECMP.
Explanation
Correct Answer
A:Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path. In the live production incident, the reported evidence is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. The intervention follows the governing fact that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. Closure requires the corresponding specific confirmation: Matched and unmatched packet samples increment their intended counters and resolve to the expected respective routing tables.
Incorrect Answers
B: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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
C:Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement. This action was designed for the separate Aggregate route contribution case, not the live production incident being assessed. The present observation is: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
D: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: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. Its governing mechanism is: Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. The narrower applicable remedy is: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests