Question 140
A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. Which next action best resolves this observed routing or switching failure?
Explanation
Correct Answer
Because route redistribution must be intentionally scoped to prevent cross-tenant leakage, the best response is to restrict routing-policy matches and validate the import and export boundary. A reviewer can close the technical case only after confirming that a negative test proves the unrelated customer prefix is absent from the target table.
Incorrect Answers
That result would be useful for a different failure, namely: A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. The current case specifically calls for: Restrict routing-policy matches and validate the import and export boundary. The required observed result is: A negative test proves the unrelated customer prefix is absent from the target table.
Distinguish internal LSAs from externally originated route information is a relevant step for the separate scenario in which a link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. It does not directly fix this case. Instead restrict routing-policy matches and validate the import and export boundary; verify: A negative test proves the unrelated customer prefix is absent from the target table.
The alternative addresses a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, not the present root cause. Here the selected correction must reflect route redistribution must be intentionally scoped to prevent cross-tenant leakage. Test for: A negative test proves the unrelated customer prefix is absent from the target table.