Free Practice Questions for VMware 5V0-31.22 Exam

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 change the password of the SDDC Manager super user account, the administrator should follow these steps:

Log in to the SDDC Manager UI as a user with the ADMIN role.

Go to Administration > Security > Password Management.

Select the SDDC Manager account from the component drop-down menu.

Click Rotate Now button.

This is the recommended method for changing the password of the SDDC Manager super user account, as documented in the VMware Cloud Foundation Administration Guide: https://docs.vmware.com/en/VMware-Cloud-Foundation/index.html

when upgrading ESXi software on Dell EMC PowerEdge servers using SDDC Manager Lifecycle Management (LCM), you must use a Dell EMC customized image that contains drivers for specific hardware components such as storage adapters.

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.virtualsan.doc/GUID-08911FD3-2462-4C1C-AE81-0D4DBC8F7990.html

According to the VMware Cloud Foundation documentation1, each workload domain in VCF has its own NSX Manager cluster that provides network services and security policies for the workloads in that domain. Therefore, to meet the customer requirements, the solution will have two workload domains: PROD and DEV, each with its own NSX Manager cluster. Additionally, the management domain will also have its own NSX Manager cluster that provides network services for the management components in VCF. However, this NSX Manager cluster is not counted as part of the solution, because it is deployed by default during the VCF bring-up process and cannot be used for workload domains2

A. 1 is not a correct answer, because it implies that there is only one workload domain in the solution, which does not meet the customer requirement of having separate PROD and DEV workload domains.

B. 4 is not a correct answer, because it implies that there are four workload domains in the solution, which exceeds the customer requirement of having two environments: PROD and DEV.

D. 3 is not a correct answer, because it implies that there are three workload domains in the solution, which does not match the customer requirement of having two environments: PROD and DEV.

References: 1: Workload Domains - VMware Docs 2: Deployment Model for NSX Manager for the Management Domain - VMware Docs

The two configuration steps that a VMware Cloud Foundation administrator must apply to achieve north/south connectivity while setting up an edge VM node for a workload domain from the SDDC Manager user interface are:

NSX VDS Uplinks

BGP Configuration

According to the web search results, the NSX VDS uplinks are required to connect the edge VM node to the physical network and provide north/south traffic for the overlay and public networks. The NSX VDS uplinks must be configured with named teaming policies that pin the traffic to specific VLANs and uplink ports1. The BGP configuration is required to enable dynamic routing between the NSX Tier-0 gateway and the physical routers. The BGP configuration must be done on both the NSX-T Data Center and the ToR switches2.

According to VMware Cloud Foundation Specialist (v2) Exam1, one of the objectives is to “Describe how to expand an existing NSX-T Edge cluster”. The exam guide also states that “SDDC Manager provides a single point of management for password rotation” and that “password rotation must be performed through SDDC Manager”.

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

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/com.vmware.vcf.vxrail.doc/GUID-E8D0A432-8573-4DF5-9330-A4FE15F74128.html

Prerequisites

A VI workload domain must be deployed.

An Workload Management ready NSX Edge cluster must be deployed on the workload domain.

You must select Workload Management on the Use Case page of the Add Edge Cluster wizard. See step 6 in Deploy an NSX Edge Cluster.

All hosts in the vSphere cluster for which you enable Workload Management must have a vSphere with Tanzu license.

Workload Management requires a vSphere cluster with a minimum of three ESXi hosts.

The following IP address subnets must be defined:

A non-routable subnet for pod networking, minimum of a /22 subnet.

A non-routable subnet for Service IP addresses, minimum of a /24 subnet

A routable subnet for ingress, minimum of a /27 subnet

A routable subnet for egress, minimum of a /27 subnet

This is because according to VMware documentation45, VCF supports two architecture models - standard and consolidated. The standard architecture model separates management workloads and user workloads into different domains, while the consolidated architecture model combines them into one domain. For a hybrid model that coexists with VMware on AWS cloud DR solution, the standard architecture model is recommended as it provides workload isolation and mobility across VCF instances6. The minimum requirement for creating a management domain or a VI workload domain is three hosts45.