Question 760
A new partner connection begins advertising all tenant routes instead of its approved subset because a broad import/export policy was selected. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
A lasting control should detect the original error before release. Test negative and positive prefix-policy outcomes after every tenant service expansion. That is important in this case because routing protocol adjacency and route-policy filtering are separate controls for which tenant prefixes are accepted or advertised. The scenario was: A new partner connection begins advertising all tenant routes instead of its approved subset because a broad import/export policy was selected.
Incorrect Answers
Routing-zone connectivity and security policy authorization are distinct requirements when business traffic crosses controlled service boundaries. For the current prevention question, the evidence instead states: A new partner connection begins advertising all tenant routes instead of its approved subset because a broad import/export policy was selected. Here, routing protocol adjacency and route-policy filtering are separate controls for which tenant prefixes are accepted or advertised.
Document tenant-scoped addressing and avoid using global subnet uniqueness as the only isolation control. That concerns overlapping IPv4 addresses across isolated tenants, while the issue here is routing policy control for tenant route exchange. Review peer address-family and tenant VRF routing policies, then permit only approved import/export prefixes and verify advertisements.
Tenant routing-zone isolation is an intentional boundary; intertenant reachability may require an approved external routing/security service rather than indiscriminate VRF route sharing. For this issue, review peer address-family and tenant VRF routing policies, then permit only approved import/export prefixes and verify advertisements.