Question 290
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: A core BGP neighbor restarts gracefully but a provider fails all traffic immediately despite planned stale-route retention. The most directly supported response is: Enable and verify supported BGP graceful restart behavior and independent next-hop recovery constraints. Technical basis: Graceful restart can preserve routing information temporarily while a control plane reconverges. Evidence of success: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget. Ongoing protection: Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.
Incorrect Answers
BGP Add-Paths and PIC address different multipath signaling and precomputed backup forwarding aspects. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Graceful restart can preserve routing information temporarily while a control plane reconverges. A passing check should show: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.
The proposed test would be relevant to: IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency. The reported problem follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges. Instead, verify: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.
The proposed test would be relevant to: MAP-T supports algorithmic IPv4-to-IPv6 translation and port-set assignment rather than central per-flow NAT state. The reported problem follows from: Graceful restart can preserve routing information temporarily while a control plane reconverges. Instead, verify: During a controlled restart, forwarding continues within specified stale-route timers without blackholing beyond the budget.