Question 370
A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What assessment accurately links the fault to its correction?
Explanation
Correct Answer
Because aggregation can hide individual component failures if advertisement policy is not controlled, the best response is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes. A reviewer can close the technical case only after confirming that the summary is advertised only under the approved component-route conditions.
Incorrect Answers
The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, aggregation can hide individual component failures if advertisement policy is not controlled. The most direct correction is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes, confirmed by the summary is advertised only under the approved component-route conditions.
That result would be useful for a different failure, namely: A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. The current case specifically calls for: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The required observed result is: The summary is advertised only under the approved component-route conditions.
This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The summary is advertised only under the approved component-route conditions. The relevant action is: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.