5V0-22.23 VMware vSAN Specialist v2 Questions and Answers

If two hosts in a four-node vSAN cluster are down, the cluster might experience data loss because the default storage policy has a Primary level of failures to tolerate (PFTT) of 1, which means that vSAN can tolerate only one host failure. The Ensure accessibility maintenance mode option does not guarantee full data redundancy, but only ensures that all accessible VMs remain accessible. If another host fails while one host is in maintenance mode, some VMs might lose access to their data components and become unavailable or corrupted. References:  vSAN Maintenance Mode Options ;  vSAN Cluster Configuration Limits

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

The most likely cause for some components to be not in a fully healthy state is that one host is in maintenance mode with the ensure accessibility option. This option creates temporary durability components on other hosts to maintain the required number of failures to tolerate (FTT) until the original components are restored or rebuilt. These durability components are not considered fully healthy because they do not have full redundancy and might not be compliant with the storage policy. The other options do not explain why some components are not fully healthy, as they do not affect the FTT or the compliance state of the objects. References:  Durability Components ;  esxcli vsan debug object overview

To ensure that any virtual machines that are created are placed in the appropriate site, the administrator needs to create VM/Host groups for the two sites and create a storage policy that includes site affinity rules and apply to VMs. VM/Host groups allow the administrator to group virtual machines and hosts based on their location or preference. Site affinity rules specify which site a virtual machine should be placed on or prefer to run on. A single VM/Host group across both sites would not allow the administrator to control the placement of virtual machines.  Putting the VMs in a vSphere DRS group or in the correct VM group would not affect their site affinity. References:  1 , page 12;  2 , section 3.2

To create a Kerberos secured NFS v4.1 file share, the administrator needs to provide the following information during the configuration of the File Service:

Active Directory Domain: The domain name of the Active Directory server that provides Kerberos authentication service for the NFS server and clients. For example, example.com.

User Account: The user name of the Active Directory account that has permissions to join the NFS server to the domain and create service principal names (SPNs) for the NFS server. For example, administrator@example.com.

Password: The password of the Active Directory account that is used for authentication. For example, P@ssw0rd.

These information are required to enable Kerberos security for NFS 4.1 and allow the NFS server to obtain a Kerberos ticket from the Active Directory server.  The administrator also needs to specify the NFS share name, path, and access permissions 1  References:  1 : VMware vSphere Storage Guide, page 118

The correct answer is C, reduced vSphere licensing. This is because using a virtual witness appliance instead of a physical witness host can save on vSphere licensing costs, as the virtual witness appliance does not consume a vSphere license. The virtual witness appliance is a preconfigured virtual machine that runs ESXi and is distributed as an OVA file. It can be deployed on any ESXi host that has network connectivity to both data sites of the stretched cluster. The virtual witness appliance does not run any virtual machines other than itself and only hosts witness components of virtual machine objects. The other options are incorrect for the following reasons:

A, increased vSAN datastore capacity, is incorrect because using a virtual witness appliance does not affect the vSAN datastore capacity. The witness appliance does not store any customer data, only metadata, such as the size and UUID of vSAN object and components. The witness appliance also does not contribute any storage devices to the vSAN datastore.

B, shared metadata between separate clusters, is incorrect because using a virtual witness appliance does not enable sharing metadata between separate clusters. The witness appliance is dedicated to one stretched cluster and cannot serve as a witness for multiple clusters. The witness appliance maintains consistency between the two data sites of the stretched cluster by hosting witness components that act as tie-breakers in case of a site failure or network partition.

D, additional compute capacity for running VMs, is incorrect because using a virtual witness appliance does not provide additional compute capacity for running VMs. The witness appliance does not run any VMs other than itself and does not participate in any compute operations of the stretched cluster. The witness appliance only hosts witness components that consume minimal CPU and memory resources. References:

VMware vSAN Specialist v2 Exam Preparation Guide , page 11

Deploying a vSAN Witness Appliance

