Exam 2V0-21.19 topic 1 question 58 discussion

Correct answer is B https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-33A65FF7-DA22-4DC5-8B18-5A7F97CCA536.html It will first check DataStore Heartbeat before restating VMs

The master host monitors the liveness of the subordinate hosts in the cluster. This communication happens through the exchange of network heartbeats every second. When the master host stops receiving these heartbeats from a subordinate host, it checks for host liveness before declaring the host failed. The liveness check that the master host performs is to determine whether the subordinate host is exchanging heartbeats with one of the datastores. See Datastore Heartbeating. Also, the master host checks whether the host responds to ICMP pings sent to its management IP addresses. https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-4ED552C3-0291-4553-A46A-290EF883BC8D.html Answer is B - as we are not told the Master has exhausted all the liveliness checks

No doubt, it's B. If the question had stated "a failed host," then the answer would be D. But since the question says the host is unreachable on the mgmt network, the next step is to check datastore heartbeating. Only after that check is the failure type determined, which may or may not lead to restarting VMs.

The correct answer is B, 1. check for n/w heartbeat 2. check datastore heartbeat only when both are missing Master host will declare slave host is dead and then 3. VM's will be restarted on other available hosts

Correct answer is B. from vSphere documentation: "When the master host in a vSphere HA cluster can not communicate with a slave host over the management network, the master host uses datastore heartbeating to determine whether the slave host has failed, is in a network partition, or is network isolated. If the slave host has stopped datastore heartbeating, it is considered to have failed and its virtual machines are restarted elsewhere." https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.avail.doc_50%2FGUID-0502B198-F5F7-4101-969C-C5B6F364C678.html

Correct answer is B https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-0502B198-F5F7-4101-969C-C5B6F364C678.html#GUID-0502B198-F5F7-4101-969C-C5B6F364C678

Correct answer B. Checked in egzam.

B - correct answer. https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.avail.doc_50%2FGUID-B9ACCE9B-A14D-4B2F-87EF-4B0A67ABDF58.html

the Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.avail.doc_50%2FGUID-B9ACCE9B-A14D-4B2F-87EF- 4B0A67ABDF58.html is relevant to vSphere 5.0 not to 6.7 , please note changes!!!

when the Master Host a failed to communicate with the slave host using the Management Network (dedicated network use for ESXi VMkernel hosts to talk with each other) , Than its try again using Datastore Heartbeats to check if the Host is alive! how it do it? every Slave ESXi hosts has empty files created by the fdm agent inside the shared Datastores was selected automatically or by the user. so.... if the Master Host failed to communicate over the management network ,then the fdm agent used for datastore heartbeat to check if the empty file was related to ESXi exits or not!! if not exist on both datastores (need to be at least 2 Datastores) then the hosts is down !! and the the VMs restarted to be host on others ESXi Correct answer is B

Correct Answer is D, because of below. Ultimately vSphere HA will restart, as we need to consider if it is a vSAN datastore, then heartbeating will not work. KB article: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-0502B198-F5F7-4101-969C-C5B6F364C678.html Note: A vSAN datastore cannot be used for datastore heartbeating. Therefore, if no other shared storage is accessible to all hosts in the cluster, there can be no heartbeat datastores in use. However, if you have storage that is accessible by an alternate network path independent of the vSAN network, you can use it to set up a heartbeat datastore.

Correct Ans is B. because in question they have mentioned if master is unable to communicate with slave host over a management network so he will try to comunicate through datastore.

Correct answer is C If the master host fails, is shut down or put in standby mode, or is removed from the cluster a new election is held. https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-672-availability-guide.pdf

B is correct - the HA Master - if it does not hear back from a slave, it could be that the network alone is down., not the actual slave, so the master will check the lock on the datastore file where the slaves send a heartbeat to - if there is no lock, the master will assume the slave is down and will then look for new slave(s) to power up the failed slave's VMs on.

Should be C. HA election occurs when you enable HA on VMware Cluster and master host:- Fails Become Network partition or isolated. Disconnect from vCenter Server. Put in maintenance or standby. HA election takes 15 seconds to elect slave as a master. It works over UDP protocol https://cloudpathshala.com/2018/09/01/how-vmware-ha-works-deep-dive/ And After Election then VM could be restarted by the new Master https://www.dtechinspiration.com/high-availability-harequirementsfundamental-componentsconfiguring/ The master host election takes about 15 secs and is conducted using UDP port. HA won’t react to any failure during the master election once the master is elected failures occur during or after is taking care by master.

Correct Answer is B When the master host in a VMware vSphere® High Availability cluster cannot communicate with a subordinate host over the management network, the master host uses datastore heartbeating to determine whether the subordinate host has failed, is in a network partition, or is network isolated. If the subordinate host has stopped datastore heartbeating, it is considered to have failed and its virtual machines are restarted elsewhere. https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.avail.doc/GUID-0502B198-F5F7-4101-969C-C5B6F364C678.html It will first use Datastore Heartbeating and if that doesn't work as well, it will restart VMs

Monitoring the state of slave hosts. If a slave host fails or becomes unreachable, the master host identifies which virtual machines need to be restarted.