Question 700
An application migration introduces a second customer with a reused private prefix and an operator merges their routing contexts to simplify inventory. 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. Document tenant-scoped addressing and avoid using global subnet uniqueness as the only isolation control. That is important in this case because separate tenant VRFs can each hold identical IP prefixes because route lookup and policy context remain isolated. The scenario was: An application migration introduces a second customer with a reused private prefix and an operator merges their routing contexts to simplify inventory.
Incorrect Answers
Compute or VMware inventory visibility and the actual fabric connectivity/template association are separate parts of data center service delivery. Here, separate tenant VRFs can each hold identical IP prefixes because route lookup and policy context remain isolated.
Maintain a tenant VNI allocation register and validate mapping when expanding virtual networks across racks. That concerns virtual network to VLAN and VNI service mapping, while the issue here is overlapping IPv4 addresses across isolated tenants. Keep overlapping tenant networks in their intended separate routing zones/VRFs and validate any approved external interconnection boundary.
Review stretched-versus-routed network requirements and DCI transport limits during cross-site application changes. Here, separate tenant VRFs can each hold identical IP prefixes because route lookup and policy context remain isolated.