5V0-22.23 Online Practice Questions and Answers

Correct Answer: B

Explanation: If the administrator did not explicitly assign a storage policy when provisioning a new VM on a vSAN datastore, the result is that the VM objects will be protected based on the vSAN Default Storage Policy configurations. The vSAN Default Storage Policy is assigned to all VM objects if no other vSAN policy is assigned when provisioning a VM. The default policy contains vSAN rule sets and a set of basic storage capabilities, such as Failures to tolerate set to 1, Number of disk stripes per object set to 1, and Thin provisioning. The other options are not correct. The VM provisioning will not fail, as vSAN requires that every VM has at least one storage policy. The vSphere Web Client will not choose the last vSAN Storage Policy used, as it will always apply the default policy if no other policy is selected. No data protection will not be applied to the VM objects, as they will have at least one replica based on the default policy. References: About the vSAN Default Storage Policy; Using vSAN Policies

Correct Answer: C

Explanation: To replace a failed cache drive in a vSAN OSA cluster, the vSAN administrator should remove the existing vSAN disk group and physically replace the device. Then check to verify that the ESXi host automatically detects the new device Afterwards manually recreate the Disk Group. This is because when a cache drive fails, it affects the entire disk group that contains it, and vSAN does not allow removing only the cache drive from a disk group. Therefore, the administrator must remove the whole disk group before replacing the cache drive, and then recreate it with the new cache drive and the existing capacity drives. The other options are not correct. Physically replacing the failed cache drive without removing the disk group first might cause errors or inconsistencies in vSAN configuration. vSAN will not automatically create a new disk group or allocate storage after replacing a cache drive, as these actions require manual intervention from the administrator. Rebalancing the cache layer is not necessary after replacing a cache drive, as vSAN will automatically distribute data across all devices in the disk group. References: Replace a Flash Caching Device on a Host; How to manually remove and recreate a vSAN disk group using esxcli

Correct Answer: D

Explanation: To reduce the amount of vSAN datastore capacity the virtual machines will consume, the vSAN administrator should change the FTT rule to "1 Failure - RAID-1 (Mirroring)", and select "Now" for Reapply to VMs. This action will reduce the number of replicas for each object from three to two, and thus free up some space on the vSAN datastore. The other options are not correct, as they will not reduce the capacity consumption. Modifying the FTT rule to "2 Failures RAID-5 (Erasure Coding)" will not work for a hybrid vSAN cluster, as erasure coding is only supported for all-flash clusters. Adding the "Flash read cache reservation" rule to the storage policy, and setting to 0% will not affect the capacity layer, as it only controls the amount of flash cache reserved for each object. Disabling Operations reserve and Host rebuild reserve and clicking "Apply" will not change the actual space used by the objects, as these reserves are only logicalsettings that affect how much free space is reported by vSAN. References: 1, page 9; , section 4.3

Correct Answer: BE

Explanation: An all-flash vSAN ESA cluster with four nodes can satisfy the storage policies that require FTT=2 (RAID-1 Mirroring) or FTT=2 (RAID-6 Erasure Coding). These policies mean that the cluster can tolerate two host failures while maintaining data availability and redundancy. RAID-1 Mirroring creates three replicas of each object across different hosts, while RAID-6 Erasure Coding splits each object into four data segments and two parity segments across different hosts. Both policies require at least four hosts in the cluster to meet the FTT=2 requirement. The other options are not correct. An all-flash vSAN ESA cluster with four nodes cannot satisfy the storage policies that require FTT=3 (RAID-1 Mirroring) or FTT=1 (RAID-5 Erasure Coding). These policies mean that the cluster can tolerate three or one host failure respectively, but they require more or less hosts than four to do so. RAID-1 Mirroring with FTT=3 requires at least six hosts in the cluster to create four replicas of each object, while RAID-5 Erasure Coding with FTT=1 requires at least three hosts in the cluster to split each object into two data segments and one parity segment. References: vSAN Express Storage Architecture; RAID Configurations, FTT, and Host Requirements

Correct Answer: C

Explanation: The Capacity Reserve feature in vSAN 8.0 OSA reduces the amount of capacity reserved for transient and rebuild operations by using a slack space threshold. This threshold is calculated based on the size of the largest component in the cluster and the number of failures to tolerate. If the used space on vSAN datastore exceeds the suggested slack space threshold, the feature will not operate properly and vSAN will revert to using the host rebuild reserve threshold. The other scenarios will not affect the Capacity Reserve feature. References: [VMware vSAN Specialist v2 EXAM 5V0-22.23], page 28

Correct Answer: AD

Explanation: To implement HCI mesh between two clusters on vSAN that are located in geographically separate sites, the vSAN administrator should consider the following requirements: Either Layer 2 or Layer 3 communications can be used. HCI mesh supports both Layer 2 and Layer 3 network configurations, as long as the network latency and bandwidth requirements are met3 The configuration must meet the same latency and bandwidth requirement as local vSAN. HCI mesh requires a network latency of less than or equal to 5 ms RTT between any two hosts in the participating clusters, and a network bandwidth of at least 10 Gbps for the vSAN network vmkernel port3 References: 3: VMware vSAN Specialist v2 Exam Preparation Guide, page 15

Correct Answer: A

Explanation: If vSAN is able to locate a full replica of 55% of the votes for the noncompliant objects of a virtual machine, vSAN will mark the virtual machine as compliant and automatically recover the noncompliant objects. This is because vSAN uses a quorum- based algorithm to determine object availability and compliance. An object is considered available if more than 50% of its votes are accessible, and compliant if it meets its assigned storage policy requirements. In this case, since 55% of the votes are accessible, vSAN can access a full replica of each object and restore its compliance state by rebuilding any missing or corrupted components. The other options are not correct. vSAN will not power off, mark as inaccessible, or mark as orphaned a virtual machine that has more than 50% of its votes accessible, as these actions would result in unnecessary downtime or data loss. References: Object States That Indicate Problems in vSAN; Accessibility of Virtual Machines Upon a Failure in vSAN

Correct Answer: AC

Explanation: To upgrade multiple vSAN Witness nodes with vLCM (single image management) that are used for vSAN Stretched and two-node Clusters, the administrator can upgrade two witness node types: appliance witness node and nested witness node. An appliance witness node is a virtual ESXi host that runs on a physical ESXi host and contains the witness components of VM objects stored in the vSAN cluster. A nested witness node is a virtual ESXi host that runs on another virtual ESXi host and contains the witness components of VM objects stored in the vSAN cluster. Both types of witness nodes can be managed by vLCM as independent nodes since vSphere 7.0 Update 3, as long as they are version

7.0 Update 2 or later. The other options are not correct. A shared witness node is a witness node that serves multiple vSAN clusters, which is not supported by vLCM. A dedicated witness node is a witness node that serves only one vSAN cluster, which is not a specific type of witness node. A physical witness node is aphysical ESXi host that contains the witness components of VM objects stored in the vSAN cluster, which cannot be upgraded by vLCM. References: vSphere Lifecycle Manager and the vSAN Witness Hosts; Shared Witness for 2-Node vSAN Deployments

Correct Answer: A

Explanation: Deploying the application on a new cluster with vSAN 8.0 ESA using a new hardware design is the correct answer because it will satisfy the customer's requirement for low latency. vSAN 8.0 ESA is a new architecture that uses a storage pool configuration where all disks are treated as capacity disks and use a new algorithm to distribute data across them. This improves the I/O flow, reduces the write amplification, and eliminates the cache tier bottleneck. Using a new hardware design with all-flash disks or NVMe disks will further enhance the performance and latency of the application, as these disks have faster read and write speeds than hybrid disks. Deploying the new applications on the existing cluster with a RAID-6 VM storage policy and an additionalstripe width of 4, deploying the application on a new cluster with vSAN 8.0 OSA using the existing hybrid configuration, and performing an in-place upgrade from vSAN 7.0 U2 OSA to vSAN

8.0 ESA are not valid or optimal solutions for this scenario. Deploying the new applications on the existing cluster with a RAID-6 VM storage policy and an additional stripe width of 4 will increase the resiliency and availability of the data, but it will also increase the network traffic, disk space consumption, and parity calculation overhead, which will negatively affect the latency and performance of the application. Deploying the application on a new cluster with vSAN 8.0 OSA using the existing hybrid configuration will not improve the latency significantly, as vSAN 8.0 OSA still uses the same disk group configuration as vSAN 7.0 U2 OSA, where one disk is designated as a cache disk and the rest are capacity disks. The cache disk can still become a bottleneck for high-performance applications, especially if it is not an SSD or NVMe disk. Performing an in-place upgrade from vSAN 7.0 U2 OSA to vSAN 8.0 ESA is not possible, as vSAN ESA requires a different hardware design than vSAN OSA. The existing disk groups need to be deleted and all disks need to be erased before switching to vSAN ESA. References: [VMware vSAN Specialist v2 Exam Preparation Guide], page 6 What's New in VMware vSAN 8.0

Correct Answer: CE

Explanation: Adding one more disk group per host with the same configuration and adding an ESXi host with identical device configuration are the two methods that the vSAN administrator should use to meet the goal of increasing capacity

and performance with the least amount of impact. Adding one more disk group per host will increase the raw storage capacity by 20% and also improve the performance by distributing the I/O load across more cache devices and disk groups.

Adding an ESXi host with identical device configuration will increase the raw storage capacity by 25% and also improve the performance by adding more compute and network resources to the cluster. Both methods can be done without

disrupting any ongoing operations or requiring any data evacuation or resynchronization. The other options are incorrect for the following reasons:

Replacing all capacity devices with a similar larger device is incorrect because it will not increase the performance and will have a significant impact on the cluster. Replacing the capacity devices requires deleting the disk groups, which will

erase all data on them and trigger a resynchronization of the affected objects. This can be disruptive and time-consuming, and also introduce additional network and disk traffic.

Replacing all cache devices with a larger device is incorrect because it will not increase the capacity and will have a significant impact on the cluster. Replacing the cache devices also requires deleting the disk groups, which will have the same drawbacks as replacing the capacity devices. Moreover, increasing the cache size may not improve the performance significantly, as vSAN OSA uses afixed cache ratio of 70% for write buffer and 30% for read cache, regardless of the cache device size. Adding faster cache devices is incorrect because it will not increase the capacity and will have a significant impact on the cluster. Adding faster cache devices also requires deleting the disk groups, which will have the same drawbacks as replacing the cache devices. Furthermore, adding faster cache devices may not improve the performance significantly, as vSAN OSA uses a fixed cache ratio of 70% for write buffer and 30% for read cache, regardless of the cache device speed. References: VMware vSAN Specialist v2 Exam Preparation Guide, page 10 Expanding a vSAN Cluster