5V0-22.21 Dumps with Practice Exam Questions Answers

Site Recovery Manager (SRM) provides disaster recovery orchestration for workloads on a vSAN stretched cluster to a third site. SRM is a disaster recovery solution that automates the recovery and migration of virtual machines between sites. It allows you to protect your applications and data by failing over to a secondary site in case of a disaster or planned maintenance. SRM also enables testing of recovery procedures without impacting production workloads.

C. Enter Maintenance Mode, confirm that pre check is fine, select "Full data migration", "Shutdown ESXi host", replace all capacity devices, "Restart ESXi host", replace capacity devices in disk groups, exit Maintenance Mode, confirm that raw capacity has been increased, and then repeat on ESXi host one-by-one. D. "Shutdown ESXi host", and replace all capacity devices. Repeat this sequence one-by-one.

Option C would allow you to perform a full data migration, which will move all data from the old capacity device to other devices. This option allows for the vSAN cluster to remain offline during the replacement process, and it allows the vSAN administrator to replace all the capacity devices at once.

Option D would also allow you to replace all capacity devices at once, however, the data is not moved from the old capacity device to other devices, this option also allows for the vSAN cluster to remain offline during the replacement process and it allows the vSAN administrator to replace all the capacity devices at once.

You can find more information on adding capacity to a vSAN cluster in the vSphere 7.0 documentation: https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-70-vsphere-storage-vsan-70-upgrade-guide.pdf and also in VMware blog like: https://blogs.vmware.com/vsphere/2021/03/vsphere-7-0-update-1-vsan-7-0-update-1-general-availability.html

The two approaches the vSAN administrator can use to complete this task are C. Enter Maintenance Mode, confirm that pre check is fine, select "Full data migration", "Shutdown ESXi host", replace all capacity devices, "Restart ESXi host", replace capacity devices in disk groups, exit Maintenance Mode, confirm that raw capacity has been increased, and then repeat on ESXi host one-by-one and D. "Shutdown ESXi host", and replace all capacity devices. Repeat this sequence one-by-one. Reference: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-C1E7F9A5-7F5E-4E7E-A012-2F0F19A3F0A4.html

he correct answers are B and E. Changing the failure tolerance method and enabling object checksum (from checksum disabled) both result in a component resync. When the failure tolerance method is changed, the components of the objects stored on the vSAN datastore need to be rebuilt in the new format, which requires a component resync. Similarly, when object checksum is enabled, the components of the objects stored on the vSAN datastore need to be rebuilt in order to enable checksum.

You can find this information in the VMware vSAN 6.7 Documentation, in the section titled 'Storage Policy Rules': https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan.doc/GUID-F54F0A1F-D9E7-46FD-86F8-6F47A6FAE17C.html

vSAN 2-Node Cluster Guide | VMware

https://core.vmware.com/resource/vsan-2-node-cluster-guide

VCP-DCV for vSphere 7.x (Exam 2V0-21.20) Official Cert Guide, 4th ...

https://douran.academy/wp-content/uploads/ebooks//vcp-dcv-for-vsphere-7.x.pdf

vSAN 70u3 Proof of Concept Guide | VMware

https://core.vmware.com/resource/vsan-70u3-proof-concept-guide

A stretched cluster in vSAN requires a reliable, low latency Layer 3 communication from the data sites to the witness site. Therefore, an interruption of Layer 3 communication from the data sites to the witness site could cause a vSAN stretched cluster to fail. Additionally, blocked UDP ports on the firewall between data sites and high latency (RTT) of more than 5ms between data sites could also cause failure of the vSAN stretched cluster.