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 ensure that a single rack failure is not going to affect the data availability, while minimizing the number of racks used, the administrator has to do the following:

• Distribute servers across at least three different racks. This is because vSAN supports up to three fault domains per cluster, which can be used to tolerate one or two failures. If only two racks are used, then only one failure can be tolerated4
• Configure three fault domains. A fault domain is a logical grouping of hosts that share a common failure point, such as a rack or a power supply. By configuring fault domains, vSAN can place replicas of an object across different fault domains, so that a failure within one fault domain does not result in data loss orunavailability4 References: 4: VMware vSAN Specialist v2 Exam Preparation Guide, page 13

To view the resynchronizing metrics, the vSAN administrator should open the Backend performance category. This category shows the performance of vSAN data components, such as read/write latency, IOPS, throughput, congestion, and resync traffic. The other categories are not relevant for this task. Disks shows the performance of physical disks in the cluster, Host Network shows the network performance of vSAN hosts, and Resvnc Latency shows the latency of resynchronization operations. References: 1, page 23; 3, section 6.4