Water-plant IT keeps a duplicate physical switch stack per agency for isolation. Which traditional pattern does virtual networking replace?
Select an answer to reveal the explanation.
Short Explanation
A second switch stack per agency is buying a second water main when valves would do. Logical segments and policy isolate traffic on shared hardware. The plant should not purchase a whole extra fabric just to keep agencies apart.
Full Explanation
Duplicate physical fabrics—one switch stack per agency—are a traditional isolation pattern virtual networking replaces with logical isolation on shared hardware. Water-plant IT can give agencies separate segments and policies without buying a separate network per department. Isolation does not always require duplicate physical fabrics when NSX-T is present. Duplicate Horizon pods are not the replacement model for department networks. A second Carbon Black Cloud instance per agency does not create network isolation fabrics. Exam caveat: highly sensitive OT zones may still warrant physical separation by policy; the exam point is that routine agency isolation need not mean duplicate chassis. Operational check: migrate two agency test workloads onto shared hosts with separate overlay isolation and retire a lab duplicate ToR pair as proof of concept. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent. Prefer verifying with a non-production agency workload before promoting the same pattern to life-safety systems. Record realization state and underlay health in the runbook used by on-call city operators. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent.