Which two options does VM Monitoring use to determine if a virtual machine should be reset? (Choose two.)
A.
Network activity from the virtual machine
B.
I/O activity from the virtual machine
C.
CPU activity from the virtual machine
D.
Heartbeats from VMware Tools
Explanation:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.avail.doc_50%
2FGUID-62B80D7A-C764-40CB-AE59-752DA6AD78E7.html
B and D is correct
I’m agree.
===============
https://blogs.vmware.com/vsphere/2014/03/vsphere-ha-vm-monitoring-back-basics.html
What is vSphere HA VM monitoring ? HA VM monitoring will restart a VM if:
That VMs VMware Tools heartbeats are not received in a set period of time (see below for details) and
The VM isn’t generating any storage or network IO (for 120 seconds by default, though this can be changed using the following advanced cluster level setting: das.iostatsInterval)
===============
For 6.5
VM and Application Monitoring
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.avail.doc/GUID-62B80D7A-C764-40CB-AE59-752DA6AD78E7.html
When you enable VM Monitoring, the VM Monitoring service (using VMware Tools) evaluates whether each virtual machine in the cluster is running by checking for regular heartbeats and I/O activity from the VMware Tools process running inside the guest. If no heartbeats or I/O activity are received, this is most likely because the guest operating system has failed or VMware Tools is not being allocated any time to complete tasks. In such a case, the VM Monitoring service determines that the virtual machine has failed and the virtual machine is rebooted to restore service.