To enable vSAN ESA, two requirements that need to be met are: vSAN Standard license or higher, and vSAN ReadyNodes configuration. vSAN Standard license or higher is required to use vSAN ESA, as it is a feature that is only available in vSAN 8.0 or later versions. vSAN ESA is an optional, alternative architecture to vSAN OSA that is designed to process and store data with higher efficiency, scalability, and performance. vSAN ReadyNodes configuration is required to use vSAN ESA, as it is a hardware configuration that is pre-configured, tested, and certified for VMware Hyper-Converged Infrastructure Software. Each vSAN ReadyNode is optimally configured for vSAN ESA with the required amount of CPU, memory, network, and storage NVMe devices. The other options are not correct. vSAN Build Your Own configuration is not supported for vSAN ESA, as it might not meet the hardware requirements or compatibility for vSAN ESA. vSAN Witness Appliance is not required to use vSAN ESA, as it is only needed for stretched cluster or two-node cluster configurations. References:  vSAN Express Storage Architecture ;  vSAN ReadyNode Hardware Guidance

The correct answer is A, the disk group must be deleted on each physical host in the vSAN OSA cluster to use the NVMe device. This is because vSAN OSA uses a disk group configuration where one disk is designated as a cache disk and the rest are capacity disks. To replace the cache disk with a different type or size, the disk group must be deleted first, which will erase all data on the disks and trigger a resynchronization of the affected objects. The administrator should put the host in maintenance mode and choose the option to evacuate all data before deleting the disk group. After replacing the cache disk with the NVMe device, the administrator should recreate the disk group and exit maintenance mode. The other options are incorrect for the following reasons:

B, the disk group does not need to be removed before adding new cache, is incorrect because adding a new cache disk to an existing disk group is not supported in vSAN OSA. The cache disk can only be replaced by deleting and recreating the disk group.

C, the host must be removed from vSAN OSA cluster before changing cache devices, is incorrect because removing the host from the cluster is not necessary and will cause more disruption and data loss than putting the host in maintenance mode. Removing the host will also delete its disk groups and require re-adding them after rejoining the cluster.

D, the cache disk drives must have a larger capacity, is incorrect because there is no requirement for the cache disk to have a larger capacity than the existing one. The cache disk size should be determined by the workload characteristics and performance requirements, not by the expansion process. References:

VMware vSAN Specialist v2 Exam Preparation Guide , page 10

To build a vSAN ESA cluster with RAID-5/FTT 1 adaptive storage policy, the absolute minimum number of hosts that need to be part of that vSAN ESA cluster is 3. This is because the vSAN ESA supports a new RAID-5 erasure coding scheme in a 2+1 configuration, which writes the data in a VM as a stripe consisting of 2 data bits and 1 parity bit, across a minimum of 3 hosts. This scheme can tolerate a single host failure (FTT=1) while consuming 1.5x the capacity of the primary data.  This scheme is suitable for smaller vSAN clusters that want to reduce capacity usage without compromising performance 1 2  References:  1 : VMware vSAN Specialist v2 Exam Preparation Guide, page 15  2 : Adaptive RAID-5 Erasure Coding with the Express Storage Architecture in vSAN 8  3

This is the sequence of steps recommended by VMware for manually restarting the vSAN cluster after a planned power outage. The steps are as follows:

Enable cluster member updates from vCenter Server only on one ESXi host. This will allow the host to receive the latest cluster membership information from vCenter Server and avoid any conflicts or inconsistencies with other hosts. The command to enable cluster member updates is  esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListUpdates .

Run the python reboot helper script only on one ESXi host to recover the cluster. This will prepare the cluster for a manual restart by partitioning the cluster and ensuring that all hosts have consistent metadata. The command to run the python reboot helper script is  python /usr/lib/vmware/vsan/bin/reboot_helper.py prepare .

Exit all hosts from maintenance mode. This will allow the hosts to resume normal operations and join the vSAN cluster. The command to exit maintenance mode is  esxcli system maintenanceMode set -e false .

The other options are incorrect for the following reasons:

B, exit all hosts from maintenance mode, run the python reboot helper script only on one ESXi host to recover the cluster, and enable cluster member updates from vCenter Server on all ESXi hosts, is incorrect because exiting all hosts from maintenance mode before running the python reboot helper script can cause data inconsistency or corruption, as the hosts may not have the latest metadata or cluster membership information. Enabling cluster member updates from vCenter Server on all ESXi hosts is also unnecessary and can cause conflicts or inconsistencies with other hosts.

C, exit all hosts from maintenance mode, enable cluster member updates from vCenter Server only on one ESXi host, and run the python reboot helper script only on one ESXi host to recover the cluster, is incorrect because exiting all hosts from maintenance mode before running the python reboot helper script can cause data inconsistency or corruption, as the hosts may not have the latest metadata or cluster membership information.

