VMware VMware Cloud Foundation Specialist (v2) 5V0-31.22 Exam Dumps: Updated Questions & Answers (November 2025)

This is because according to VMware documentation1, these are the steps to replace a failed host in a stretched cluster:

Run the compact cluster API to remove any stale data from vSAN.

Decommission the host to be removed using SDDC Manager UI or API.

Commission the replacement host to the same network pool as the removed host using SDDC Manager UI or API.

Add the newly commissioned host to the cluster using SDDC Manager UI or API.

Explanation: According to the VMware documentation, when replacing a failed host in a stretched cluster, the first step is to decommission the failed host. This should be followed by removing the host using cluster APIs, commissioning the new host with the correct network, and then adding the newly commissioned host to the cluster using cluster APIs.

 This is because when deploying a stretched cluster in a VMware Cloud Foundation environment, you must ensure that:

The vSAN network, the host overlay network and the vMotion network are stretched across both availability zones12. These networks enable data replication, communication and migration between hosts in different sites.

The host overlay network has DHCP enabled to provide IP addresses to hosts1. This simplifies the configuration and management of hosts in different sites.

Each vSAN stretched cluster has one witness host deployed in a separate location from both availability zones12. The witness host acts as a tie-breaker in case of a site failure or split-brain scenario.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-7B4CC729-20BD-4CC9-B855-B38F02F74D40.html

The option that should be enabled in the Planning and Preparation Workbook to address this issue is C. Identity and Access Management for VMware Cloud Foundation. According to the VMware Cloud Foundation documentation1, Identity and Access Management for VMware Cloud Foundation is a prerequisite for deploying Developer Ready Infrastructure using VMware Cloud Foundation. Identity and Access Management for VMware Cloud Foundation provides a centralized identity and access management service for the SDDC components and workloads, using Workspace ONE Access as the identity provider. If this option is not enabled in the Planning and Preparation Workbook, the Developer Ready Infrastructure using VMware Cloud Foundation option will be excluded and display an error.

A. Stretched Cluster for Management Domain is not a correct option, because it is not related to the deployment of Developer Ready Infrastructure using VMware Cloud Foundation. Stretched Cluster for Management Domain is an optional feature that allows you to stretch the management domain across two availability zones for high availability and disaster recovery purposes2

B. Clustered Workspace ONE Access is not a correct option, because it is not required for deploying Developer Ready Infrastructure using VMware Cloud Foundation. Clustered Workspace ONE Access is an optional feature that allows you to deploy a highly available Workspace ONE Access instance using vRealize Suite Lifecycle Manager. This feature is only available when Identity and Access Management for VMware Cloud Foundation is enabled3

D. Stretched Cluster for Workload Domain is not a correct option, because it is not related to the deployment of Developer Ready Infrastructure using VMware Cloud Foundation. Stretched Cluster for Workload Domain is an optional feature that allows you to stretch a VI workload domain across two availability zones for high availability and disaster recovery purposes4

References: 1: Deploying Application Virtual Networks in VMware Cloud Foundation 2: Deploying Stretched Clusters in VMware Cloud Foundation 3: VMware Cloud Foundation Design for vRealize Suite Lifecycle and Access Management 4: Deploying Stretched Clusters in VMware Cloud Foundation

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-77C40307-8466-4331-A510-9334C0F6CF32.html

This is because according to VMware documentation2, these are some of the prerequisites for enabling workload management for a VMware Cloud Foundation Management Workload Domain:

You must have a vSphere cluster with NSX-T networking configured.

You must have vSAN File Services enabled on your cluster.

You must have vSphere HA and DRS enabled in fully automated mode on your cluster.

The other options are incorrect because they are not required or supported for this deployment.

https://docs.vmware.com/en/VMware-Harbor-Registry/services/vmware-harbor-registry/GUID-index.html

This is because according to VMware documentation34, vSphere with Tanzu uses storage policies to integrate with shared datastores available in your environment, including VMFS, NFS, vSAN, or vVols datastores. The storage policies represent datastores and manage the storage placement of such objects as persistent volumes (PVs). Storage Policy Based Management (SPBM) is a framework that provides a single unified control plane across different types of datastores and enables administrators to define policies based on storage capabilities and requirements5.

The Cloud Native Storage for vSphere with Tanzu workflow is as follows: 1. A developer deploys a pod using the kubectl CLI. 2. The vSphere with Tanzu Cloud Native Storage-Container Storage Interface (CNS-CSI) reads this request from the control plane API server. 3. CNS-CSI informs the vCenter Server CNS that a disk with gold storage class is required. 4. CNS interfaces with SPBM for a suitable datastore that satisfies the gold storage class (storage policy). 5. SPBM decides on a suitable datastore and interfaces with DRS for a suitable ESXi host. 6. Hostd on the ESXi host creates a first class disk (VMDK) on the datastore. 7. Spherelet on the ESXi host takes the VMDK. 8. Spherelet mounts the VMDK to the vSphere pod. 9. Spherelet reports the mount as a successful event to the control plane API server.

This is because according to VMware documentation1, vSphere Native Key Provider (NKP) is a simple key management solution that does not support key replication across sites or clusters. It also does not support vSphere Virtual Machine encryption which requires a third-party KMS solution2. Therefore, to enable both vSAN data at rest encryption and vSphere Virtual Machine encryption in a multi-site VCF solution, you need to use a third-party KMS solution that allows for key replication across sites.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-54B9FBA2-FDB1-400B-A6AE-81BF3AC9DF97.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.3/vcf-lifecycle/GUID-8FA44ACE-8F04-47DA-845E-E0863094F7B0.html

The administrator can follow these steps to download the latest VCF software bundles:

Download the latest bundle transfer utility from myvmware.com. This is a tool that allows you to download the bundles from the VMware depot and upload them to the SDDC Manager appliance1

Use the utility to download the latest software bundles for the upgrade. You need to specify the version to which you are upgrading and provide your VMware Customer Connect credentials. The utility will verify the file size and checksum of the downloaded bundles1

Copy the bundles to SDDC manager using file sharing. You can use SCP or SFTP to transfer the bundles from your laptop to the SDDC Manager appliance. You need to upload the manifest file first, which is a metadata file that contains information about the VMware product versions included in the release Bill of Materials1

References: 1: Offline Bundle Download for VMware Cloud Foundation

This is because according to VMware documentation2, these are some of the features that are supported when implementing NSX Federation:

NAT operations: You can configure NAT rules for Tier-0 gateways across locations.

Load Balancer: You can configure load balancer services for Tier-0 gateways across locations.

The correct tool to use for replacing the vSAN Witness appliance for a VMware Cloud Foundation stretched vSAN cluster is the vSphere Client. According to the VMware Cloud Foundation documentation1, you can replace or change the vSAN witness host for a stretched cluster using the vSphere Client without affecting life cycle operations of SDDC Manager. You need to select a new host to use as the vSAN witness host, claim disks on the new witness host, and review the configuration.

vSphere Update Manager is not the correct tool, because it is used for patching and upgrading ESXi hosts, not for replacing vSAN witness hosts2

SDDC Manager is not the correct tool, because it does not have a workflow for replacing vSAN witness hosts. You need to use the vSphere Client for this task1

vSAN PowerCLI is not the correct tool, because it is a PowerShell module that provides cmdlets for managing and automating vSAN environments, not for replacing vSAN witness hosts3

References: 1: Change the vSAN Witness Host in a Stretched Cluster - VMware Docs 2: Upgrade ESXi Hosts Using vSphere Update Manager - VMware Docs 3: VMware PowerCLI User’s Guide - VMware Docs