Utility-billing operators want “who can talk to whom” policies to travel with workloads when VMs move between racks. Which SDDC trait should they identify?
Select an answer to reveal the explanation.
Short Explanation
When a billing VM moves racks, the rule should ride along like a badge on the worker, not stay glued to the old cubicle wall. SDDC policy lives on virtual constructs and workloads, not only on a physical port.
Full Explanation
In an SDDC, security and network policy can be defined on virtual constructs and workloads so it follows the VM across hosts and racks. That is how utility-billing isolation survives vMotion without a port rewrite. Binding policy only to a physical port or VLAN, substituting Horizon clones, or recabling after vMotion are traditional or out-of-scope approaches.