Nutanix Certified Associate Practice Exam

Why might a VM not restart as expected after a host reboots in an all-AHV environment?

1. The VM was encrypted and failed to decrypt

2. The affinity for the VM is set for only the host that is rebooted

3. The VM’s resources were insufficient after migration

4. The VM configuration was corrupted during the reboot process

The correct answer is: The affinity for the VM is set for only the host that is rebooted

Choosing the option regarding VM affinity settings is appropriate because it addresses a fundamental aspect of how virtual machines (VMs) are managed in an AHV (Acropolis Hypervisor) environment. When a VM is deployed with an affinity rule, it is specified to run only on certain host(s) in the cluster. If the VM has an affinity for a host that is currently being rebooted, it will not be able to restart since its designated host is unavailable. In an AHV environment, if all the resources of a VM are tied to a specific host that is down, the system cannot dynamically relocate the VM to another host due to that affinity setting. This situation results in the inability of the VM to power on until the host is back online and fully operational, thus preventing the VM from restarting as expected. Understanding the implications of affinity rules is crucial, as they dictate how VMs are distributed across hosts, balancing load and ensuring performance. This option underscores the importance of considering affinity settings when troubleshooting VM restart issues post-host reboots.