Question 990
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. 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.
- Verify label disposition and QoS handling at MPLS egress boundaries after policy changes.
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
- Check LDP session transport filtering as part of control-plane ACL reviews.
Explanation
Correct Answer
D:Check LDP session transport filtering as part of control-plane ACL reviews. The current controlled acceptance rehearsal demonstrates why this check matters: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. It monitors the mechanism that LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment. The continuing safeguard should be correlated with the specific acceptance test: An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
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: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The directly relevant continuing check is: Check LDP session transport filtering as part of control-plane ACL reviews. The governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
B: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: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The directly relevant continuing check is: Check LDP session transport filtering as part of control-plane ACL reviews. The governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
C: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 controlled acceptance rehearsal. The observed problem here is: Two directly connected LDP speakers see discovery Hellos but never establish an operational session because a control-plane filter blocks TCP 646. The directly relevant continuing check is: Check LDP session transport filtering as part of control-plane ACL reviews. The governing mechanism is: LDP uses discovery messages followed by a TCP session for the reliable exchange of labels; blocking the transport stops session establishment.
Question 991
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review route-preference conventions for static backups during routing-policy audits.
- Check classifier counters, filter attachment and target-table availability after changes.
- Review first-match precedence with representative negative and positive traffic tests.
- Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
Explanation
Correct Answer
A:Review route-preference conventions for static backups during routing-policy audits. The current controlled acceptance rehearsal demonstrates why this check matters: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. It monitors the mechanism that For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. The continuing safeguard should be correlated with the specific acceptance test: The selected active prefix shows the intended protocol, route preference, and forwarding next hop both before and after a controlled failover.
Incorrect Answers
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-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The directly relevant continuing check is: Review route-preference conventions for static backups during routing-policy audits. The governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
C:Review first-match precedence with representative negative and positive traffic tests. This control addresses the distinct Filter policy overmatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The directly relevant continuing check is: Review route-preference conventions for static backups during routing-policy audits. The governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
D: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-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. The directly relevant continuing check is: Review route-preference conventions for static backups during routing-policy audits. The governing mechanism is: For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.
Question 992
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. 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 IPv6 static routes for proper next-hop scope after link renumbering.
- Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer.
- Monitor OSPFv2 and OSPFv3 neighbor health independently on dual-stack links.
Explanation
Correct Answer
C:Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The current controlled acceptance rehearsal demonstrates why this check matters: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. It monitors the mechanism that BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange. The continuing safeguard should be correlated with the specific acceptance test: Approved IPv6 prefixes are received, installed and reachable with the correct inet6.0 next-hop resolution.
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: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The directly relevant continuing check is: Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
B:Check IPv6 static routes for proper next-hop scope after link renumbering. This control addresses the distinct IPv6 static link-local next hop operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The directly relevant continuing check is: Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
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: An eBGP peering is established for inet unicast but the provider cannot receive approved IPv6 prefixes because the IPv6 address family is absent. The directly relevant continuing check is: Check BGP families, IPv6 route filters and next-hop resolution on each dual-stack peer. The governing mechanism is: BGP address families carry IPv6 routes separately from IPv4 unicast NLRI; an IPv4 session alone does not guarantee IPv6 exchange.
Question 993
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
- Audit IS-IS route advertisements against customer import and export inventories.
- Validate NET area planning and permitted levels before adding a core adjacency.
- Use controlled startup overload and readiness criteria after routing-engine restarts.
Explanation
Correct Answer
C:Validate NET area planning and permitted levels before adding a core adjacency. The current controlled acceptance rehearsal demonstrates why this check matters: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. It monitors the mechanism that IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The continuing safeguard should be correlated with the specific acceptance test: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The directly relevant continuing check is: Validate NET area planning and permitted levels before adding a core adjacency. The governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
B: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 controlled acceptance rehearsal. The observed problem here is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The directly relevant continuing check is: Validate NET area planning and permitted levels before adding a core adjacency. The governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
D:Use controlled startup overload and readiness criteria after routing-engine restarts. This control addresses the distinct IS-IS overload-state recovery operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The directly relevant continuing check is: Validate NET area planning and permitted levels before adding a core adjacency. The governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas.
Question 994
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
- Monitor LFIB consistency with advertised label bindings after topology convergence.
- Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts.
- Audit service FEC transport next hops after RSVP design changes.
Explanation
Correct Answer
D:Audit service FEC transport next hops after RSVP design changes. The current controlled acceptance rehearsal demonstrates why this check matters: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. It monitors the mechanism that LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. The continuing safeguard should be correlated with the specific acceptance test: The service FEC shows an RSVP transport next hop and packets use the intended stacked labels and RSVP path.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The directly relevant continuing check is: Audit service FEC transport next hops after RSVP design changes. The governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
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 provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The directly relevant continuing check is: Audit service FEC transport next hops after RSVP design changes. The governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
C:Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts. This control addresses the distinct Segment routing SID advertisement operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. The directly relevant continuing check is: Audit service FEC transport next hops after RSVP design changes. The governing mechanism is: LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.
Question 995
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Include AS-path comparisons in periodic interdomain routing audit reports.
- Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow.
- Audit peer AS numbers during carrier handoffs and AS migration work.
- Document intended MED comparison scope and test different-neighbor-AS cases.
Explanation
Correct Answer
B:Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow. The current controlled acceptance rehearsal demonstrates why this check matters: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. It monitors the mechanism that Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design. The continuing safeguard should be correlated with the specific acceptance test: The intended peer receives the route through permitted reflection or a full-mesh session, and next-hop reachability is correct.
Incorrect Answers
A:Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The directly relevant continuing check is: Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow. The governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
C:Audit peer AS numbers during carrier handoffs and AS migration work. This control addresses the distinct BGP peer autonomous system mismatch operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The directly relevant continuing check is: Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow. The governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
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 controlled acceptance rehearsal. The observed problem here is: A router learns a BGP route from one IBGP peer but does not advertise it to a second IBGP peer, despite both sessions being Established. The directly relevant continuing check is: Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow. The governing mechanism is: Standard IBGP propagation rules do not relay an IBGP-learned route to another IBGP peer without a suitable route-reflection or confederation design.
Question 996
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
- Alert on unusual LSP aging patterns and repeated adjacency churn.
- Monitor Level 1 attached-bit or default-route availability at area boundaries.
- Use controlled startup overload and readiness criteria after routing-engine restarts.
Explanation
Correct Answer
B:Alert on unusual LSP aging patterns and repeated adjacency churn. The current controlled acceptance rehearsal demonstrates why this check matters: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. It monitors the mechanism that IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB. The continuing safeguard should be correlated with the specific acceptance test: LSPs from the peer remain current across normal refresh cycles and SPF paths do not disappear unexpectedly.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The directly relevant continuing check is: Alert on unusual LSP aging patterns and repeated adjacency churn. The governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
C: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 controlled acceptance rehearsal. The observed problem here is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The directly relevant continuing check is: Alert on unusual LSP aging patterns and repeated adjacency churn. The governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
D:Use controlled startup overload and readiness criteria after routing-engine restarts. This control addresses the distinct IS-IS overload-state recovery operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A core node repeatedly ages out IS-IS LSPs from one neighbor, leaving intermittent missing routes and shortened adjacency uptime. The directly relevant continuing check is: Alert on unusual LSP aging patterns and repeated adjacency churn. The governing mechanism is: IS-IS LSP sequence, remaining lifetime and flooding determine which topology information survives in the LSDB.
Question 997
During a controlled acceptance rehearsal of the same defect on a separate test network, 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?
- Monitor Level 1 attached-bit or default-route availability at area boundaries.
- Alert on unusual LSP aging patterns and repeated adjacency churn.
- Use controlled startup overload and readiness criteria after routing-engine restarts.
- Include interface family iso in standardized IS-IS provisioning templates.
Explanation
Correct Answer
C:Use controlled startup overload and readiness criteria after routing-engine restarts. The current controlled acceptance rehearsal 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
A: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 controlled acceptance rehearsal. 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.
B:Alert on unusual LSP aging patterns and repeated adjacency churn. This control addresses the distinct IS-IS LSP lifetime anomaly operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. 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: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 controlled acceptance rehearsal. 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 998
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document stub and normal area policies and validate expected LSA types.
- Include interface network-type checks in PE-to-PE circuit acceptance.
- Alert on repeated OSPF adjacency resets and divergent LSA conditions.
- Include OSPF interface MTU checks in transport migration validation.
Explanation
Correct Answer
C:Alert on repeated OSPF adjacency resets and divergent LSA conditions. The current controlled acceptance rehearsal demonstrates why this check matters: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. It monitors the mechanism that Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. The continuing safeguard should be correlated with the specific acceptance test: Both peers show the expected current LSAs with consistent sequence and topology, and the computed path reaches the destination.
Incorrect Answers
A: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 controlled acceptance rehearsal. The observed problem here is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The directly relevant continuing check is: Alert on repeated OSPF adjacency resets and divergent LSA conditions. The governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
B:Include interface network-type checks in PE-to-PE circuit acceptance. This control addresses the distinct Point-to-point OSPF network type operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The directly relevant continuing check is: Alert on repeated OSPF adjacency resets and divergent LSA conditions. The governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
D:Include OSPF interface MTU checks in transport migration validation. This control addresses the distinct OSPF MTU ExStart stall operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. The directly relevant continuing check is: Alert on repeated OSPF adjacency resets and divergent LSA conditions. The governing mechanism is: Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.
Question 999
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
- Include OSPF interface MTU checks in transport migration validation.
- Audit external route export allowlists against approved customer prefixes.
- Test backbone adjacency and ABR inter-area route reachability on every area change.
Explanation
Correct Answer
D:Test backbone adjacency and ABR inter-area route reachability on every area change. The current controlled acceptance rehearsal demonstrates why this check matters: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. It monitors the mechanism that Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers. The continuing safeguard should be correlated with the specific acceptance test: ABRs have the intended area 0 connectivity and inter-area routes are present with correct next hops.
Incorrect Answers
A: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: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The directly relevant continuing check is: Test backbone adjacency and ABR inter-area route reachability on every area change. The governing mechanism is: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
B:Include OSPF interface MTU checks in transport migration validation. This control addresses the distinct OSPF MTU ExStart stall operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The directly relevant continuing check is: Test backbone adjacency and ABR inter-area route reachability on every area change. The governing mechanism is: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
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: An area border router carries area 20 routes, but traffic between area 20 and area 30 is missing because backbone attachment is broken. The directly relevant continuing check is: Test backbone adjacency and ABR inter-area route reachability on every area change. The governing mechanism is: Normal OSPF multi-area routing relies on backbone area 0 to connect nonbackbone areas through area border routers.
Question 1000
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- 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.
- Exercise RSTP role transition in planned failover tests.
- Audit edge-port BPDU protection and alerts during customer endpoint changes.
Explanation
Correct Answer
D:Audit edge-port BPDU protection and alerts during customer endpoint changes. The current controlled acceptance rehearsal demonstrates why this check matters: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. It monitors the mechanism that Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. The continuing safeguard should be correlated with the specific acceptance test: The violating connection is blocked or alerted according to policy while legitimate host-facing links remain available.
Incorrect Answers
A: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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The directly relevant continuing check is: Audit edge-port BPDU protection and alerts during customer endpoint changes. The governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
B: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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The directly relevant continuing check is: Audit edge-port BPDU protection and alerts during customer endpoint changes. The governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
C: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 customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. The directly relevant continuing check is: Audit edge-port BPDU protection and alerts during customer endpoint changes. The governing mechanism is: Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests