5V0-22.23 Exam Dumps : VMware vSAN Specialist v2

In a vSAN stretched cluster configuration, both data sites are active sites, but one site must be designated as the preferred site and the other site as the secondary or nonpreferred site. This configuration helps to ensure that data remains on a given site in case of a network partition between the sites. If the network connection between the two active sites is lost, vSAN continues operation with the preferred site, unless it is resyncing or has another issue. The site that leads to maximum data availability is the one that remains in operation. The other options are not relevant to this scenario. References: Introduction to Stretched Clusters; vSAN Stretched Cluster Guide

To expand disk group #2 to have three capacity devices, the vSAN administrator should add the new capacity device to the disk group and vSAN will automatically rebalance. This action allows the administrator to increase the storage capacity of the disk group without disrupting any ongoing operations or evacuating any data. vSAN will automatically distribute data across all devices in the disk group to balance performance and utilization. The other options are not correct. Creating a new disk group with a single capacity device and then migrating the existing capacity devices is not necessary, as it would require more steps and resources than adding a device to an existing disk group. Putting the entire ESXi host or the disk group in maintenance mode and evacuating all data is not required, as it would cause downtime and data movement that could be avoided by adding a device to an existing disk group. References: Add Devices to the Disk Group; Expanding a vSAN Cluster

To protect a virtual machine against a disk or disk group failure, the storage policy must have a failure tolerance method (FTM) of RAID-1 or RAID-6 and a failure to tolerate (FTT) value of at least 1. RAID-1 mirrors the data across multiple disk groups, while RAID-6 uses erasure coding to stripe the data and parity information across multiple disk groups. RAID-5 is not suitable for this scenario, as it can only tolerate one disk failure per stripe. FTT 2 or 3 would require more disk groups than available in the cluster. Therefore, the correct options are C and E. References: 1, page 8; 2, section 3.1