Question 930
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
- Audit external route export allowlists against approved customer prefixes.
- Reserve router IDs in an inventory and audit uniqueness during device provisioning.
Explanation
Correct Answer
D:Reserve router IDs in an inventory and audit uniqueness during device provisioning. The current controlled acceptance rehearsal demonstrates why this check matters: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. It monitors the mechanism that OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. The continuing safeguard should be correlated with the specific acceptance test: The routers advertise distinct IDs, neighbors remain Full and the LSDB no longer shows conflicting origins.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
B:Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. This control addresses the distinct OSPF authentication key mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
C: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: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. The directly relevant continuing check is: Reserve router IDs in an inventory and audit uniqueness during device provisioning. The governing mechanism is: OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.
Question 931
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. 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.
- Validate planned VRRP priorities and failover behavior after router maintenance.
- 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
B:Validate planned VRRP priorities and failover behavior after router maintenance. The current controlled acceptance rehearsal demonstrates why this check matters: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. It monitors the mechanism that VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway. The continuing safeguard should be correlated with the specific acceptance test: The designated router is primary under normal conditions and the backup takes over promptly during an injected outage.
Incorrect Answers
A: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: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The directly relevant continuing check is: Validate planned VRRP priorities and failover behavior after router maintenance. The governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
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: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The directly relevant continuing check is: Validate planned VRRP priorities and failover behavior after router maintenance. The governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
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: Two routers share a VRRP virtual gateway but the lower-priority device stays primary contrary to design after a controlled handoff. The directly relevant continuing check is: Validate planned VRRP priorities and failover behavior after router maintenance. The governing mechanism is: VRRP elects a primary virtual-router owner based on effective priority and protocol state, providing a shared first-hop gateway.
Question 932
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Document intended MED comparison scope and test different-neighbor-AS cases.
- Verify prefix-level export allowlists during customer peering acceptance.
- Record negotiated BGP timers and correlate flap events with packet-loss telemetry.
- Document peer distance, TTL, and authorized transport path for remote eBGP sessions.
Explanation
Correct Answer
B:Verify prefix-level export allowlists during customer peering acceptance. The current controlled acceptance rehearsal 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: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 controlled acceptance rehearsal. 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:Record negotiated BGP timers and correlate flap events with packet-loss telemetry. This control addresses the distinct BGP peer flap from mismatched hold timers operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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 peer distance, TTL, and authorized transport path for remote eBGP sessions. This control addresses the distinct EBGP multihop peering operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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 933
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- 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.
- Maintain a documented martian and bogon-address policy aligned with assigned network ranges.
Explanation
Correct Answer
D:Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The current controlled acceptance rehearsal demonstrates why this check matters: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. It monitors the mechanism that Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context. The continuing safeguard should be correlated with the specific acceptance test: The prefix is absent from permitted active forwarding while legitimate nearby routes remain reachable and logged rejection evidence matches policy.
Incorrect Answers
A: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: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The directly relevant continuing check is: Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
B:Check classifier counters, filter attachment and target-table availability after changes. This control addresses the distinct Filter-based forwarding classification operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The directly relevant continuing check is: Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
C: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: PE-16 receives a route for a prefix that operations classify as martian, and policy reviews show that it should not be accepted as a normal reachable destination. The directly relevant continuing check is: Maintain a documented martian and bogon-address policy aligned with assigned network ranges. The governing mechanism is: Junos martian-address handling protects against inappropriate use of addresses that should not appear as normal routing destinations in that context.
Question 934
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit source/destination tunnel-pair symmetry during new GRE turn-ups.
- Document encryption requirements separately from GRE connectivity requirements.
- Include encapsulation overhead in tunnel MTU and traffic acceptance tests.
- Monitor underlay reachability independently from tunnel interface administrative state.
Explanation
Correct Answer
D:Monitor underlay reachability independently from tunnel interface administrative state. The current controlled acceptance rehearsal demonstrates why this check matters: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. It monitors the mechanism that GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The continuing safeguard should be correlated with the specific acceptance test: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.
Incorrect Answers
A: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 interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The directly relevant continuing check is: Monitor underlay reachability independently from tunnel interface administrative state. The governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
B: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 interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The directly relevant continuing check is: Monitor underlay reachability independently from tunnel interface administrative state. The governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
C:Include encapsulation overhead in tunnel MTU and traffic acceptance tests. This control addresses the distinct GRE encapsulation MTU overhead operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The directly relevant continuing check is: Monitor underlay reachability independently from tunnel interface administrative state. The governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable.
Question 935
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document expected label stacks at ingress, transit and penultimate hop for key services.
- Compare LDP-enabled links with IGP core interfaces after changes.
- Verify label disposition and QoS handling at MPLS egress boundaries after policy changes.
- Continuously validate configured RSVP explicit paths against network topology inventory.
Explanation
Correct Answer
B:Compare LDP-enabled links with IGP core interfaces after changes. The current controlled acceptance rehearsal demonstrates why this check matters: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. It monitors the mechanism that LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. The continuing safeguard should be correlated with the specific acceptance test: Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The directly relevant continuing check is: Compare LDP-enabled links with IGP core interfaces after changes. The governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
C:Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. This control addresses the distinct Explicit-null forwarding operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The directly relevant continuing check is: Compare LDP-enabled links with IGP core interfaces after changes. The governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
D:Continuously validate configured RSVP explicit paths against network topology inventory. This control addresses the distinct RSVP-TE constrained path missing operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. The directly relevant continuing check is: Compare LDP-enabled links with IGP core interfaces after changes. The governing mechanism is: LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.
Question 936
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Check LDP session transport filtering as part of control-plane ACL reviews.
- Monitor LFIB consistency with advertised label bindings after topology convergence.
- Document expected label stacks at ingress, transit and penultimate hop for key services.
- Track intended one-way and reverse-path LSP inventories for bidirectional services.
Explanation
Correct Answer
D:Track intended one-way and reverse-path LSP inventories for bidirectional services. The current controlled acceptance rehearsal demonstrates why this check matters: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. It monitors the mechanism that RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP. The continuing safeguard should be correlated with the specific acceptance test: Forward and reverse tests each map to separately verified forwarding paths with their intended egress destinations.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The directly relevant continuing check is: Track intended one-way and reverse-path LSP inventories for bidirectional services. The governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
B:Monitor LFIB consistency with advertised label bindings after topology convergence. This control addresses the distinct Incoming label missing in LFIB operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The directly relevant continuing check is: Track intended one-way and reverse-path LSP inventories for bidirectional services. The governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
C: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 controlled acceptance rehearsal. The observed problem here is: A customer expects an RSVP transport LSP configured from PE-A to PE-B to automatically carry reverse-direction traffic, but reverse path tests fail. The directly relevant continuing check is: Track intended one-way and reverse-path LSP inventories for bidirectional services. The governing mechanism is: RSVP-TE LSPs are unidirectional; a forward LSP does not automatically constitute a return LSP.
Question 937
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document intended MED comparison scope and test different-neighbor-AS cases.
- Verify prefix-level export allowlists during customer peering acceptance.
- Record negotiated BGP timers and correlate flap events with packet-loss telemetry.
- Review inbound prefix filtering and max-route thresholds with every peer change.
Explanation
Correct Answer
C:Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The current controlled acceptance rehearsal demonstrates why this check matters: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. It monitors the mechanism that BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long. The continuing safeguard should be correlated with the specific acceptance test: The negotiated hold time is visible and the session remains Established under representative transport jitter without spurious expiry.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The directly relevant continuing check is: Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
B:Verify prefix-level export allowlists during customer peering acceptance. This control addresses the distinct BGP export policy omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The directly relevant continuing check is: Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
D:Review inbound prefix filtering and max-route thresholds with every peer change. This control addresses the distinct BGP import policy leak operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A remote BGP peer repeatedly closes sessions after sporadic delays, and operations incorrectly assume the configured hold timers on both routers must be identical even though negotiation occurs. The directly relevant continuing check is: Record negotiated BGP timers and correlate flap events with packet-loss telemetry. The governing mechanism is: BGP peers negotiate a hold time during OPEN exchange; a negotiated liveness timer expires when valid BGP messages are absent too long.
Question 938
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review instance-to-interface memberships during virtual switching changes.
- Reconcile customer port VLAN membership against service orders after provisioning.
- 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.
Explanation
Correct Answer
B:Reconcile customer port VLAN membership against service orders after provisioning. The current controlled acceptance rehearsal demonstrates why this check matters: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. It monitors the mechanism that An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership. The continuing safeguard should be correlated with the specific acceptance test: The CE MAC is learned in VLAN 120 and its frames reach a same-VLAN peer without leaking into VLAN 110.
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 controlled acceptance rehearsal. The observed problem here is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The directly relevant continuing check is: Reconcile customer port VLAN membership against service orders after provisioning. The governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
C: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 controlled acceptance rehearsal. The observed problem here is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The directly relevant continuing check is: Reconcile customer port VLAN membership against service orders after provisioning. The governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
D:Audit allowed VLAN sets per service and test tagged membership during changes. This control addresses the distinct Trunk allowed VLAN omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer CE is connected to an access port configured for VLAN 110, while its service should be VLAN 120, and its frames cannot reach the correct broadcast domain. The directly relevant continuing check is: Reconcile customer port VLAN membership against service orders after provisioning. The governing mechanism is: An access port classifies untagged received frames into its configured VLAN, which determines Layer 2 forwarding membership.
Question 939
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include interface network-type checks in PE-to-PE circuit acceptance.
- Test backbone adjacency and ABR inter-area route reachability on every area change.
- Audit external route export allowlists against approved customer prefixes.
- Baseline OSPF timer settings per transport class and alert on configuration drift.
Explanation
Correct Answer
A:Include interface network-type checks in PE-to-PE circuit acceptance. The current controlled acceptance rehearsal demonstrates why this check matters: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. It monitors the mechanism that OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election. The continuing safeguard should be correlated with the specific acceptance test: Each endpoint shows a point-to-point interface and one stable Full neighbor without DR or BDR expectations.
Incorrect Answers
B:Test backbone adjacency and ABR inter-area route reachability on every area change. This control addresses the distinct OSPF backbone connectivity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The directly relevant continuing check is: Include interface network-type checks in PE-to-PE circuit acceptance. The governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.
C: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: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The directly relevant continuing check is: Include interface network-type checks in PE-to-PE circuit acceptance. The governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.
D:Baseline OSPF timer settings per transport class and alert on configuration drift. This control addresses the distinct OSPF hello dead timer mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two routers on an engineered point-to-point interface spend time trying to use an unnecessary broadcast DR election process. The directly relevant continuing check is: Include interface network-type checks in PE-to-PE circuit acceptance. The governing mechanism is: OSPF point-to-point network types use one direct adjacency without broadcast-network DR and BDR election.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests