Question 470
During production incident triage, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit peer AS numbers during carrier handoffs and AS migration work.
- Audit local-preference policy for consistency across ingress points.
- Include AS-path comparisons in periodic interdomain routing audit reports.
- Review inbound prefix filtering and max-route thresholds with every peer change.
Explanation
Correct Answer
A:Audit peer AS numbers during carrier handoffs and AS migration work. The current live production incident demonstrates why this check matters: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. It monitors the mechanism that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. The continuing safeguard should be correlated with the specific acceptance test: Both peers establish an expected eBGP session and the remote AS displayed in session state matches the design.
Incorrect Answers
B:Audit local-preference policy for consistency across ingress points. This control addresses the distinct BGP local preference egress operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
C: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 live production incident. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
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 live production incident. The observed problem here is: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. The directly relevant continuing check is: Audit peer AS numbers during carrier handoffs and AS migration work. The governing mechanism is: BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.
Question 471
During production incident triage, 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?
- Check LDP session transport filtering as part of control-plane ACL reviews.
- Document expected label stacks at ingress, transit and penultimate hop for key services.
- Audit service FEC transport next hops after RSVP design changes.
- Rehearse RSVP protection paths during maintenance and monitor bypass readiness.
Explanation
Correct Answer
C:Audit service FEC transport next hops after RSVP design changes. The current live production incident 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:Check LDP session transport filtering as part of control-plane ACL reviews. This control addresses the distinct LDP TCP 646 establishment operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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:Document expected label stacks at ingress, transit and penultimate hop for key services. This control addresses the distinct Penultimate hop popping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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.
D:Rehearse RSVP protection paths during maintenance and monitor bypass readiness. This control addresses the distinct RSVP link protection plan operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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 472
During production incident triage, 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?
- Reconcile customer port VLAN membership against service orders after provisioning.
- Include native VLAN agreement and negative isolation tests in trunk turn-up procedures.
- Monitor unknown-unicast rate together with MAC-table learning and churn.
- Review instance-to-interface memberships during virtual switching changes.
Explanation
Correct Answer
A:Reconcile customer port VLAN membership against service orders after provisioning. The current live production incident 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
B:Include native VLAN agreement and negative isolation tests in trunk turn-up procedures. This control addresses the distinct Native VLAN mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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:Monitor unknown-unicast rate together with MAC-table learning and churn. This control addresses the distinct Unknown unicast flooding behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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:Review instance-to-interface memberships during virtual switching changes. This control addresses the distinct Virtual switch instance membership operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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 473
During production incident triage, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Compare MSTP region configuration and digests on each addition or VLAN change.
- Exercise RSTP role transition in planned failover tests.
- Audit edge-port BPDU protection and alerts during customer endpoint changes.
- Monitor root-protection violations and keep the intended root location documented.
Explanation
Correct Answer
D:Monitor root-protection violations and keep the intended root location documented. The current live production incident demonstrates why this check matters: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. It monitors the mechanism that Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. The continuing safeguard should be correlated with the specific acceptance test: The port enters the documented root-prevented state for superior BPDUs and recovers when the rogue advertisement stops.
Incorrect Answers
A:Compare MSTP region configuration and digests on each addition or VLAN change. This control addresses the distinct MSTP region mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The directly relevant continuing check is: Monitor root-protection violations and keep the intended root location documented. The governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
B: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 live production incident. The observed problem here is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The directly relevant continuing check is: Monitor root-protection violations and keep the intended root location documented. The governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
C: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 live production incident. The observed problem here is: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. The directly relevant continuing check is: Monitor root-protection violations and keep the intended root location documented. The governing mechanism is: Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.
Question 474
During production incident triage, 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?
- Check peer-specific TCP reachability and filtering during peering change control.
- Review inbound prefix filtering and max-route thresholds with every peer change.
- Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow.
- Include AS-path comparisons in periodic interdomain routing audit reports.
Explanation
Correct Answer
C:Audit route-reflector cluster design and iBGP full-mesh requirements as peer counts grow. The current live production incident 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:Check peer-specific TCP reachability and filtering during peering change control. This control addresses the distinct BGP TCP transport blocked operational scenario rather than preventing recurrence of the live production incident. 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.
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 live production incident. 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: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 live production incident. 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 475
During production incident triage, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Validate NET area planning and permitted levels before adding a core adjacency.
- Audit IS-IS route advertisements against customer import and export inventories.
- Maintain a registry of ISO NET system IDs across every area and lab clone.
- Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
Explanation
Correct Answer
B:Audit IS-IS route advertisements against customer import and export inventories. The current live production incident demonstrates why this check matters: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. It monitors the mechanism that IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The continuing safeguard should be correlated with the specific acceptance test: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.
Incorrect Answers
A:Validate NET area planning and permitted levels before adding a core adjacency. This control addresses the distinct IS-IS level-one area mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The directly relevant continuing check is: Audit IS-IS route advertisements against customer import and export inventories. The governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
C:Maintain a registry of ISO NET system IDs across every area and lab clone. This control addresses the distinct Duplicate IS-IS system ID operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The directly relevant continuing check is: Audit IS-IS route advertisements against customer import and export inventories. The governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
D:Baseline metric-style compatibility before area-wide IS-IS cost adjustments. This control addresses the distinct IS-IS narrow metric ceiling operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The directly relevant continuing check is: Audit IS-IS route advertisements against customer import and export inventories. The governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain.
Question 476
During production incident triage, engineers observe: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Check MPLS interface participation during each core link turn-up.
- Check LDP session transport filtering as part of control-plane ACL reviews.
- Continuously validate configured RSVP explicit paths against network topology inventory.
- Track reserved and unreserved bandwidth on TE links before new LSP provisioning.
Explanation
Correct Answer
A:Check MPLS interface participation during each core link turn-up. The current live production incident demonstrates why this check matters: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. It monitors the mechanism that MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. The continuing safeguard should be correlated with the specific acceptance test: The core interface is MPLS enabled and labeled forwarding entries exist for the expected transport destination.
Incorrect Answers
B:Check LDP session transport filtering as part of control-plane ACL reviews. This control addresses the distinct LDP TCP 646 establishment operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The directly relevant continuing check is: Check MPLS interface participation during each core link turn-up. The governing mechanism is: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
C: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 live production incident. The observed problem here is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The directly relevant continuing check is: Check MPLS interface participation during each core link turn-up. The governing mechanism is: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
D:Track reserved and unreserved bandwidth on TE links before new LSP provisioning. This control addresses the distinct RSVP reservable bandwidth shortage operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. The directly relevant continuing check is: Check MPLS interface participation during each core link turn-up. The governing mechanism is: MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.
Question 477
During production incident triage, engineers observe: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Baseline OSPF timer settings per transport class and alert on configuration drift.
- Document broadcast-segment DR priorities and rehearse controlled elections.
- Audit external route export allowlists against approved customer prefixes.
- Periodically compare intended and observed SPF cost paths after bandwidth changes.
Explanation
Correct Answer
D:Periodically compare intended and observed SPF cost paths after bandwidth changes. The current live production incident demonstrates why this check matters: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. It monitors the mechanism that OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric. The continuing safeguard should be correlated with the specific acceptance test: Calculated path costs and the active next hop match the expected path, and failover still uses a valid alternate.
Incorrect Answers
A: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 live production incident. The observed problem here is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The directly relevant continuing check is: Periodically compare intended and observed SPF cost paths after bandwidth changes. The governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
B:Document broadcast-segment DR priorities and rehearse controlled elections. This control addresses the distinct DR priority zero misconception operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The directly relevant continuing check is: Periodically compare intended and observed SPF cost paths after bandwidth changes. The governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
C: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 live production incident. The observed problem here is: Core traffic uses the higher-delay OSPF path because its calculated sum of interface costs is lower than the intended low-delay path. The directly relevant continuing check is: Periodically compare intended and observed SPF cost paths after bandwidth changes. The governing mechanism is: OSPF chooses routes using accumulated link-state cost along the path; interface bandwidth alone does not guarantee the intended end-to-end metric.
Question 478
During production incident triage, engineers observe: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit VLAN-to-IRB bindings and routed interfaces during new service activation.
- Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up.
- Review instance-to-interface memberships during virtual switching changes.
- Monitor unknown-unicast rate together with MAC-table learning and churn.
Explanation
Correct Answer
B:Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The current live production incident demonstrates why this check matters: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. It monitors the mechanism that Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. The continuing safeguard should be correlated with the specific acceptance test: Per-unit counters and a packet capture demonstrate each authorized VLAN tag reaches its mapped logical interface.
Incorrect Answers
A:Audit VLAN-to-IRB bindings and routed interfaces during new service activation. This control addresses the distinct IRB routed gateway missing operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The directly relevant continuing check is: Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
C:Review instance-to-interface memberships during virtual switching changes. This control addresses the distinct Virtual switch instance membership operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The directly relevant continuing check is: Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
D:Monitor unknown-unicast rate together with MAC-table learning and churn. This control addresses the distinct Unknown unicast flooding behavior operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. The directly relevant continuing check is: Verify logical-unit VLAN IDs and encapsulation during each additional service turn-up. The governing mechanism is: Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.
Question 479
During production incident triage, 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?
- Check MPLS interface participation during each core link turn-up.
- 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.
Explanation
Correct Answer
B:Check LDP session transport filtering as part of control-plane ACL reviews. The current live production incident 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:Check MPLS interface participation during each core link turn-up. This control addresses the distinct MPLS interface not enabled operational scenario rather than preventing recurrence of the live production incident. 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: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 live production incident. 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.
D:Document expected label stacks at ingress, transit and penultimate hop for key services. This control addresses the distinct Penultimate hop popping operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: 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 480
During production incident triage, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. Which ongoing validation or operating control most directly prevents this specific failure from recurring?
- Audit LACP partner identity and collecting/distributing state during bundle maintenance.
- Validate planned VRRP priorities and failover behavior after router maintenance.
- Monitor VRRP failover and preempt events correlated to upstream route health.
- Baseline BFD timer settings by platform and monitor false-flap trends.
Explanation
Correct Answer
D:Baseline BFD timer settings by platform and monitor false-flap trends. The current live production incident demonstrates why this check matters: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. It monitors the mechanism that BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. The continuing safeguard should be correlated with the specific acceptance test: The session remains stable during representative load yet detects an injected forwarding fault within the approved interval.
Incorrect Answers
A:Audit LACP partner identity and collecting/distributing state during bundle maintenance. This control addresses the distinct LACP partner mismatch operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
B:Validate planned VRRP priorities and failover behavior after router maintenance. This control addresses the distinct VRRP master priority failover operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
C:Monitor VRRP failover and preempt events correlated to upstream route health. This control addresses the distinct VRRP preemption oscillation operational scenario rather than preventing recurrence of the live production incident. The observed problem here is: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. The directly relevant continuing check is: Baseline BFD timer settings by platform and monitor false-flap trends. The governing mechanism is: BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests