Question 940
During a controlled acceptance rehearsal of the same defect on a separate test network, 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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Monitor root-protection violations and keep the intended root location documented.
- Audit edge-port BPDU protection and alerts during customer endpoint changes.
- Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.
- Exercise RSTP role transition in planned failover tests.
Explanation
Correct Answer
D:Exercise RSTP role transition in planned failover tests. The current controlled acceptance rehearsal demonstrates why this check matters: 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. It monitors the mechanism that RSTP holds alternate paths in a discarding state to avoid loops, then can rapidly transition a suitable alternate after the active path fails. The continuing safeguard should be correlated with the specific acceptance test: A controlled root-port failure causes the expected alternate port to forward without creating a bridging loop.
Incorrect Answers
A:Monitor root-protection violations and keep the intended root location documented. This control addresses the distinct Root protection against rogue core operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Exercise RSTP role transition in planned failover tests. The 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.
B:Audit edge-port BPDU protection and alerts during customer endpoint changes. This control addresses the distinct Unexpected BPDU on edge port operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Exercise RSTP role transition in planned failover tests. The 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.
C: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 controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Exercise RSTP role transition in planned failover tests. The 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.
Question 941
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
- Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up.
- Review instance-to-interface memberships during virtual switching changes.
- Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation.
Explanation
Correct Answer
D:Maintain unique outer service identifiers for separate tenants and test cross-tenant isolation. The current controlled acceptance rehearsal 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: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 controlled acceptance rehearsal. 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.
B:Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. This control addresses the distinct Flexible VLAN tagging logical units operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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: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 controlled acceptance rehearsal. 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 942
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths.
- Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer.
- Check IPv6 static routes for proper next-hop scope after link renumbering.
- Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links.
Explanation
Correct Answer
C:Check IPv6 static routes for proper next-hop scope after link renumbering. The current controlled acceptance rehearsal demonstrates why this check matters: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. It monitors the mechanism that An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. The continuing safeguard should be correlated with the specific acceptance test: The IPv6 route is active in inet6.0 with the correct interface-scoped next hop and test traffic reaches the peer.
Incorrect Answers
A:Exercise large-packet IPv6 and PMTU tests through tunneled or low-MTU paths. This control addresses the distinct ICMPv6 packet-too-big handling operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The directly relevant continuing check is: Check IPv6 static routes for proper next-hop scope after link renumbering. The governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
B:Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. This control addresses the distinct IPv6 BGP NLRI family omitted operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The directly relevant continuing check is: Check IPv6 static routes for proper next-hop scope after link renumbering. The governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
D:Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links. This control addresses the distinct OSPFv3 neighbor uses link-local operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. The directly relevant continuing check is: Check IPv6 static routes for proper next-hop scope after link renumbering. The governing mechanism is: An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.
Question 943
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Review STP root and backup priorities after device replacement or MAC changes.
- Exercise RSTP role transition in planned failover tests.
- Test one-way BPDU loss and protected port-state behavior during redundancy reviews.
- Monitor root-protection violations and keep the intended root location documented.
Explanation
Correct Answer
C:Test one-way BPDU loss and protected port-state behavior during redundancy reviews. The current controlled acceptance rehearsal 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: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 controlled acceptance rehearsal. 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:Exercise RSTP role transition in planned failover tests. This control addresses the distinct RSTP alternate port activation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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.
D:Monitor root-protection violations and keep the intended root location documented. This control addresses the distinct Root protection against rogue core operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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.
Question 944
During a controlled acceptance rehearsal of the same defect on a separate test network, 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 ongoing validation or operating control most directly prevents this specific failure from recurring?
- Baseline BFD timer settings by platform and monitor false-flap trends.
- Monitor VRRP failover and preempt events correlated to upstream route health.
- Test control-plane and data-plane continuity separately under planned RE switchovers.
- Audit NSR state and replicate routing databases before maintenance windows.
Explanation
Correct Answer
A:Baseline BFD timer settings by platform and monitor false-flap trends. The current controlled acceptance rehearsal demonstrates why this check matters: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. It monitors the mechanism that BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The continuing safeguard should be correlated with the specific acceptance test: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Incorrect Answers
B:Monitor VRRP failover and preempt events correlated to upstream route health. This control addresses the distinct VRRP preemption oscillation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
C:Test control-plane and data-plane continuity separately under planned RE switchovers. This control addresses the distinct GRES forwarding versus routing continuity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
D:Audit NSR state and replicate routing databases before maintenance windows. This control addresses the distinct NSR backup routing synchronization operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
Question 945
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate planned VRRP priorities and failover behavior after router maintenance.
- Audit NSR state and replicate routing databases before maintenance windows.
- Monitor VRRP failover and preempt events correlated to upstream route health.
- Baseline BFD timer settings by platform and monitor false-flap trends.
Explanation
Correct Answer
B:Audit NSR state and replicate routing databases before maintenance windows. The current controlled acceptance rehearsal demonstrates why this check matters: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. It monitors the mechanism that NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers. The continuing safeguard should be correlated with the specific acceptance test: The standby RE has synchronized routing state and peer sessions stay established through a tested RE switch.
Incorrect Answers
A:Validate planned VRRP priorities and failover behavior after router maintenance. This control addresses the distinct VRRP master priority failover operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The directly relevant continuing check is: Audit NSR state and replicate routing databases before maintenance windows. The governing mechanism is: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
C:Monitor VRRP failover and preempt events correlated to upstream route health. This control addresses the distinct VRRP preemption oscillation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The directly relevant continuing check is: Audit NSR state and replicate routing databases before maintenance windows. The governing mechanism is: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
D:Baseline BFD timer settings by platform and monitor false-flap trends. This control addresses the distinct BFD detect timer too aggressive operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A redundant RE pair has GRES enabled but lacks stateful routing protocol synchronization, so an unplanned switchover causes avoidable routing churn. The directly relevant continuing check is: Audit NSR state and replicate routing databases before maintenance windows. The governing mechanism is: NSR runs routing protocol state on the backup Routing Engine so failover can preserve adjacencies without depending on graceful-restart helpers.
Question 946
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Monitor member count, error rate and utilization separately from AE state.
- Audit NSR state and replicate routing databases before maintenance windows.
- Track graceful-restart capabilities and maintenance test outcomes for every relevant peer.
- Monitor VRRP failover and preempt events correlated to upstream route health.
Explanation
Correct Answer
A:Monitor member count, error rate and utilization separately from AE state. The current controlled acceptance rehearsal demonstrates why this check matters: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. It monitors the mechanism that A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. The continuing safeguard should be correlated with the specific acceptance test: The active member count and per-link utilization match service design, and the aggregate handles representative traffic without excessive drops.
Incorrect Answers
B:Audit NSR state and replicate routing databases before maintenance windows. This control addresses the distinct NSR backup routing synchronization operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The directly relevant continuing check is: Monitor member count, error rate and utilization separately from AE state. The governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
C:Track graceful-restart capabilities and maintenance test outcomes for every relevant peer. This control addresses the distinct Graceful restart helper expectations operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The directly relevant continuing check is: Monitor member count, error rate and utilization separately from AE state. The governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
D:Monitor VRRP failover and preempt events correlated to upstream route health. This control addresses the distinct VRRP preemption oscillation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. The directly relevant continuing check is: Monitor member count, error rate and utilization separately from AE state. The governing mechanism is: A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.
Question 947
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit edge-port BPDU protection and alerts during customer endpoint changes.
- Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.
- Monitor root-protection violations and keep the intended root location documented.
- Test one-way BPDU loss and protected port-state behavior during redundancy reviews.
Explanation
Correct Answer
C:Monitor root-protection violations and keep the intended root location documented. The current controlled acceptance rehearsal demonstrates why this check matters: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. It monitors the mechanism that Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The continuing safeguard should be correlated with the specific acceptance test: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.
Incorrect Answers
A:Audit edge-port BPDU protection and alerts during customer endpoint changes. This control addresses the distinct Unexpected BPDU on edge port operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The directly relevant continuing check is: Monitor root-protection violations and keep the intended root location documented. The governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
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 controlled acceptance rehearsal. The observed problem here is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The directly relevant continuing check is: Monitor root-protection violations and keep the intended root location documented. The governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
D:Test one-way BPDU loss and protected port-state behavior during redundancy reviews. This control addresses the distinct Loop protection after BPDU loss operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The directly relevant continuing check is: Monitor root-protection violations and keep the intended root location documented. The governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
Question 948
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Maintain a documented martian and bogon-address policy aligned with assigned network ranges.
- Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
- Check classifier counters, filter attachment and target-table availability after changes.
- Exercise backup-path liveness detection under downstream and local failure scenarios.
Explanation
Correct Answer
C:Check classifier counters, filter attachment and target-table availability after changes. The current controlled acceptance rehearsal demonstrates why this check matters: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. It monitors the mechanism that Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. The continuing safeguard should be correlated with the specific acceptance test: Counters for the targeted match increment, only the intended traffic uses the alternate next hop, and unmatched traffic stays on its original path.
Incorrect Answers
A:Maintain a documented martian and bogon-address policy aligned with assigned network ranges. This control addresses the distinct Martian-address acceptance operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The directly relevant continuing check is: Check classifier counters, filter attachment and target-table availability after changes. The governing mechanism is: Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
B: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 controlled acceptance rehearsal. The observed problem here is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The directly relevant continuing check is: Check classifier counters, filter attachment and target-table availability after changes. The governing mechanism is: Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
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 controlled acceptance rehearsal. The observed problem here is: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. The directly relevant continuing check is: Check classifier counters, filter attachment and target-table availability after changes. The governing mechanism is: Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.
Question 949
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit external route export allowlists against approved customer prefixes.
- Reserve router IDs in an inventory and audit uniqueness during device provisioning.
- Review passive-interface policy whenever a customer-facing segment is added.
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
Explanation
Correct Answer
D:Periodically compare intended and observed SPF cost paths after bandwidth changes. The current controlled acceptance rehearsal demonstrates why this check matters: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. It monitors the mechanism that OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The continuing safeguard should be correlated with the specific acceptance test: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
Incorrect Answers
A:Audit external route export allowlists against approved customer prefixes. This control addresses the distinct OSPF export policy omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The directly relevant continuing check is: Periodically compare intended and observed SPF cost paths after bandwidth changes. The governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
B:Reserve router IDs in an inventory and audit uniqueness during device provisioning. This control addresses the distinct Duplicate OSPF router identifier operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The directly relevant continuing check is: Periodically compare intended and observed SPF cost paths after bandwidth changes. The governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
C: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 controlled acceptance rehearsal. The observed problem here is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The directly relevant continuing check is: Periodically compare intended and observed SPF cost paths after bandwidth changes. The governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
Question 950
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document encryption requirements separately from GRE connectivity requirements.
- Audit source/destination tunnel-pair symmetry during new GRE turn-ups.
- Monitor underlay reachability independently from tunnel interface administrative state.
- Include encapsulation overhead in tunnel MTU and traffic acceptance tests.
Explanation
Correct Answer
D:Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The current controlled acceptance rehearsal demonstrates why this check matters: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. It monitors the mechanism that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The continuing safeguard should be correlated with the specific acceptance test: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.
Incorrect Answers
A:Document encryption requirements separately from GRE connectivity requirements. This control addresses the distinct GRE confidentiality misconception operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
B:Audit source/destination tunnel-pair symmetry during new GRE turn-ups. This control addresses the distinct GRE tunnel endpoint mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
C:Monitor underlay reachability independently from tunnel interface administrative state. This control addresses the distinct GRE underlay recursive loss operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The directly relevant continuing check is: Include encapsulation overhead in tunnel MTU and traffic acceptance tests. The governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests