Question 490
During production incident triage, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
- Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation.
- Monitor unknown-unicast rate together with MAC-table learning and churn.
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
Explanation
Correct Answer
B:Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The current live production incident demonstrates why this check matters: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. It monitors the mechanism that Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. The continuing safeguard should be correlated with the specific acceptance test: A same-tag packet from one customer cannot reach the other's service, while each customer's traffic traverses its own outer VLAN.
Incorrect Answers
A:Audit VLAN-to-IRB bindings and routed interfaces during new service activation. This control addresses the distinct IRB routed gateway missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The directly relevant continuing check is: Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
C:Monitor unknown-unicast rate together with MAC-table learning and churn. This control addresses the distinct Unknown unicast flooding behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The directly relevant continuing check is: Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
D:Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. This control addresses the distinct Native VLAN mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. The directly relevant continuing check is: Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The governing mechanism is: Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.
Question 491
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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Alert on MAC move spikes and review customer redundancy topology before accepting dual links.
- Review instance-to-interface memberships during virtual switching changes.
- Reconcile customer port VLAN membership against service orders after provisioning.
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
Explanation
Correct Answer
D:Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism that Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The continuing safeguard should be correlated with the specific acceptance test: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.
Incorrect Answers
A:Alert on MAC move spikes and review customer redundancy topology before accepting dual links. This control addresses the distinct MAC move instability operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
B:Review instance-to-interface memberships during virtual switching changes. This control addresses the distinct Virtual switch instance membership operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
C:Reconcile customer port VLAN membership against service orders after provisioning. This control addresses the distinct Access VLAN membership operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. The governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.
Question 492
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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Compare LDP-enabled links with IGP core interfaces after changes.
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
- Sample FEC label bindings and forwarding resolution after prefix or IGP changes.
- Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
Explanation
Correct Answer
C:Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The current live production incident demonstrates why this check matters: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. It monitors the mechanism 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. The continuing safeguard should be correlated with the specific acceptance test: The relevant FEC has a reachable next hop and valid incoming and outgoing label entries along the intended LSP.
Incorrect Answers
A:Compare LDP-enabled links with IGP core interfaces after changes. This control addresses the distinct LDP discovery and IGP mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The directly relevant continuing check is: Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The 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.
B:Track reserved and unreserved bandwidth on TE links before new LSP provisioning. This control addresses the distinct RSVP reservable bandwidth shortage operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The directly relevant continuing check is: Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The 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.
D:Rehearse RSVP protection paths during maintenance and monitor bypass readiness. This control addresses the distinct RSVP link protection plan operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An LDP session is operational, but a destination FEC lacks the usable outgoing label that an ingress PE expects to use. The directly relevant continuing check is: Sample FEC label bindings and forwarding resolution after prefix or IGP changes. The 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.
Question 493
During production incident triage, engineers observe: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate loopback reachability, source address and peer configuration during IBGP rollout.
- Verify prefix-level export allowlists during customer peering acceptance.
- Audit local-preference policy for consistency across ingress points.
- Document intended MED comparison scope and test different-neighbor-AS cases.
Explanation
Correct Answer
B:Verify prefix-level export allowlists during customer peering acceptance. The current live production incident demonstrates why this check matters: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. It monitors the mechanism that BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0. The continuing safeguard should be correlated with the specific acceptance test: The authorized prefix appears in the neighbor's received-route view and unrelated infrastructure addresses remain absent.
Incorrect Answers
A:Validate loopback reachability, source address and peer configuration during IBGP rollout. This control addresses the distinct IBGP loopback source resolution operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The directly relevant continuing check is: Verify prefix-level export allowlists during customer peering acceptance. The governing mechanism is: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
C:Audit local-preference policy for consistency across ingress points. This control addresses the distinct BGP local preference egress operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The directly relevant continuing check is: Verify prefix-level export allowlists during customer peering acceptance. The governing mechanism is: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
D:Document intended MED comparison scope and test different-neighbor-AS cases. This control addresses the distinct BGP MED comparison scope operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A route is active locally but a new eBGP customer cannot see it because the intended route has no matching BGP export acceptance. The directly relevant continuing check is: Verify prefix-level export allowlists during customer peering acceptance. The governing mechanism is: BGP route advertisements are shaped by export routing policy and eligibility rather than the mere presence of a route in inet.0.
Question 494
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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review import/export scope and route-copy audits when new routing instances are introduced.
- Track ECMP next-hop count and routing-cost drift after transport changes.
- Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
- Exercise backup-path liveness detection under downstream and local failure scenarios.
Explanation
Correct Answer
A:Review import/export scope and route-copy audits when new routing instances are introduced. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism that Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms. The continuing safeguard should be correlated with the specific acceptance test: The intended route appears in both authorized tables with the right next hop, while unrelated routes are not leaked.
Incorrect Answers
B:Track ECMP next-hop count and routing-cost drift after transport changes. This control addresses the distinct Equal-cost multipath eligibility operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Review import/export scope and route-copy audits when new routing instances are introduced. The governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
C:Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. This control addresses the distinct Per-flow hash expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Review import/export scope and route-copy audits when new routing instances are introduced. The governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
D:Exercise backup-path liveness detection under downstream and local failure scenarios. This control addresses the distinct Static backup blackhole operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Review import/export scope and route-copy audits when new routing instances are introduced. The governing mechanism is: Routing instances and RIBs are isolated unless routes are explicitly installed or copied into other tables through supported mechanisms.
Question 495
During production incident triage, engineers observe: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review passive-interface policy whenever a customer-facing segment is added.
- Document stub and normal area policies and validate expected LSA types.
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
- Baseline OSPF timer settings per transport class and alert on configuration drift.
Explanation
Correct Answer
D:Baseline OSPF timer settings per transport class and alert on configuration drift. The current live production incident demonstrates why this check matters: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. It monitors the mechanism that OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance. The continuing safeguard should be correlated with the specific acceptance test: The two interfaces report matching timers and the neighbor stays Full beyond several dead intervals.
Incorrect Answers
A:Review passive-interface policy whenever a customer-facing segment is added. This control addresses the distinct OSPF passive interface operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The directly relevant continuing check is: Baseline OSPF timer settings per transport class and alert on configuration drift. The governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
B:Document stub and normal area policies and validate expected LSA types. This control addresses the distinct Stub area external LSA expectation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The directly relevant continuing check is: Baseline OSPF timer settings per transport class and alert on configuration drift. The governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
C:Periodically compare intended and observed SPF cost paths after bandwidth changes. This control addresses the distinct OSPF metric path preference operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Junos router shows repeated OSPF Hello reception but cannot maintain a neighbor because hello and dead intervals differ across a point-to-point link. The directly relevant continuing check is: Baseline OSPF timer settings per transport class and alert on configuration drift. The governing mechanism is: OSPF adjacencies depend on compatible timer values to agree on liveness and neighbor maintenance.
Question 496
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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Use controlled startup overload and readiness criteria after routing-engine restarts.
- Stage IS-IS key rotations with overlap and rollback checks wherever supported.
- Audit IS-IS route advertisements against customer import and export inventories.
- Monitor Level 1 attached-bit or default-route availability at area boundaries.
Explanation
Correct Answer
A:Use controlled startup overload and readiness criteria after routing-engine restarts. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism that An IS-IS node in overload advertises that it should not be used for transit SPF paths even while adjacencies can be up. The continuing safeguard should be correlated with the specific acceptance test: Overload state matches the operational plan, and transit path calculations include the router only after successful readiness checks.
Incorrect Answers
B:Stage IS-IS key rotations with overlap and rollback checks wherever supported. This control addresses the distinct IS-IS authentication mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Use controlled startup overload and readiness criteria after routing-engine restarts. The 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.
C:Audit IS-IS route advertisements against customer import and export inventories. This control addresses the distinct IS-IS route export scope operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Use controlled startup overload and readiness criteria after routing-engine restarts. The 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.
D:Monitor Level 1 attached-bit or default-route availability at area boundaries. This control addresses the distinct IS-IS Level 1 exit default operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Use controlled startup overload and readiness criteria after routing-engine restarts. The 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.
Question 497
During production incident triage, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include interface family iso in standardized IS-IS provisioning templates.
- Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
- Monitor Level 1 attached-bit or default-route availability at area boundaries.
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
Explanation
Correct Answer
C:Monitor Level 1 attached-bit or default-route availability at area boundaries. The current live production incident demonstrates why this check matters: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. It monitors the mechanism that Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The continuing safeguard should be correlated with the specific acceptance test: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
Incorrect Answers
A:Include interface family iso in standardized IS-IS provisioning templates. This control addresses the distinct IS-IS ISO family missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The directly relevant continuing check is: Monitor Level 1 attached-bit or default-route availability at area boundaries. The governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
B:Baseline metric-style compatibility before area-wide IS-IS cost adjustments. This control addresses the distinct IS-IS narrow metric ceiling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The directly relevant continuing check is: Monitor Level 1 attached-bit or default-route availability at area boundaries. The governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
D:Record DIS priorities and pseudonode behavior in service-provider switching design reviews. This control addresses the distinct IS-IS DIS election surprise operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The directly relevant continuing check is: Monitor Level 1 attached-bit or default-route availability at area boundaries. The governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
Question 498
During production incident triage, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review instance-to-interface memberships during virtual switching changes.
- Alert on MAC move spikes and review customer redundancy topology before accepting dual links.
- Audit allowed VLAN sets per service and test tagged membership during changes.
- Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
Explanation
Correct Answer
C:Audit allowed VLAN sets per service and test tagged membership during changes. The current live production incident demonstrates why this check matters: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. It monitors the mechanism that A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. The continuing safeguard should be correlated with the specific acceptance test: VLAN 340 MAC learning and tagged traffic are observed on the intended trunk without accidentally carrying other customer VLANs.
Incorrect Answers
A:Review instance-to-interface memberships during virtual switching changes. This control addresses the distinct Virtual switch instance membership operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The directly relevant continuing check is: Audit allowed VLAN sets per service and test tagged membership during changes. The governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
B:Alert on MAC move spikes and review customer redundancy topology before accepting dual links. This control addresses the distinct MAC move instability operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The directly relevant continuing check is: Audit allowed VLAN sets per service and test tagged membership during changes. The governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
D:Audit VLAN-to-IRB bindings and routed interfaces during new service activation. This control addresses the distinct IRB routed gateway missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. The directly relevant continuing check is: Audit allowed VLAN sets per service and test tagged membership during changes. The governing mechanism is: A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.
Question 499
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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Compare LDP-enabled links with IGP core interfaces after changes.
- Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts.
- Check LDP session transport filtering as part of control-plane ACL reviews.
- Document expected label stacks at ingress, transit and penultimate hop for key services.
Explanation
Correct Answer
B:Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts. The current live production incident demonstrates why this check matters: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. It monitors the mechanism that SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The continuing safeguard should be correlated with the specific acceptance test: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
Incorrect Answers
A:Compare LDP-enabled links with IGP core interfaces after changes. This control addresses the distinct LDP discovery and IGP mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The directly relevant continuing check is: Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts. The governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
C:Check LDP session transport filtering as part of control-plane ACL reviews. This control addresses the distinct LDP TCP 646 establishment operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The directly relevant continuing check is: Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts. The governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
D:Document expected label stacks at ingress, transit and penultimate hop for key services. This control addresses the distinct Penultimate hop popping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The directly relevant continuing check is: Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts. The governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.
Question 500
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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Compare MSTP region configuration and digests on each addition or VLAN change.
- Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.
- Review STP root and backup priorities after device replacement or MAC changes.
- Test one-way BPDU loss and protected port-state behavior during redundancy reviews.
Explanation
Correct Answer
D:Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The current live production incident demonstrates why this check matters: 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. It monitors the mechanism that Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. The continuing safeguard should be correlated with the specific acceptance test: The protected port remains safe during the simulated BPDU loss and returns to normal after signaling is restored.
Incorrect Answers
A:Compare MSTP region configuration and digests on each addition or VLAN change. This control addresses the distinct MSTP region mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
B:Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. This control addresses the distinct Per-VLAN spanning-tree path operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
C:Review STP root and backup priorities after device replacement or MAC changes. This control addresses the distinct Root bridge election priority operational scenario rather than preventing recurrence of the live production incident. The observed problem here 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 directly relevant continuing check is: Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The governing mechanism is: Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests