NCP-MCI-6.5 Free Practice Test

During an AHV upgrade, an administrator finds that a critical VM was powered off rather than migration to another host.
Which scenario explains this behavior?

1. A. NO AHV hosts were able to be scheduled.
2. B. The VM OS hung during migration.
3. C. The VM was on the same host as the acropolis leader.
4. D. The VM was marked as an agent VM.

Correct Answer: D
An agent VM is a special type of VM that is used for running services or applications that are not affected by high availability (HA) events or host maintenance. An agent VM is never migrated to any other host in the cluster. If an HA event occurs or the host is put in maintenance mode, agent VMs are powered off and are powered on on the same host once that host returns to a normal state. This behavior is different from regular VMs, which are migrated to another host in the cluster if possible, or restarted on the same host if not possible1.
Therefore, during an AHV upgrade, an administrator may find that a critical VM was powered off rather than migrated to another host if the VM was marked as an agent
VM. This can be done either from the Prism web console by selecting the Use this VM as an agent VM option in the Update VM dialog box, or from the aCLI by using the vm.create or vm.update commands with the agent_vm=true parameter2. To avoid this situation, the administrator should ensure that any critical VMs are not marked as agent VMs before starting the AHV upgrade.
Reference: AHV Networking Best Practices