A port authority’s operators struggle to reason about routing tables and policy after dozens of near-duplicate Virtual Networks were created. What VN design hygiene should leadership enforce?
Select an answer to reveal the explanation.
Short Explanation
VNs are powerful walls, but building a new wall for every closet turns the campus into a maze nobody can navigate. Keep VNs tied to real macro boundaries—OT versus office, agencies that must stay apart—not vanity duplicates. Operable routing tables beat impressive VN counts.
Full Explanation
Each Virtual Network adds overlay routing and policy complexity. SD-Access designs should create VNs for meaningful macro-segmentation needs rather than per-closet or per-app vanity sprawl. Excessive VN counts inflate operational burden on borders, shared-services fusion, and troubleshooting; combining macro VNs with SGTs for micro-segmentation is the usual scalable pattern.