Wastewater SCADA owners fear that an SDDC means plant traffic shares a broadcast domain with 311 web VMs on the same hosts. Which SDDC isolation concept should they identify?
Select an answer to reveal the explanation.
Short Explanation
Same hosts do not mean the same hallway. Overlay isolation lets plant traffic and 311 VMs share hypervisors without sharing a broadcast domain.
Full Explanation
Wastewater SCADA owners fear that sharing hypervisor hosts with 311 web VMs means sharing a broadcast domain. In an SDDC, many logical networks can coexist on the same hypervisor hardware without sharing a broadcast domain because overlay segments isolate Layer-2 domains even when hosts are shared. Plant traffic and citizen-portal VMs can therefore share clusters while remaining on separate logical networks and security policies. Shared hardware does not imply a single Layer-2 domain. Moving 311 to SaaS is unrelated to host-level overlay isolation. Installing Carbon Black on PLCs does not create network broadcast isolation between VM segments. Exam caveat: isolation still requires correct segment assignment, tagging, and distributed firewall rules; co-residency without policy is not automatic safety. Operational check: place a SCADA test VM and a 311 test VM on the same host on different overlay segments and confirm they do not share ARP/broadcast scope unless routing and policy explicitly allow communication. 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.