5V0-31.22 VMware Cloud Foundation Specialist (v2) Free Practice Exam Questions (2025 Updated)

vSphere Single Sign-On (SSO) provides secure authentication and authorization services for VMware Cloud Foundation components, including vCenter Server and Platform Services Controller (PSC). In a consolidated architecture deployment of VMware Cloud Foundation, the vSphere SSO configuration is shared across all the workload domains.

To ensure that subsequent workload domains can use the same identity sources as an external identity source registered in a consolidated architecture, the administrator needs to replicate the vSphere SSO configuration. This can be achieved by configuring the same identity sources for vSphere SSO across all the workload domains.

Configuring IWA (Integrated Windows Authentication) or LDAPS (Lightweight Directory Access Protocol over SSL) as an identity source is a part of configuring the vSphere SSO configuration for identity sources.

Keeping the pre-configured defaults does not guarantee that the subsequent workload domains will use the same identity sources as the external identity source registered in a consolidated architecture.

References:

VMware Cloud Foundation Operations and Administration Guide: https://docs.vmware.com/en/VMware-Cloud-Foundation/index.html

VMware vSphere Security Guide: https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-security-guide.pdf

To ensure that any subsequent workload domains can be accessed using the same identity sources, it is necessary to replicate the vSphere SSO configuration across all the workload domains in a consolidated architecture deployment. This can be achieved by replicating the vSphere SSO configuration between the primary and additional SDDC Manager instances. This ensures that all the workload domains registered with the SDDC Manager will be able to consume resources and services from the same identity sources without any additional configuration in each individual workload domain.

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-1238AFD8-232C-4EFC-BD54-796CB9F8C45F.html Says "Persistent Volumes Claim"

According to VMware Cloud Foundation Planning and Preparation Workbook, a statement that is true regarding NSX Manager configuration in a VMware Cloud Foundation environment is:

The cluster virtual IP address (VIP) address must be used for API and GUI access to NSX Managers

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-management-domain-design/GUID-B0C6B2C7-E778-4CD1-BBAD-986A8AF5B930.html

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 according to VMware documentation3, these are some of the functions that will help the service provider with Tanzu resource management:

Object Limits: You can specify limits on objects such as pods, services, persistent volume claims, etc. for each namespace.

Resource Limits: You can specify limits on resources such as CPU and memory for each namespace.

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-2674DA5A-8DF7-4212-A4A9-88CD798DC303.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-1B9AAE1E-7C55-4A7A-A921-9F84F248AF68.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-6904A34A-1F67-4BBA-ACE8-12F039EC97E9.html

To provide identity and access management services to the cross-instance SDDC components, you create a global environment in vRealize Suite Lifecycle Manager in which you deploy a 3-node clustered Workspace ONE Access instance.

Workspace ONE Access is a service that provides identity and access management for the VMware Cloud Foundation environment. It enables single sign-on, multi-factor authentication, conditional access policies, and user lifecycle management for the SDDC components and workloads12

vRealize Suite Lifecycle Manager is a service that provides lifecycle management for the vRealize Suite products, such as vRealize Automation, vRealize Operations Manager, vRealize Log Insight, and Workspace ONE Access. It automates the deployment, configuration, patching, upgrading, and scaling of these products34

When you deploy a 3-node clustered Workspace ONE Access instance using vRealize Suite Lifecycle Manager, you are creating a highly available identity and access management service for your VMware Cloud Foundation environment.

References: 1: Workspace ONE Access Overview 2: VMware Cloud Foundation Design for vRealize Suite Lifecycle and Access Management 3: vRealize Suite Lifecycle Manager Overview 4: vRealize Suite Lifecycle Manager Installation, Upgrade, and Management Guide : Deploy Clustered Workspace ONE Access Instance Using vRealize Suite Lifecycle Manager

To create a VI workload domain with VMFS on FC storage, the hosts must be commissioned with VMFS on FC as the storage type and must be associated with a vMotion only or vMotion and NFS network pool. https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-4EBF9094-F732-4800-86FF-30C5D88B9758.html

To deploy a VI Workload Domain with VMFS on FC storage, the hosts must be associated with a network pool that contains the vMotion network information. This is because the vMotion network is required for adding a host to the SDDC Manager inventory and for migrating workloads between hosts.

A NFS only network pool, a network pool with vMotion and iSCSI, or an iSCSI only network pool are not valid options for deploying a VI Workload Domain with VMFS on FC storage. These network pools are used for different types of storage, such as NFS, vVols on iSCSI, or vSAN.

The references are:

Network Pool Management, section “Information Required for a Network Pool”

Hosts | VMware Cloud Foundation API Reference Guide APIs, section “The hosts, if intended to be used for VMFS on FC, domain must be associated with either a NFS enabled or vMotion enabled network pool.”

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-4EBF9094-F732-4800-86FF-30C5D88B9758.html#:~:text=You%20must%20have%20valid%20license%20keys%20for%20the%20following%20products%3A

The two licenses that must already be present in the SDDC Manager inventory for creating a VMFS on FC-based VI workload domain are:

VMware NSX-T Data Center

VMware vSphere

These licenses are required for the following products:

VMware NSX-T Data Center: This product provides the networking and security platform for the VI workload domain. It enables the creation of logical networks, routing, firewalling, load balancing, and other network services.

VMware vSphere: This product provides the virtualization layer for the VI workload domain. It includes the ESXi hypervisor and the vCenter Server appliance.

References:

Prerequisites for a Workload Domain, License Keys section

About VI Workload Domains, The workflow automatically section

https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-48A7A433-F3A0-4F77-99C4-B6280CD5D3F4.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.3/vcf-lifecycle/GUID-BB15EADE-DCD3-4D51-824E-124C9B364D20.html

This is because according to VMware documentation3, these are two use cases that would require the creation of multiple clusters in a workload domain. Different host CPU types may affect EVC compatibility and performance across clusters4. Bare-Metal vs. virtual workloads may have different storage and network requirements that need separate clusters5.

The SDDC Manager UI provides a single point of control for managing and monitoring your VMware Cloud Foundation instance and for provisioning workload domains. You use the navigation bar to move between the main areas of the user interface 1. The SDDC Manager UI provides an integrated view of the physical and virtual infrastructure and centralized access to manage the physical and logical resources 2.

The REST API can also be used to create a new VI workload domain using VMware Cloud Foundation. The VMware Cloud Foundation API Reference Guide provides information on available operations 3.