Question 110
Two tenants reuse the same VNI plan in separate routing contexts, but a careless global RT import configuration risks leaking one tenant's advertisements into the other. 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. Test both positive and negative route-target import outcomes during tenant deployment. Logical tenant separation relies on explicit control-plane route distribution scope, not only shared fabric transport.
Incorrect Answers
Document loopback allocation and verify its route advertisement during device replacement and uplink maintenance. That concerns VTEP loopback source identity stability, while the issue here is EVPN route target tenant import. Compare intended export RTs and import policy in the participating tenant instances, correcting only the authorized membership.
Edge-routed bridging places an appropriate distributed Layer 3 gateway function at fabric edges for attached virtual networks. However, the present prevention decision is grounded in: Two tenants reuse the same VNI plan in separate routing contexts, but a careless global RT import configuration risks leaking one tenant's advertisements into the other. For this issue, compare intended export RTs and import policy in the participating tenant instances, correcting only the authorized membership.
Validate ESI and link-aggregation consistency whenever replacing a multihoming peer. Here, route targets mark EVPN VPN route membership and VRF import/export decisions; an established BGP session alone does not authorize all tenant routes.