D, enable cluster member updates from vCenter Server on all ESXi hosts, run the python reboot helper script on all ESXi hosts to recover the cluster, and exit all hosts from maintenance mode, is incorrect because enabling cluster member updates from vCenter Server on all ESXi hosts is unnecessary and can cause conflicts or inconsistencies with other hosts. Running the python reboot helper script on all ESXi hosts concurrently can also cause a race condition that can result in unexpected outcomes.

References:

Manually Shut Down and Restart the vSAN Cluster

Restart the vSAN Cluster

When adding a host to a vSAN cluster, it is recommended to create uniformly-configured hosts and reference the VMware Compatibility Guide. These actions will ensure that the host meets the hardware and software requirements for vSAN, and that it can work seamlessly with the existing hosts in the cluster. Uniformly-configured hosts have the same number and type of disk groups, cache devices, capacity devices, network adapters, and drivers. The VMware Compatibility Guide provides a list of certified components and firmware versions that are compatible with vSAN. The other options are not recommended, as they can cause disruption or degradation of the vSAN cluster services.  Disabling vSAN performance service, vSphere Cluster Services, or vSphere High Availability (HA) can affect the monitoring, availability, and load balancing of the cluster.

The Capacity Reserve feature in vSAN 8.0 OSA reduces the amount of capacity reserved for transient and rebuild operations by using a slack space threshold. This threshold is calculated based on the size of the largest component in the cluster and the number of failures to tolerate. If the used space on vSAN datastore exceeds the suggested slack space threshold, the feature will not operate properly and vSAN will revert to using the host rebuild reserve threshold. The other scenarios will not affect the Capacity Reserve feature. References: [VMware vSAN Specialist v2 EXAM 5V0-22.23], page 28

When adding a disk to a host that was previously used in a decommissioned vSAN cluster, the disk may still have some vSAN metadata partitions that prevent it from being recognized by disk management. To resolve this issue, the disk partitions need to be deleted using either ESXCLI or partedUtil commands. This will erase all data on the disk and make it available for use in disk management. References:  VMware vSAN Specialist v2 EXAM 5V0-22.23 , page 21

The correct answer is B, check VMKNICs, uplinks, physical switches, and associated settings. This is because the VMware Skyline Health: Network Latency Check reports the network latency between vSAN hosts and displays the network latency in real time. Failure indicates that the network latency is above the normal threshold, which can affect the performance and availability of vSAN. The network latency can be caused by various factors, such as misconfiguration, congestion, or errors in the network components. The vSAN administrator should check the VMKNICs, uplinks, physical switches, and associated settings for any issues and resolve them accordingly. The vSAN administrator can also use tools such as vmkping or esxtop to test the network connectivity and performance between hosts. The other options are incorrect for the following reasons:

A, immediately reboot the non-compliant hosts, is incorrect because rebooting the non-compliant hosts is not a recommended action and can cause more disruption and data loss than resolving the network issue. Rebooting the hosts will also trigger a resynchronization of data across the cluster, which can affect the performance and availability of vSAN.

C, rerun the VMware Skyline Health: vSAN Cluster Partition report, is incorrect because rerunning the VMware Skyline Health: vSAN Cluster Partition report will not help to resolve the network latency issue. The vSAN Cluster Partition report checks if there are any network partitions in the cluster that prevent communication between hosts. The network partition can be caused by network latency, but it is not the same as network latency. The vSAN administrator should first fix the network latency issue before checking for any network partitions .

D, place the non-compliant hosts into an isolated network partition, is incorrect because placing the non-compliant hosts into an isolated network partition will not help to resolve the network latency issue. It will also cause more problems for vSAN, such as data inconsistency, reduced redundancy, and degraded performance. The vSAN administrator should avoid creating any network partitions in the cluster and ensure that all hosts can communicate with each other. References:

VMware vSAN Specialist v2 Exam Preparation Guide , page 9

Network Health - Network Latency Check (2149511)

