Free 5V0-22-23 Vmware 5V0-22-23 Practice Test Question - Page 3

Question 7 (Topic 1)

After a planned power outage, an administrator decided to restart the vSAN cluster manually. What is the correct sequence of steps for the administrator to follow after powering on the ESXi hosts?

Select an option, then click Submit answer.

○ 1. Enable cluster member updates from vCenter Server only on one ESXi host. 2. Run the python reboot helper script only on one ESXi host to recover the cluster. 3. Exit all hosts from maintenance mode.
○ 1. Exit all hosts from maintenance mode. 2. Run the python reboot helper script only on one ESXi host to recover the cluster. 3. Enable cluster member updates from vCenter Server on all ESXi hosts.
○ 1. Exit all hosts from maintenance mode. 2. Enable cluster member updates from vCenter Server only on one ESXi host. 3. Run the python reboot helper script only on one ESXi host to recover the cluster.
○ 1. Enable cluster member updates from vCenter Server on all ESXi hosts. 2. Run the python reboot helper script on all ESXi hosts to recover the cluster. 3. Exit all hosts from maintenance mode.

Reference / correct answer:

1. Exit all hosts from maintenance mode. 2. Run the python reboot helper script only on one ESXi host to recover the cluster. 3. Enable cluster member updates from vCenter Server on all ESXi hosts.

Most accepted answer: B. 1. Exit all hosts from maintenance mode. 2. Run the python reboot helper script only on one ESXi host to recover the cluster. 3. Enable cluster member updates from vCenter Server on all ESXi hosts.

Community votes: B=3

Selected Answer: B B. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-monitoring.doc/GUID-31B4F958-30A9-4BEC-819E-32A18A685688.html upvoted 2 times

Selected Answer: B When all the hosts are back after powering on, exit all hosts from maintenance mode. If the vCenter Server is powered off, use the following command on the ESXi hosts to exit maintenance mode. esxcli system maintenanceMode set -e false Perform this step on all the hosts. Run the following command only on that host. If you run the command on multiple hosts concurrently, it may cause a race condition causing unexpected results. python /usr/lib/vmware/vsan/bin/reboot_helper.py recover Enable cluster member updates from vCenter Server by running the following command on the ESXi hosts in the cluster. Ensure that you run the following command on all the hosts. esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-monitoring.doc/GUID-31B4F958-30A9-4BEC-819E-32A18A685688.html upvoted 1 times

Selected Answer: B B - Correct upvoted 1 times

B correct https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-monitoring.doc/GUID-31B4F958-30A9-4BEC-819E-32A18A685688.html upvoted 1 times

B. 1. Exit all hosts from maintenance mode. 2. Run the python reboot helper script only on one ESXi host to recover the cluster. 3. Enable cluster member updates from vCenter Server on all ESXi hosts. upvoted 1 times

Question 8 (Topic 1)

After a server power failure, the administrator noticed the scheduled resyncing in the cluster monitor displays objects to be resynchronized under the pending category. Why are there objects in this category?

Select an option, then click Submit answer.

○ The delay timer has not expired.
○ These objects belong to virtual machines, which are powered off.
○ Object resynchronization must be started manually.
○ There are too many objects to be synchronized.

Reference / correct answer:

There are too many objects to be synchronized.

Most accepted answer: D. There are too many objects to be synchronized.

Community votes: D=2

Selected Answer: D Answer D is correct. As detailed by kernelkraut, if it is marked "pending", that means the timer is expired, and the objects are yet to be synchronized. upvoted 1 times

"Pending" implies the delay timer has already expired but that there are not enough resources available to re-sync those objects. The only valid choice left is D. Reference: https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-monitoring-troubleshooting/GUID-57D74904-A8C4-4F3B-8D2A-1017AA8EBA85.html Remaining number of objects to be resynchronized. You can classify scheduled resyncing into two categories: scheduled and pending. The scheduled category displays the objects that are not resyncing because the delay timer has not expired. Resynchronization of objects starts once the timer expires. The pending category displays the objects with the expired delay timer that cannot be resynchronized. This can be due to insufficient resources in the current cluster or the vSAN FTT policy set on the cluster not being met. upvoted 2 times

A is correct: Scheduled resyncing Remaining number of objects to be resynchronized. You can classify scheduled resyncing into two categories: scheduled and pending. The scheduled category displays the objects that are not resyncing because the delay timer has not expired. Resynchronization of objects starts once the timer expires. The pending category displays the objects with the expired delay timer that cannot be resynchronized. This can be due to insufficient resources in the current cluster or the vSAN FTT policy set on the cluster not being met upvoted 1 times

D. There are too many objects to be synchronized. upvoted 2 times

Selected Answer: D D - to many objects to resyn upvoted 3 times

Free 5V0-22-23 – Vmware 5V0-22-23 Practice Test Question