VMware 5V0-22.21 Practice Test - Questions Answers, Page 13

The vSAN administrator should check VMKNICs, uplinks, physical switches, and associated settings.

High network latency can be caused by incorrect networking configurations or misconfigured switch settings. By checking the VMKNICs, uplinks, and switches, the vSAN administrator can identify any potential causes of the high network latency and take steps to remedy them.

Roll back the vLCM configuration to the latest compliant image. After saving the configuration, all hosts in the cluster are out of compliance, so the next step is to roll back the vLCM configuration to the latest compliant image. This can be done by selecting the “Roll Back” option from the vLCM image selection menu. Reference: https://docs.vmware.com/en/VMwarevSphere/7.0/com.vmware.vsphere.upgrade.doc/GUID-B2F7B3A3-BD7F-4A4F-A77C- 90F4B7EAC54F.html

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.

To add the vSAN Witness Appliance to the cluster as a host, the vSAN administrator can either deploy and configure the vSAN Witness Appliance OVA, or add the vSAN Witness Appliance ESXi host to the vSAN cluster. Reference: https://docs.vmware.com/en/VMwarevSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-F7DDC9E9-C7D1-4FE1-A5D5-F3F7A8A2B0F3.html

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-612FD656-5C18-4F89-80A5-3A01E89E0FB6.html

Check health of the system using Skyline Health for vSphere

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-612FD656-5C18-4F89-80A5-3A01E89E0FB6.html

https://core.vmware.com/resource/vmware-vsan-design-guide

VMware vSAN Design Guide | VMware

https://core.vmware.com/resource/vmware-vsan-design-guide

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-703-releasenotes.html

VMware vCenter Server 7.0 Update 3 Release Notes

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-703-releasenotes.html

1. 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-byone.

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-generalavailability.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/VMwarevSphere/7.0/com.vmware.vsphere.storage.doc/GUID-C1E7F9A5-7F5E-4E7E-A012-2F0F19A3F0A4.html

In order to complete this task, the vSAN administrator should take action D. Change the default policy to force provisioning to spread components across hosts. This can be done by enabling the ‘Force Provisioning’ option in the storage policy. Reference: https://docs.vmware.com/en/VMwarevSphere/ 7.0/com.vmware.vsphere.storage.doc/GUID-F9F1C7A2-B9F2-4E2C-ABF7- 634B2E2D7ABF.html

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vmware-vsan-701-release-notes.htmlVMware vSAN 7.0 Update 1 Release Notes

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vmware-vsan-701-release-notes.html

https://core.vmware.com/resource/vsan-operations-guidevSAN Operations Guide | VMware

https://core.vmware.com/resource/vsan-operations-guide

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/performance/vsphere-esxi-vcenter-server-70-performance-best-practices.pdf

Performance Best Practices for VMware vSphere 7.0

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/performance/vsphere-esxi-vcenter-server-70-performance-best-practices.pdf

This is because vSAN maintains a copy of the object on each host that is a member of the vSAN cluster. When a host enters maintenance mode, the object's replica is moved to another host in the cluster. If another host in the cluster fails during this time, it's possible that the updated replica of an object may be lost. However, vSAN will still use the stale replica of the object on the host that exited maintenance mode to service read requests, and will update the stale replica with the latest writes from the remaining host after the host exits maintenance mode.

It is important to note that this scenario assumes that the host failure is a permanent failure and that vSAN does not have any additional data protection methods enabled such as RAID-5, RAID-6, or Erasure Coding.

The correct answer is D. The latest writes from Host-2 are applied to the stale components of Host-1 once the host exits maintenance mode. This is because vSAN utilizes a "write-order fidelity" mechanism which ensures that any writes that were committed to the other hosts in the cluster before Host-1 entered maintenance mode are applied to the stale components of Host-1 as soon as the host exits maintenance mode. Reference: https://docs.vmware.com/en/VMwarevSphere/ 7.0/com.vmware.vsphere.storage.doc/GUID-C1E7F9A5-7F5E-4E7E-A012- 2F0F19A3F0A4.html

When a host goes offline, it may cause errors on the vCenter dashboard, and the summary page of the VMs may display Noncompliant VM Storage Policies. The administrator should check the vSAN object health to identify and repair any objects that are in a non-compliant state. The following steps can be taken:

Go to the vCenter Server's Monitor tab

Select vSAN from the left-hand menu

Select Skyline Health from the sub-menu

Select Data from the sub-sub-menu

Select vSAN object health

This will give you an overview of the vSAN object health, you can check the objects that are in a noncompliant state and use the "Repair Objects" button to repair them.

It's important to also check the reason why the host was offline, and fix it before bringing it back to the cluster.

You can also check the triggered alarms related to vSAN in Monitor -> Triggered Alarms -> vSAN object alarms, to ensure that all issues related to vSAN are resolved.

This page will display any objects that are not compliant with the storage policy and will allow the administrator to take the necessary steps to repair the objects and bring the VMs back into compliance.

The Cache Disk will be marked as failed, and the Ensure Accessibility option will be required before any components are rebuilt. When a single cache disk fails within one of the vSAN hosts, the Disk Group will be marked as failed and the Ensure Accessibility option will be required before any components are rebuilt. The Ensure Accessibility option will rebuild the components on other cache disks, as long as sufficient capacity is available.

Reference: https://docs.vmware.com/en/VMwarevSphere/6.7/com.vmware.vsphere.vsan.doc/GUID-F7CC6CDB-B8C8-4F66-BEE0-E82C6D8F1F9C.html