A virtual machine named VM01 is running on Host01 on a four-node vSAN cluster. vSphere HA is enabled for the cluster. vSphere HA host isolation response is set to Power off and

restart VMs. VM01 has a storage policy assigned to it that contains the rule Primary level of failures to tolerate = 1.

A network failure occurs that causes a vSAN network partition. Host01 is isolated from the rest of the cluster. The other three nores a

re NOT affected by the network failure.

How does this network failure impact VM01?

A. vSphere HA attempts to restart VM01 on Host01 after the number of minutes configured in the VSAN ClomRepairDelay advanced setting has elapsed.

B. vSphere HA immediately

attempts to restart VM01 on Host01.

C. vSAN rebuilds all components that belong to VM01 on other nodes in the cluster. After the rebuild is complete vSphere HA attempts to restart VM01 on a node other than Host01.

D. vSphere HA powers off Vm01 and attempt

s to restart it on a node other than Host01.

Explanation:

vSAN will wait for 60 minutes by default and then rebuild the affected data on other hosts in the cluster. The 60-minute timer is in place to avoid unnecessary movement of large amounts o

f data. As an example, a reboot takes the host offline for approximately 10 minutes. It would be inefficient and resource intensive to begin rebuilding several gigabytes or terabytes of data when the host is offline briefly.

vSphere HA is tightly integrate

d with vSAN. The VMs that were running on a failed host are rebooted on other healthy hosts in the cluster in a matter of minutes. A click-through demonstration of this scenario is available here: vSphere HA and vSAN 50 VM Recovery.

Recommendation: Enable

vSphere HA for a vSAN cluster.

Reference: vSAN Frequently Asked Questions (FAQ).pdf (Page 11)