Which option can a vSphere administrator utilize to transfer VMs to another portgroup experiencing high latency?

The ability to transfer virtual machines (VMs) to another portgroup, especially when facing high latency, is accomplished through vSphere vMotion. This feature allows a vSphere administrator to migrate running VMs from one host to another without any downtime. It does this while they are live, ensuring business continuity while addressing network performance issues.

Using vMotion to move VMs to a different portgroup can help the administrator switch the VMs to a networking path that provides better performance or lower latency. This capability is crucial in maintaining application availability and responsiveness and ensures optimal resource utilization across the virtual environment.

While other options might relate to improving network performance or managing resources, they do not serve the specific purpose of migrating a VM from one portgroup to another. For example, Network Port Binding is concerned with how virtual network adapters are connected to physical NICs, IP hash pertains to load balancing in distributed port groups, and Network I/O Control regulates bandwidth usage across virtual networks. These do not directly enable the live migration of VMs as vMotion does.