Question 410
A fictional service-provider team at Northshore Digital is reviewing a network change window. The finding is: An aggregation policy announces a summary after all contributing more-specific routes vanish, misleading a downstream provider during an outage. Which ongoing control would most directly detect or prevent the same failure from recurring?
Explanation
Correct Answer
Test route contributor withdrawal in staging and compare active aggregates with constituent route inventory after changes. This monitors the behavior that failed at Northshore Digital; the most useful acceptance signal is that the aggregate is active only with the expected contributors and disappears when the contributor precondition is removed.
Incorrect Answers
Review per-link reserved and unreserved bandwidth before creating or resizing TE tunnels. That ongoing check is for RSVP path bandwidth admission; it would not reliably detect recurrence of aggregate route contributor. An aggregate route is conditional on active contributing routes and normally uses a discard or reject next hop to avoid creating a forwarding loop.
Continuously compare generated route eligibility and effective next hop against the approved regional reachability plan. The monitored boundary differs from aggregate route contributor, so the original weakness might reappear unnoticed. An aggregate route is conditional on active contributing routes and normally uses a discard or reject next hop to avoid creating a forwarding loop.
Validate VRF-specific route tables and access boundaries after all cross-instance policy changes. That ongoing check is for routing instance separation; it would not reliably detect recurrence of aggregate route contributor. An aggregate route is conditional on active contributing routes and normally uses a discard or reject next hop to avoid creating a forwarding loop.