Refer to the Exhibit.
An administrator is applying patches to a batch of ESXi 5.x hosts in an under-allocated HA/DRS cluster. An attempt is made to place the host into maintenance mode, but the progress has stalled at 2%. DRS are configured as shown in the exhibit. Of the four choices below, two would effectively resolve this issue.
Which two steps could be taken to correct the problem? (Choose two.)
A.
Manually migrates any running virtual machines to another host
B.
Set the cluster to Fully Automated
C.
Disable HA Monitoring to allow Maintenance Mode to proceed
D.
Set the cluster migration threshold to Aggressive
Explanation:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&extern alId=1007156
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&extern alId=1036167
– If an ESX host is a part of VMware High Availability (HA) or DR’S cluster, check the Admission Control settings. You may have to disable this option if there are not enough resources to ensure fail over capacity.
– If you want vCenter Server to migrate your running virtual machines automatically to other hosts when placing your host in maintenance mode, DR’S must be enabled in your cluster in the Fully Automated mode.
So my responses are B and C. I think if you change DRS settings through a MM placement it will migrate them… please share your thoughts at: (and try it out in your lab) http://certcollection.org/forum/topic/143147-vcp-510-updated-dump-and-links/
I think the important piece of information here is that the cluster in under-allocated, meaning there shouldn’t be resource contention therefore no need to violate HA constraints while patching. I think in this case A and B would be the correct answers. Also, you do not know what the status of HA is, it could already be disabled.
This is related to DRS only and we are talking about vmotion through DRS. HA is not in picture at all.
So answer should be A and B