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

vSphere vMotion is a technology that enables the migration of virtual machines (VMs) from one physical server to another while they are running, without downtime. This capability is particularly useful for transferring VMs to another portgroup that may be experiencing high latency. By utilizing vMotion, a vSphere administrator can relocate the VM to a portgroup with better performance and lower latency, thus ensuring that the VM continues to function optimally.

Vmotion works in conjunction with vCenter Server to manage the resources and overhead involved in the migration process, allowing for seamless moves of VMs. This is critical when dealing with high latency issues, as it can help maintain service availability and application performance by ensuring that VMs are placed on the most appropriate networks.

In contrast, the other options do not provide the necessary functionality for moving VMs from one portgroup to another during high latency situations. Network port binding relates to how a VM is connected to the network but doesn’t address VM migration. IP hash is a load balancing technique and does not facilitate VM transfers. Network I/O Control manages bandwidth allocation among VMs, which is separate from transferring VMs between portgroups. Thus, the choice of vSphere vMotion stands out as the most effective option for addressing