A township KVM pilot must use the same network-virtualization platform already running on ESXi. Which NSX Data Center benefit matches that use case?
Select an answer to reveal the explanation.
Short Explanation
The township does not need a second overlay product just because a lab is KVM. NSX-T was built for more than vSphere. NSX-V, a standard vSwitch, and Carbon Black are not that shared NV platform.
Full Explanation
A township KVM pilot that must share the network-virtualization platform already running on ESXi depends on NSX-T multi-hypervisor support so both hypervisors share one NV platform. That benefit is why NSX-T is chosen over older vSphere-only designs when civic innovation labs mix stacks. Claiming NSX-V remains the only supported platform for the KVM pilot fails the use case and the product history the exam expects. Forcing the pilot onto a vSphere Standard Switch with no overlay abandons shared network virtualization. Carbon Black Cloud is endpoint security, not a shared overlay fabric for both hypervisors. Exam caveat: multi-hypervisor support is an NSX-T identification point—do not award NSX-V or endpoint products. Operational check: prepare a KVM transport node into the existing overlay transport zone used by ESXi, attach a pilot segment, and verify bidirectional connectivity and DFW realization on both hypervisor types before expanding the township pilot. In municipal operations, record the chosen control and the rejected distractors in the change ticket so future on-call staff understand which failure modes would affect city services. Re-validate after the next maintenance window that the same design still holds for the current NSX build and the agency workloads that depend on it.