An administrator determines that when a host residing in a High Availability (HA) cluster fails, the
virtual machines fail to restart on a remaining host, or will only restart after a long delay.
Which two conditions would account for this behavior? (Choose two.)
A.
The virtual machines were not protected by vSphere HA at the time the failure occurred.
B.
Distributed Resource Scheduler was not enabled at the time the failure occurred.
C.
There is insufficient spare capacity on hosts with which the virtual machines are compatible.
D.
The virtual machines contain physical Raw Device Mappings.
Explanation:
That’s a fucking hard one.
0
0
A and C are correct
vSphere HA might not restart a virtual machine after a failure or might delay its restart for several reasons.
Virtual machine is not protected by vSphere HA at the time the failure occurred
Insufficient spare capacity on hosts with which the virtual machine is compatible
vSphere HA attempted to restart the virtual machine but encountered a fatal error each time it tried.
Restart actually succeeded.
http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-A2FF35B8-62FF-4960-82F1-EA5E0C912CB7.html
0
0
http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.troubleshooting.doc%2FGUID-A2FF35B8-62FF-4960-82F1-EA5E0C912CB7.html
0
0
concur
0
0
damn question. the real answer in a real scenario where this might happen is C.
My reasoning is this:
when the host fails, the remaining ones start recovering virtual machines as much as they can, as the whole cluster might be overloaded vms will possible have a long delay when starting, once capacity is reached, the rest of the vms will remain down.
Now in the other hand, if a vm is not HA covered it won’t start no matter what.
As it is written, this questions mislead people to think that the same vm can or cannot restart. it would be different if it said, some vms fail to restart, and some other restart with a long delay.
0
0