VMware VMware vSAN Specialist v2 5V0-22.23 Exam Dumps: Updated Questions & Answers (September 2025)

To create an image using vSphere Lifecycle Manager, the mandatory requirement is to specify the ESXi version. An image is a collection of software components that define the desired state of hosts in a cluster. An image must include at least one ESXi version component, which determines the base hypervisor software for the hosts. Optionally, an image can also include other components, such as vendor add-ons, firmware and drivers add-ons, or custom components. The other options are not correct. A component is a generic term for any software element that can be included in an image, but it is not a specific type of component. A firmwareand drivers add-on is an optional component that provides firmware and drivers updates for hardware devices on the hosts. A vendor add-on is an optional component that provides vendor-specific software for the hosts. References: About Images; Create an Image

VMware Cloud on AWS is a service that delivers a fully managed VMware SDDC on AWS infrastructure. It uses vSAN as the mandatory, primary storage for the SDDC clusters. vSAN provides a high-performance, resilient, and secure shared storage solution for the VMware Cloud on AWS environment. The other options are not correct, as vSAN is not mandatory or primary for them. VMware Horizon, VMware Aria Automation, and Tanzu Kubernetes Grid Integrated Edition can use vSAN as an optional or secondary storage solution, but they can also use other types of storage. References: , section 1.1; , section 1.2

The reconfiguring state indicates that some components stored on the vSAN datastore are being moved or resized to meet a new storage policy requirement. This state can occur when the applied storage policy is modified, such as changing the number of failures to tolerate, stripe width, or object space reservation. The other situations will not cause components to enter this state. References: [VMware vSAN Specialist v2 EXAM 5V0-22.23], page 31

The correct answer is D, add additional capacity disks to each disk group. This is because adding capacity disks to existing disk groups is the fastest and easiest way to expand the capacity of the vSAN datastore without disrupting any ongoing operations or requiring additional hardware. The administrator can add up to five capacity disks per disk group in vSAN OSA, which means each host can have up to 25 capacity disks in total. The administrator should make sure that the new capacity disks are unformatted and not partitioned, so that vSAN can recognize and claim them. The administrator should also manually rebalance the cluster after adding the capacity disks to distribute the data evenly across the new devices. The other options are incorrect for the following reasons:

A, enable Deduplication and Compression on the cluster level, is incorrect because enabling Deduplication and Compression is not a recommended way to expand the capacity of the vSAN datastore. Deduplication and Compression is a space efficiency feature that reduces the logical space consumption of data by eliminating duplicate blocks and applying compression algorithms. However, enabling Deduplication and Compression requires a full data evacuation and resynchronization, which can be disruptive and time-consuming. Deduplication and Compression also introduces additional CPU and memory overhead, which can affect the performance of the cluster. Deduplication and Compression is only supported on all-flash clusters, not on hybrid clusters.

B, add additional capacity by adding a disk on one host and creating a storage pool, is incorrect because creating a storage pool is not supported in vSAN OSA. A storage pool is a new configuration introduced in vSAN 8 ESA, where all disks are treated as capacity disks and use a new algorithm to distribute data acrossthem. This configuration is not compatible with vSAN OSA, which uses a disk group configuration where one disk is designated as a cache disk and the rest are capacity disks. To use a storage pool, the administrator would need to migrate to vSAN 8 ESA on a new cluster with new hardware.

C, add additional capacity by adding a vSAN ReadyNode to the cluster, is incorrect because adding a vSAN ReadyNode to the cluster is not the fastest or easiest way to expand the capacity of the vSAN datastore. A vSAN ReadyNode is a preconfigured server that meets the hardware requirements for running vSAN. Adding a vSAN ReadyNode to the cluster would require additional hardware procurement, installation, and configuration. It would also increase the compute capacity of the cluster, which may not be necessary for the workload. Adding a vSAN ReadyNode would also trigger a resynchronization of data across the cluster, which can affect the performance and availability of the cluster. References:

VMware vSAN Specialist v2 Exam Preparation Guide, page 10

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

The three actions that the vSAN administrator should perform on the staging cluster prior to moving the vSAN nodes to the production cluster are:

Disable vSAN Services: This will stop any vSAN-related operations on the staging cluster, such as resynchronization, rebalancing, or repair. This will also prevent any new virtual machines from being created or migrated to the staging cluster.

Delete all Disk Groups: This will remove all disks from the vSAN cluster and erase all data on them. This will also free up the disks for use in the production cluster.

Delete all partitions from the capacity disks: This will ensure that there are no remnants of any previous vSAN configuration on the disks. This will also avoid any potential conflicts or errors when adding the disks to the production cluster.

Enabling File Services, marking the disks for partial reservation, and removing all capacity drives are not necessary or recommended actions for this scenario. Enabling File Services would add an unnecessary layer of complexity and overhead to the staging cluster. Marking the disks for partial reservation would reduce the available capacity for vSAN and potentially cause performance issues. Removing all capacity drives would leave only cache disks in the staging cluster, which would not be compatible with vSAN. References:

VMware vSAN Specialist v2 Exam Preparation Guide, page 10

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

A durability component is a temporary component that is created when a host or disk group is placed in maintenance mode with the Ensure data accessibility option, or when a host or disk group fails unexpectedly. A durability component improves the availability of data by maintaining the required number of failures to tolerate (FTT) until the original component is restored or rebuilt. A durability component also speeds up the resynchronization process by reducing the amount of data that needs to be copied. The other characteristics are not applicable to a durability component. References: VMware vSAN Specialist v2 EXAM 5V0-22.23, page 10, Objective 6.8; [Durability Components]

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

When a host in a vSAN stretched cluster goes offline, vSAN will use Adaptive Resync to recalculate the quorum on an object. Quorum is the minimum number of votes that an object needs to be available. For example, a RAID-1 object with two data components and one witness component needs two votes out of three to be available. If one data component goes offline, the object still has quorum and is available. However, if both data components go offline, the object loses quorum and is unavailable. Adaptive Resync will adjust the quorum requirement based on the availability of components and fault domains. For example, if one fault domain goes offline, Adaptive Resync will lower the quorum requirement to one vote out of two, so that the object can remain available with one data component and one witness component. References: VMware vSAN Specialist v2 EXAM 5V0-22.23, page 18