5V0-22.23 Exam Dumps : VMware vSAN Specialist v2

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 deploy a new two-node vSAN cluster with a shared witness, the administrator must meet several requirements, one of which is that the ESXi hosts must have a minimum of 64 GBs of memory. This is because each host must have enough memory to run the VMs and also to support the vSAN metadata overhead. The other options are not requirements for a two-node vSAN cluster with a shared witness. The ESXi hosts do not need SSDs or NVMe for Virtual Flash File System, as they can use any supported storage devices for vSAN. The ESXi host’s controller cache and advanced features do not need to be disabled, as they can be used to improve performance and reliability. The ESXi host’s drives do not need to be configured in RAID 1, as vSAN uses its own software-defined RAID mechanism to provide Failures to Tolerate. References: Shared Witness for 2-Node vSAN Deployments; Two-Node Cluster Requirements

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