Question 980
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Sample FEC label bindings and forwarding resolution after prefix or IGP changes.
- Monitor LFIB consistency with advertised label bindings after topology convergence.
- Document expected label stacks at ingress, transit and penultimate hop for key services.
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
Explanation
Correct Answer
D:Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The current controlled acceptance rehearsal demonstrates why this check matters: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. It monitors the mechanism that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The continuing safeguard should be correlated with the specific acceptance test: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.
Incorrect Answers
A:Sample FEC label bindings and forwarding resolution after prefix or IGP changes. This control addresses the distinct Missing LDP FEC label mapping operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
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 new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
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 new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.
Question 981
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
- Track intended one-way and reverse-path LSP inventories for bidirectional services.
- Validate actual SR paths and segment lists after core metric or policy changes.
- Monitor LFIB consistency with advertised label bindings after topology convergence.
Explanation
Correct Answer
D:Monitor LFIB consistency with advertised label bindings after topology convergence. The current controlled acceptance rehearsal demonstrates why this check matters: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. It monitors the mechanism that MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. The continuing safeguard should be correlated with the specific acceptance test: A lookup for the affected incoming label shows the expected output label and interface, and an MPLS trace reaches the egress.
Incorrect Answers
A: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: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The directly relevant continuing check is: Monitor LFIB consistency with advertised label bindings after topology convergence. The governing mechanism is: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
B:Track intended one-way and reverse-path LSP inventories for bidirectional services. This control addresses the distinct RSVP LSP directionality operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The directly relevant continuing check is: Monitor LFIB consistency with advertised label bindings after topology convergence. The governing mechanism is: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
C:Validate actual SR paths and segment lists after core metric or policy changes. This control addresses the distinct SR-MPLS node-SID shortest path operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. The directly relevant continuing check is: Monitor LFIB consistency with advertised label bindings after topology convergence. The governing mechanism is: MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.
Question 982
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Document peer distance, TTL, and authorized transport path for remote eBGP sessions.
- Review inbound prefix filtering and max-route thresholds with every peer change.
- Include AS-path comparisons in periodic interdomain routing audit reports.
- Check BGP negotiated families and IPv6 route policy during dual-stack migrations.
Explanation
Correct Answer
C:Include AS-path comparisons in periodic interdomain routing audit reports. The current controlled acceptance rehearsal demonstrates why this check matters: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. It monitors the mechanism that When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers. The continuing safeguard should be correlated with the specific acceptance test: A route detail comparison shows the relevant AS-path difference and chosen path conforms to approved policy.
Incorrect Answers
A: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 provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The directly relevant continuing check is: Include AS-path comparisons in periodic interdomain routing audit reports. The governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
B: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 provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The directly relevant continuing check is: Include AS-path comparisons in periodic interdomain routing audit reports. The governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
D:Check BGP negotiated families and IPv6 route policy during dual-stack migrations. This control addresses the distinct BGP IPv6 family inactive operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A provider selects an unexpected egress when local preferences are equal, because the chosen route has fewer AS hops than a manually favored alternative. The directly relevant continuing check is: Include AS-path comparisons in periodic interdomain routing audit reports. The governing mechanism is: When earlier selection criteria tie, BGP typically prefers a shorter AS path before later tie-breakers.
Question 983
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- 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
C:Monitor Level 1 attached-bit or default-route availability at area boundaries. The current controlled acceptance rehearsal demonstrates why this check matters: A Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. It monitors the mechanism that Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes. The continuing safeguard should be correlated with the specific acceptance test: A usable default or intended inter-area reachability is present, and traced traffic exits through the designed L1/L2 router.
Incorrect Answers
A: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 Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The directly relevant continuing check is: Monitor Level 1 attached-bit or default-route availability at area boundaries. The governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
B: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 Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The directly relevant continuing check is: Monitor Level 1 attached-bit or default-route availability at area boundaries. The governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
D: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 Level 1-only provider edge has no route outside its area because it expects to learn every external prefix in the Level 1 database. The directly relevant continuing check is: Monitor Level 1 attached-bit or default-route availability at area boundaries. The governing mechanism is: Level 1 routers may rely on an attached Level 1/2 router or configured default to exit an area rather than carrying all inter-area routes.
Question 984
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Exercise backup-path liveness detection under downstream and local failure scenarios.
- Review generated-route contributors and policy conditions whenever edge reachability changes.
- Check classifier counters, filter attachment and target-table availability after changes.
- Review import/export scope and route-copy audits when new routing instances are introduced.
Explanation
Correct Answer
B:Review generated-route contributors and policy conditions whenever edge reachability changes. The current controlled acceptance rehearsal demonstrates why this check matters: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. It monitors the mechanism that Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The continuing safeguard should be correlated with the specific acceptance test: The generated default becomes active with the expected next hop only when the qualifying contributor exists.
Incorrect Answers
A: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 generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The directly relevant continuing check is: Review generated-route contributors and policy conditions whenever edge reachability changes. The governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
C: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: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The directly relevant continuing check is: Review generated-route contributors and policy conditions whenever edge reachability changes. The governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
D:Review import/export scope and route-copy audits when new routing instances are introduced. This control addresses the distinct RIB group forwarding copy operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The directly relevant continuing check is: Review generated-route contributors and policy conditions whenever edge reachability changes. The governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text.
Question 985
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Review inbound prefix filtering and max-route thresholds with every peer change.
- Check BGP negotiated families and IPv6 route policy during dual-stack migrations.
- Record negotiated BGP timers and correlate flap events with packet-loss telemetry.
- Audit local-preference policy for consistency across ingress points.
Explanation
Correct Answer
D:Audit local-preference policy for consistency across ingress points. The current controlled acceptance rehearsal demonstrates why this check matters: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. It monitors the mechanism that Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. The continuing safeguard should be correlated with the specific acceptance test: The designated BGP exit wins best-path selection for the intended prefixes and backup behavior remains correct.
Incorrect Answers
A: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: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The directly relevant continuing check is: Audit local-preference policy for consistency across ingress points. The governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
B:Check BGP negotiated families and IPv6 route policy during dual-stack migrations. This control addresses the distinct BGP IPv6 family inactive operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The directly relevant continuing check is: Audit local-preference policy for consistency across ingress points. The governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
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: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. The directly relevant continuing check is: Audit local-preference policy for consistency across ingress points. The governing mechanism is: Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.
Question 986
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
- Verify label disposition and QoS handling at MPLS egress boundaries after policy changes.
- Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
- Audit SID allocations, uniqueness and IGP propagation during segment-routing rollouts.
Explanation
Correct Answer
B:Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The current controlled acceptance rehearsal demonstrates why this check matters: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. It monitors the mechanism that Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. The continuing safeguard should be correlated with the specific acceptance test: A captured or traced packet reaches the egress with the expected explicit-null label and traffic-class handling.
Incorrect Answers
A: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: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The directly relevant continuing check is: Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
C: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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The directly relevant continuing check is: Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
D: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 service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. The directly relevant continuing check is: Verify label disposition and QoS handling at MPLS egress boundaries after policy changes. The governing mechanism is: Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.
Question 987
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. 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.
- Review inbound prefix filtering and max-route thresholds with every peer change.
- Audit local-preference policy for consistency across ingress points.
- Document peer distance, TTL, and authorized transport path for remote eBGP sessions.
Explanation
Correct Answer
D:Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The current controlled acceptance rehearsal demonstrates why this check matters: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. It monitors the mechanism that An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers. The continuing safeguard should be correlated with the specific acceptance test: The multihop session forms between the designed IP endpoints, TTL is appropriate and only intended neighbors can connect.
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 eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The directly relevant continuing check is: Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
B: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 eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The directly relevant continuing check is: Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
C:Audit local-preference policy for consistency across ingress points. This control addresses the distinct BGP local preference egress operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A remote eBGP session must cross an intervening router but was configured as directly connected, so it fails even though both endpoints are routable. The directly relevant continuing check is: Document peer distance, TTL, and authorized transport path for remote eBGP sessions. The governing mechanism is: An eBGP session to a non-direct neighbor needs multihop transport allowances; directly connected assumptions do not work across intervening routers.
Question 988
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. 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.
- Test one-way BPDU loss and protected port-state behavior during redundancy reviews.
- Compare MSTP region configuration and digests on each addition or VLAN change.
- Review STP root and backup priorities after device replacement or MAC changes.
Explanation
Correct Answer
C:Compare MSTP region configuration and digests on each addition or VLAN change. The current controlled acceptance rehearsal demonstrates why this check matters: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. It monitors the mechanism that MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping. The continuing safeguard should be correlated with the specific acceptance test: Both switches report the same region digest and expected instance-specific spanning-tree paths.
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: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. The directly relevant continuing check is: Compare MSTP region configuration and digests on each addition or VLAN change. The governing mechanism is: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
B: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: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. The directly relevant continuing check is: Compare MSTP region configuration and digests on each addition or VLAN change. The governing mechanism is: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
D: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: Two switches intended to operate in the same MSTP region treat each other as a boundary because their VLAN-to-instance mapping digests differ. The directly relevant continuing check is: Compare MSTP region configuration and digests on each addition or VLAN change. The governing mechanism is: MSTP region membership depends on matching region configuration identifiers, including VLAN-to-instance mapping.
Question 989
During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Maintain explicit inter-instance route-leak allowlists and regression tests.
- Review route-preference conventions for static backups during routing-policy audits.
- Review generated-route contributors and policy conditions whenever edge reachability changes.
- Test covered and uncovered address samples as part of aggregate change validation.
Explanation
Correct Answer
A:Maintain explicit inter-instance route-leak allowlists and regression tests. The current controlled acceptance rehearsal demonstrates why this check matters: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. It monitors the mechanism that Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy. The continuing safeguard should be correlated with the specific acceptance test: Permitted prefixes are visible in the correct tables and an unauthorized destination is absent from the receiving customer's forwarding view.
Incorrect Answers
B:Review route-preference conventions for static backups during routing-policy audits. This control addresses the distinct Administrative preference overrides static operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The directly relevant continuing check is: Maintain explicit inter-instance route-leak allowlists and regression tests. The governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
C:Review generated-route contributors and policy conditions whenever edge reachability changes. This control addresses the distinct Generated default route prerequisite operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The directly relevant continuing check is: Maintain explicit inter-instance route-leak allowlists and regression tests. The governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
D:Test covered and uncovered address samples as part of aggregate change validation. This control addresses the distinct Aggregate rejection behavior operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A customer routing instance unexpectedly reaches another customer's prefix because an overly broad route import exposes paths across isolation boundaries. The directly relevant continuing check is: Maintain explicit inter-instance route-leak allowlists and regression tests. The governing mechanism is: Separate Junos routing instances maintain distinct routing tables; cross-instance reachability requires an intentional route-leak mechanism and suitable policy.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests