GIS mapping virtual machines must vMotion between county hosts. Which vSphere networking object carries that host service, rather than guest application traffic?
Select an answer to reveal the explanation.
Short Explanation
vMotion rides a staff-only hallway on the host, not the GIS guest's own front door. That hallway is a VMkernel adapter. The guest vNIC carries map-app traffic, and an NSX firewall rule or overlay name does not become the vMotion stack.
Full Explanation
VMkernel adapters are host-stack interfaces that carry ESXi services such as management, vMotion, iSCSI, and vSAN. Live migration of GIS VMs requires a VMkernel adapter enabled for vMotion on each participating host. Guest vNICs belong to the virtual machines and carry application traffic. Distributed Firewall rules and overlay segments are NSX objects and do not replace the vSphere VMkernel port that provides the vMotion service.