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

The maximum time range that can be stored by the vSAN health check history is 180 days (C).

According to the VMware Official Guide, “The vSAN Health Check history is stored for up to 180 days before it is automatically purged.”

To create a Kerberos secured NFS v4.1 file share, minimally the Active Directory Domain (D), Organizational Unit (A), User Account (A), and Password (A) must be provided during the configuration of the File Service. According to the VMware Official Guide, “To configure Kerberossecured NFS v4.1 file share, you must provide the Active Directory domain, organizational unit, user account, and password.”

The three topics that would impact the design of a new vSAN cluster to host production mission critical workloads are A. The amount of ESXi host memory, D. The size of the cache tier according to workload characteristics, and E. The supported CPU type of the ESXi host.

The amount of ESXi host memory is important because it determines the amount of memory available to virtual machines, which can impact the performance of the applications running on them.

The size of the cache tier according to workload characteristics is also important as it determines how much write buffer memory is available to the vSAN cluster. This is essential as write buffer memory helps to ensure high performance and low latency.

Finally, the supported CPU type of the ESXi host is important as this will impact the performance of the cluster, as well as compatibility with certain applications.

For more information, see the official VMware guide on vSAN cluster design:

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan.doc/GUID-E1A6F9E6-8D6B-4F2D-A554-E8D97

The default health check interval for the vSAN Health services is every 10 minutes. This interval is used by the vSAN Health service to monitor the health of the vSAN cluster and report any anomalies it finds. The vSAN Health service is responsible for running the health checks and if any issues are detected, it will notify the administrator. For more information, see the official VMware guide on vSAN Health Service: https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenterserver- 67-vsan-health-service-guide.pdf

The RAID configuration that the administrator must use in this storage policy to achieve the best performance for the database virtual machines is RAID-6.

RAID-6 is an effective configuration for a vSAN cluster with eight hosts as it allows for two hosts to fail and still maintain protection of the data. RAID-6 is a data striping configuration with two parity bits stored across multiple disks, which improves read performance while also providing fault tolerance.

For more information, see the official VMware guide on vSAN Storage Policies:

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan.doc/GUIDDAC07A3E-A077-4A93-A9D0-9CBB2F4F4B4D.html

You can silence the vSAN health status alerts from the vCenter HTML client. This will prevent vCenter from sending notifications during the scheduled maintenance window. To silence an alert, you can navigate to the "Monitoring" tab, go to "Alarms" and click on the desired alert to open its settings.

From there, you can select "Actions" and then "Silence Alarm". This will prevent notifications for the selected alert until it is cleared or unsilenced.

Please note that this is not a permanent solution and will need to be reapplied after maintenance if desired. Reference: https://docs.vmware.com/en/VMwarevSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-E5D5F4A4-2F5C-4F6E-9E97- 8CBB3D3F3E6B.html

This is the most efficient way of configuring a vSAN Direct Configuration on an existing cluster because it does not require the administrator to delete any existing disk groups or add any additional disks. The administrator can use the vSphere Client or vSphere Web Client to view the available disks in the Disk Management tab [1], and then claim the unused disks from the disk groups to be used for the vSAN Direct Configuration. After all of the disks have been claimed, the administrator can run the vSAN Direct Configuration wizard.

https://kb.vmware.com/s/article/1018029

1. Configuring vCenter Server to send alarms when virtual machines ...

https://kb.vmware.com/s/article/1018029

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

VMware vCenter Server 7.0 Update 1 Release Notes

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

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/branding/vmware-trademark-guidelines.pdf

VMWARE TRADEMARK GUIDE

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/branding/vmware-trademark-guidelines.pdf

An all-flash vSAN cluster contains a sufficient number of capacity devices and cache devices to support different RAID levels.

FTT=3(RAID-1 Mirroring) - This policy requires at least 4 capacity devices, where each object is mirrored across three copies of the object. This can be satisfied by the 4 nodes all-flash vSAN cluster.

FTT=1 (RAID-1 Mirroring) - This policy requires at least 2 capacity devices, where each object is mirrored across one copy of the object. This can be satisfied by the 4 nodes all-flash vSAN cluster.

FTT=2 (RAID-6 Erasure Coding) - This policy requires at least 6 capacity devices, where each object is striped across two sets of parity and data. This cannot be satisfied by the 4 nodes all-flash vSAN cluster.

FTT=1 (RAID-5 Erasure Coding) - vSAN does not support RAID-5 Erasure coding.

Reference: https://docs.vmware.com/en/VMwarevSphere/

7.0/com.vmware.vsphere.vsan.doc/GUID-2E99D1D1-1D9E-4C9A-9F17-0E1A7C846F5D.html