vSAN will use a 4+1 RAID-5 data placement scheme with parity will be used is the correct answer because vSAN 8 ESA uses adaptive RAID-5 erasure coding that depends on the number of hosts in the cluster. If the cluster has 6 or more hosts, vSAN will use a 4+1 RAID-5 scheme, where the data is written as a stripe of 4 data bits and 1 parity bit across 5 hosts. This provides a failure tolerance of 1 (FTT=1) and a space efficiency of 1.25x. If the cluster has less than 6 hosts (3 to 5), vSAN will use a 2+1 RAID-5 scheme, where the data is written as a stripe of 2 data bits and 1 parity bit across 3 hosts. This also provides a failure tolerance of 1 (FTT=1) but a space efficiency of 1.5x. In this case, the cluster has 5 hosts, so vSAN will use the 4+1 RAID-5 scheme.

The other options are incorrect for the following reasons:

A, vSAN will use a 2+1 RAID-5 data placement scheme with parity will be used, is incorrect because vSAN will only use this scheme if the cluster has less than 6 hosts but more than 2 hosts. In this case, the cluster has 5 hosts, so vSAN will use the 4+1 RAID-5 scheme.

B, RAID 5 will provide an FTT=2 level of protection in this case, is incorrect because RAID 5 can only provide an FTT=1 level of protection, regardless of the number of hosts or the data placement scheme. To achieve an FTT=2 level of protection, vSAN would need to use RAID 6 erasure coding, which requires at least 6 hosts in the cluster.

D, vSAN will spread the components across all of the disk groups, is incorrect because vSAN will not necessarily spread the components across all of the disk groups in the cluster. vSAN will only spread the components across as many disk groups as needed to meet the storage policy requirements and to balance the load and capacity. In this case, vSAN will only need to spread the components across 5 disk groups for each stripe of RAID-5 data. References:

VMware vSAN Specialist v2 Exam Preparation Guide , page 11

Adaptive RAID-5 Erasure Coding with the Express Storage Architecture in vSAN 8

Using vSAN ESA and the new Storage pool configuration where all disks contribute to capacity is the correct answer because it allows the organization to take advantage of the new features in vSAN 8.0, such as improved I/O flow, better resiliency, and more efficient disk usage. With vSAN ESA, there is no need to create disk groups or designate cache disks, as all disks are treated as capacity disks and use a new algorithm to distribute data across them. This also simplifies the disk management and reduces the overhead of cache management. References:

VMware vSAN Specialist v2 Exam Preparation Guide , page 6

What’s New in VMware vSAN 8.0

The Skyline Health interval validates online if there are new Health Checks available for vSAN every 24 hours. This means that vSAN checks for new health checks from VMware Analytics Cloud once a day and updates the vSAN Health Service accordingly. The other options are not correct, as they do not match the actual frequency of the online validation. References:  About the vSAN Skyline Health

To satisfy the customer’s needs for high-performance, low-latency applications at edge locations, the best deployment option is to use a new three-node vSAN 8.0 All-Flash Cluster with OSA in each edge location and configure each application VM with a RAID-1 VM storage policy. This option will provide the following benefits:

All-flash clusters offer the highest performance and lowest latency for vSAN, as they use flash devices for both cache and capacity tiers. Flash devices have faster read and write operations than magnetic disks, and they also support advanced features such as deduplication, compression, and encryption.

OSA stands for One Socket Architecture, which means that each host has only one CPU socket with multiple cores. This reduces the licensing cost and complexity of vSphere and vSAN, as well as the power consumption and cooling requirements of the hosts. OSA also improves the performance of vSAN by eliminating the NUMA effect, which is the latency caused by accessing memory or devices across different CPU sockets.

RAID-1 is a mirroring technique that creates two copies of each data component and places them on different hosts. This provides high availability and fault tolerance for the application VMs, as they can survive the failure of one host or disk. RAID-1 also offers better performance than RAID-5 or RAID-6, as it does not incur any parity overhead or additional write operations.

The other options are not optimal for the customer’s needs, as they either sacrifice performance or capacity. Option A uses RAID-5, which is an erasure coding technique that splits each data component into three data segments and one parity segment, and distributes them across four hosts. This reduces the capacity consumption by 25%, but it also increases the write latency and network traffic, as each write operation requires four hosts to participate. Option C uses ESA, which stands for Enterprise Storage Architecture, which means that each host has two CPU sockets with multiple cores. This increases the licensing cost and complexity of vSphere and vSAN, as well as the power consumption and cooling requirements of the hosts. ESA also introduces the NUMA effect, which can degrade the performance of vSAN by adding latency to access memory or devices across different CPU sockets. Option D uses RAID-5 with ESA, which combines the disadvantages of both options A and C.