Question 800
An engineer copies a route-target configuration from a different tenant and unintentionally exposes remote IP prefixes to the wrong routing zone. Once the issue is resolved, which ongoing practice BEST prevents this type of failure?
Explanation
Correct Answer
The preventive practice is aligned with the diagnosed mechanism, not an unrelated protection. Include routing zone identity and route targets in tenant VRF change reviews. Tenant control-plane reachability depends on explicitly scoped route membership, not only the existence of a shared EVPN BGP session.
Incorrect Answers
Audit routing-zone attachment when moving or renaming virtual networks. That concerns routing zone maps to tenant VRF, while the issue here is VRF route target mismatch across overlay tenants. Correct the approved export/import route target association in the affected tenant VRFs while testing isolation from other routing zones.
Separate tenant VRFs can each hold identical IP prefixes because route lookup and policy context remain isolated. However, the present prevention decision is grounded in: An engineer copies a route-target configuration from a different tenant and unintentionally exposes remote IP prefixes to the wrong routing zone. For this issue, correct the approved export/import route target association in the affected tenant VRFs while testing isolation from other routing zones.
Track border interface, routing-zone and peer parameters together for tenant interconnect changes. Here, overlay tenant route import requires route-target membership aligned with the intended VRF and EVPN service distribution.