A company's Type 2 hypervisor host is running several production virtual machines. The administrator needs to move a running VM to a different physical host with no noticeable downtime for users. Which feature should the administrator use?
Live migration moves a running virtual machine between hosts while preserving its state, so users experience little or no interruption. It is designed exactly for relocating active workloads during maintenance or load balancing. Because the requirement is to move a running VM with no noticeable downtime, live migration is the appropriate feature.
Why this answer
Live migration is the feature that transfers a running virtual machine between physical hosts while keeping it available to users. Snapshots, cloning, and resource pooling serve different purposes such as rollback, duplication, and capacity sharing, and none of them relocate an active VM to another host with no noticeable downtime.
Exam trap
The trap here is confusing a snapshot, which preserves a point-in-time state, with live migration, which actually moves a running VM to another host.