5V0-22.23 Online Practice Questions and Answers

Correct Answer: D

Explanation: 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

Correct Answer: D

Explanation: The reason why the vSAN administrator cannot find any vSAN performance statistics on the cluster summary page is that the vSAN performance service is not enabled. The vSAN performance service is a feature that collects and analyzes performance metrics and displays them in graphical charts in vCenter. The vSAN performance service must be turned on manually for each vSAN cluster, as it is not enabled by default. The other options are not correct. The integration of vRealize Operations Manager with the vSAN cluster is not required to view vSAN performance statistics, as they are available in vCenter. The administrator's permissions on the cluster level do not affect the visibility of vSAN performance statistics, as they are accessible to any user who can view the cluster. vSAN performance statistics are not only available via CLI, as they can also be viewed in vCenter using the vSAN performance service. References: About the vSAN Performance Service; Enable or Disable the Performance Service

Correct Answer: A

Explanation: The maximum amount of capacity disks an administrator can have in disk groups on a single vSAN OSA host is 35. This is because a single host can have up to five disk groups, and each disk group can have up to seven capacity disks. Therefore, the maximum number of capacity disks per host is 5 x 7 = 35. The other options are not correct, as they are lower than the maximum number of capacity disks per host. References: Designing and Sizing vSAN Storage; [vSAN ReadyNode Hardware Guidance]

Correct Answer: CE

Explanation: Horizon and Dynamic Environment Manager are two end-user computing (EUC) solutions that can be implemented on vSAN storage to provide a virtual desktop infrastructure (VDI) solution and store applications running inside the VDI environment. Horizon is a platform that delivers virtual desktops and applications across a variety of devices and locations, while Dynamic Environment Manager is a tool that provides personalization and dynamic policy configuration across any virtual, physical, and cloud- based Windows desktop environment. The other solutions are not directly related to VDI or application storage on vSAN. References: VMware vSAN Specialist v2 EXAM 5V0-22.23, page 8, Objective 3.5; [Horizon]; [Dynamic Environment Manager]

Correct Answer: C

Explanation: The correct order to perform the update from vSAN version 7.0.2 to version 8.0 is to upgrade the vCenter Server first, then upgrade the ESXi hosts, and finally upgrade the vSAN on-disk format. This order follows the general vSphere upgrade order, which ensures compatibility and interoperability between different components. Upgrading the vCenter Server first allows it to manage and monitor the ESXi hosts and the vSAN cluster during the upgrade process. Upgrading the ESXi hosts second ensures that they have the latest software patches and drivers for vSAN. Upgrading the vSAN on-disk format last enables the new features and functionality of vSAN 8.0. The other options are not correct, as they do not follow the recommended upgrade order.

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: A

Explanation: To upgrade the complete vSAN cluster as a single task, including firmware and drivers for its hardware, the vSAN administrator should select Remediate All through vLCM to upgrade all hosts in the cluster. This option allows the administrator to apply the image created by vLCM to all hosts in the cluster in a single operation, without having to manually remediate each host individually. The other options are not correct, as they do not perform the upgrade of the vSAN cluster as a single task. Placing all hosts in the vSAN cluster into Maintenance Mode is not necessary, as vLCM will automatically place each host into Maintenance Mode before applying the image. Staging the upgrade of the vSAN cluster through vLCM is only a preparatory step that downloads the image components to each host, but does not apply them. Manually remediating one host at a time in the vSAN cluster is not efficient, as it requires more user intervention and time. References: vSphere Lifecycle Manager (vLCM) on HPE; Lifecycle Management with vLCM in vSAN 7 Update 1

Correct Answer: D

Explanation: When a host in a vSAN stretched cluster goes offline, the data components on the hosts will be marked as degraded. This means that the data is still available, but the redundancy level is reduced. vSAN will try to rebuild the missing components on another host in the same fault domain, if there is enough capacity and resources. If the host comes back online within 60 minutes, vSAN will resync the data and restore the redundancy level. If the host does not come back online within 60 minutes, vSAN will rebuild the missing components on another fault domain, if there is enough capacity and resources. This will incur additional network traffic across the witness link. References: VMware vSAN Specialist v2 EXAM 5V0-22.23, page 17

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: A

Explanation: The reason why there are objects in the pending category of the scheduled resyncing in the cluster monitor is that the delay timer has not expired. The delay timer is a configurable setting that determines how long vSAN waits before repairing a non-compliant object after placing a host in a failed state or maintenance mode. The default value is 60 minutes, but it can be changed in the vSAN Services configuration. The pending category displays the objects with the expired delay timer that cannot be resynchronized due to insufficient resources in the current cluster or the vSAN FTT policy set on the cluster not being met. The other options are not correct. These objects do not belong to virtual machines that are powered off, as vSAN resynchronizes all objects regardless of their power state. Object resynchronization does not need to be started manually, as vSAN initiates it automatically when the delay timer expires. There are not too many objects to be synchronized, as vSAN can handle multiple resynchronization tasks in parallel. References: Monitor the Resynchronization Tasks in the vSAN Cluster; About vSAN Cluster Resynchronization