5V0-22.23 Exam Dumps : VMware vSAN Specialist v2

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

To implement HCI mesh between two clusters on vSAN that are located in geographically separate sites, the vSAN administrator should consider the following requirements:

• Either Layer 2 or Layer 3 communications can be used. HCI mesh supports both Layer 2 and Layer 3 network configurations, as long as the network latency and bandwidth requirements are met3
• The configuration must meet the same latency and bandwidth requirement as local vSAN. HCI mesh requires a network latency of less than or equal to 5 ms RTT between any two hosts in the participating clusters, and a network bandwidth of at least 10 Gbps for the vSAN network vmkernel port3 References: 3: VMware vSAN Specialist v2 Exam Preparation Guide, page 15

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