County health wants to scale network isolation for clinic VMs without buying a larger chassis switch. Which SDDC concept does that requirement illustrate?
Select an answer to reveal the explanation.
Short Explanation
Need more isolated clinic networks? In an SDDC you grow software capacity, not the chassis in the closet. Isolation scales as virtual services, not as a forklift.
Full Explanation
County health wants to scale network isolation for clinic VMs without buying a larger chassis switch. That illustrates network services scaling as software capacity rather than only by forklifting a larger physical chassis. Overlay segments and distributed policy consume control-plane and host capacity, so additional clinic isolation is created as objects on the prepared fabric instead of as a bigger switch SKU. Requiring a new chassis in every clinic closet before isolation can grow is the traditional constraint the SDDC removes. Treating clinic isolation as a Horizon client-mode setting misses the network-virtualization control point. Converting NSX-T to NSX-V VXLAN is an irrelevant product-era distraction and not how isolation scales. Exam caveat: software scale still has limits—transport-node capacity, Edge sizing, and underlay bandwidth—but those are capacity plans, not per-clinic chassis forklifts. Operational check: provision an additional clinic segment and distributed firewall policy on existing transport nodes and confirm isolation without a hardware refresh ticket. Keep municipal naming and change tickets aligned with the software objects so civic audits can trace intent.