A mission critical application with four VMs have been deployed inside of a six-node Nutanix cluster. An alert is generated that a node in the cluster has failed and is no longer online. After the ale

The correct answer is C. Host Affinity. Host Affinity pins VMs to a specific host or set of hosts. When a node with Host Affinity-configured VMs fails, those VMs will NOT automatically restart on another node - they remain offline until their designated host recovers. This prevents the undesired reboot behavior describ

Nutanix Cluster Management

Question

A mission critical application with four VMs have been deployed inside of a six-node Nutanix cluster. An alert is generated that a node in the cluster has failed and is no longer online. After the alert, two of the VMs reboot and come back online on another node. Which feature, when configured, would have prevented the two VMs from rebooting?

Options

AHost Anti-Affinity
BVM High Availability
CHost Affinity
DProtection Domain

How the community answered

(32 responses)

A
9% (3)
B
3% (1)
C
81% (26)
D
6% (2)

Explanation

Host Affinity pins VMs to a specific host or set of hosts. When a node with Host Affinity-configured VMs fails, those VMs will NOT automatically restart on another node - they remain offline until their designated host recovers. This prevents the undesired reboot behavior described.

Host Anti-Affinity (A) is the opposite: it spreads VMs across different hosts to avoid co-location, but does not prevent restarts on failover.
VM High Availability (B) is exactly what CAUSED the reboots - HA automatically restarts VMs on surviving nodes when a host fails.
Protection Domain (D) is used for snapshot scheduling and replication, not for controlling VM placement or restart behavior.

Topics

#VM-Host Affinity#VM Placement Policy#High Availability#Node Failure

Community Discussion

No community discussion yet for this question.

Full NCA-5.15 Practice