Recycling-center hosts must carry Geneve overlay and VLAN-backed NSX traffic. Which switch role on the host carries that overlay?
Select an answer to reveal the explanation.
Short Explanation
The prepared host switch is an N-VDS or an NSX-enabled VDS — that is the on-host fabric for overlay and NSX VLANs. A leftover standard switch, a sensor, or BLAST is not that switch.
Full Explanation
On ESXi transport nodes, overlay and VLAN-backed NSX traffic rides an N-VDS or an NSX-enabled vSphere Distributed Switch—the on-host fabric recycling-center hosts need for Geneve overlay and NSX VLAN traffic. A standalone vSphere Standard Switch is not the NSX overlay host switch and cannot be treated as the prepared data-plane switch for this use case. Carbon Black sensors do not become the host virtual switch. Horizon BLAST is a desktop display protocol, not the overlay data plane on the hypervisor. Exam caveat: whether the design uses N-VDS or NSX-enabled VDS, the host switch must be the NSX-prepared switch consuming the uplink profile—not a leftover standard switch beside it. Operational check: on a recycling-center host, confirm the NSX host switch is N-VDS or NSX-enabled VDS with the expected uplinks, attach a test overlay VM, and verify Standard Switch, Carbon Black, and BLAST were not named as the overlay switch. Keep the civic framing visible in runbooks so the next operator can restate why the correct control fits the agency outcome, why each distractor fails by concept, and which Manager or fabric view proves the design after change. Keep the civic framing visible in runbooks so the next operator can restate why the correct control fits the agency outcome, why each distractor fails by concept, and which Manager or fabric view proves the design after change.