Question 1
A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What remediation is most directly applicable?
Explanation
Correct Answer
Underlying cause: Aggregation can hide individual component failures if advertisement policy is not controlled. Corrective action: distinguish aggregate reachability from specific-route forwarding and test loss of component routes. Verify the outcome: The summary is advertised only under the approved component-route conditions.
Incorrect Answers
Distinguish session negotiation from UPDATE message route advertisements is a relevant step for the separate scenario in which a provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. It does not directly fix this case. Instead distinguish aggregate reachability from specific-route forwarding and test loss of component routes; verify: The summary is advertised only under the approved component-route conditions.
The alternative addresses a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table, not the present root cause. Here the selected correction must reflect aggregation can hide individual component failures if advertisement policy is not controlled. Test for: The summary is advertised only under the approved component-route conditions.
This answer would be more suitable when a route shows as active but the interface destination still drops traffic after an interface move, where the corrective action is to compare installed forwarding entries with interface operational status and adjacency resolution. The failure here is different: Aggregation can hide individual component failures if advertisement policy is not controlled. Required validation: The summary is advertised only under the approved component-route conditions.