The following three hosts are being put into a virtualization cluster for a new project initiative: As more VMs are deployed to the cluster, which of the following virtualization technologies is…

High availability monitors host-level failures and orchestrates VM restarts on surviving hosts - it does not produce errors simply because VM density on the cluster increases.

The balloon driver inflates inside a guest OS to force it to release memory pages back to the hypervisor, but if the guest itself is under memory pressure it cannot satisfy the reclamation request, causing the hypervisor to log a ballooning error. As additional VMs are deployed to a cluster with finite physical RAM, memory pressure builds and ballooning is triggered more aggressively, increasing the frequency of these errors. Unlike overcommitment or hyperthreading, ballooning has a direct guest-level driver dependency that can fail explicitly and visibly when guests are uncooperative or lack the driver.

Memory overcommitment is a configuration policy allowing more virtual RAM to be provisioned than physical RAM exists; it does not itself throw errors but delegates reclamation work to mechanisms such as ballooning, swapping, and transparent page sharing.

Hyperthreading exposes logical CPU threads to the hypervisor and does not generate errors as VM density grows unless raw CPU capacity is fully exhausted, which is a distinct and separate constraint from memory resource pressure.