5V0-31.22 Sample Questions Answers

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

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-D3C55AA8-D4B9-49D4-A26F-7A713A141251.html Verify that there are at least three hosts available in the SDDC Manager inventory. For information on commissioning hosts.

The minimum number of hosts required for a new vSAN cluster is three, according to the VMware Cloud Foundation documentation1. This is because a vSAN cluster needs at least three hosts that contribute capacity to the cluster to form a quorum and tolerate failures. However, for best results and availability, VMware recommends adding at least four hosts to the cluster2

References: 1: Cluster Requirements for vSAN 2: Characteristics of a vSAN Cluster

https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-concepts-planning/GUID-3E4E6039-BD24-4C40-8575-5AA0EECBBBEC.html

Spherelet. An additional process called Spherelet is created on each host. It is a kubelet that is ported natively to ESXi and allows the ESXi host to become part of the Kubernetes cluster.

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-design/GUID-2156EC66-BBBB-4197-91AD-660315385D2E.html

erasure coding vSAN storage policy with the ability to tolerate two host failures requires at least six fault domains (hosts) in a cluster. Therefore, an 8-hosts cluster can meet this requirement for DEV/UAT workloads. Additionally, creating separate workload domains for DEV/UAT and DMZ can provide full management and network isolation between these two zones.

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.virtualsan.doc/GUID-AD408FA8-5898-4541-9F82-FE72E6CD6227.html

https://docs.vmware.com/en/VMware-Cloud-on-AWS/services/com.vmware.vsphere.vmc-aws-manage-data-center-vms.doc/GUID-EDBB551B-51B0-421B-9C44-6ECB66ED660B.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-getting-started/GUID-C68FD810-D270-43F2-AEBF-D522BA1F402B.html#:~:text=For%20each%20VI%20workload%20domain,vSphere%20maximum%20of%2064%20hosts. You create VI workload domains to run customer workloads. For each VI workload domain, you can choose the storage option - vSAN, NFS, vVols, or VMFS on FC.

VMware Cloud Foundation supports several storage types as principal and supplemental storage for VI workload domains. Principal storage is the initial shared storage type that is selected during the creation of a workload domain or cluster in SDDC Manager. Supplemental storage is the additional shared storage type that can be added after a cluster has been created using the vSphere Client.

The supported principal storage types for VI workload domains are:

• vSAN
• NFS v3
• vVols (FC, iSCSI, or NFS)

The supported supplemental storage types for VI workload domains are:

• vSAN
• NFS v3 or v4.1
• vVols (FC, iSCSI, or NFS)
• VMFS on FC
• iSCSI
• NVMeoF/TCP

Therefore, the only option that contains only supported storage types for VI workload domains is B. NFS v3, NFS v4.1, vSAN.

For more information, please refer to the following sources:

• Supported Storage Types for VMware Cloud Foundation
• Managing Storage in VMware Cloud Foundation
• VMWare Cloud Foundation Now Supports NVMeoF/TCP

According to About Identity and Access Management for VMware Cloud Foundation23, one of the prerequisites for deploying Identity and Access Management for VMware Cloud Foundation is to enable NSX Routing for Management Domain in SDDC Manager. This allows SDDC Manager to communicate with Active Directory servers across different networks.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-AFF133BC-F4B6-4753-815F-20D3D752D898.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.

According to VMware Cloud Foundation Architecture Poster, VCF with NSX-T Federation provides network high availability across workloads in two data center locations by synchronizing network configuration and state across sites. It also simplifies day 2 operations by providing centralized management and policy enforcement across sites. It also reduces RTO by enabling fast failover of network services between sites.

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

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

See 'Figure 25. Configure Cloud Builder validation' at https://infohub.delltechnologies.com/l/dell-poweredge-mx-deployment-with-vmware- cloud-foundation-deployment-guide/vmware-cloud-builder-configuration-validation https://my-cloudy-world.com/2021/05/28/vmware-cloud-builder-bringup-validation-tasks/

This is because according to VMware documentation1, the VMware Cloud Foundation Upgrade bundle upgrades the SDDC Manager appliance and Lifecycle Management, which are components of VMware Cloud Builder.

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-T-Data-Center/3.2/administration/GUID-F3A0A27E-88C0-4A64-8754-33CED93985D3.html

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.

This is because according to VMware documentation, this is the ideal design of VMware Cloud Foundation domains that the architect should recommend based on the Bill of Material for different vSAN ready nodes. This design can provide optimal performance and availability by using vSAN ready nodes with different disk group configurations for different domains based on their workload characteristics and requirements. The management domain can use vSAN ready nodes with one disk group per node to provide sufficient capacity and redundancy for management components such as vCenter Server and NSX Manager. The workload domains can use vSAN ready nodes with two disk groups per node to provide higher performance and throughput for VI workloads such as VMs and containers.

Based on VCF Domain Requirement and vSAN Cluster Practice, 4x Nodes will be a Managemnet Domain (Min. Requirement 4 Nodes) other 4x Nodes (with 1 Disk Group) and 8x Nodes (with 2 Disk Groups) seperate 2x Workload Domain because vSAN Best Pratices same cluster should be same numebr disk group and same number of Cache and Capacity (same size) each host .

If you want to replace an existing license with a newly added license, you must add and assign the new license in the management UI (for example, vSphere Client or NSX Manager) of the component whose license you are replacing. https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-FD3B1D45-AC70-45CC-A507-944D1A476EB9.html

According to the VMware documentation, each NSX-T Local Manager is associated with a vCenter Server, and each NSX-T Local Manager can manage up to three vCenters. In a VCF deployment with two environments (PROD and DEV) and two different hardware server types in PROD, there would be a total of three vCenter Servers. Therefore, a total of three NSX-T Local Managers would be provisioned to manage the three vCenter Servers.

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-D3C55AA8-D4B9-49D4-A26F-7A713A141251.html

This is because according to VMware documentation1, the VMware Imaging Appliance (VIA) is a tool that automates ESXi host imaging and configuration for VCF deployments. It supports custom ESXi images that include additional drivers or VIBs that are not part of the base ESXi image2. You can download ESXi software and VIBs from VMware or third-party sources and upload them to VIA for creating custom images3.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-admin/GUID-A56D8E59-A549-4624-BC61-4A92710F9FA1.html

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-lifecycle/GUID-3B41CF79-C721-4AFC-A263-0672143DF41E.html

This is because according to VMware documentation6, these are three initial shared storage types that are supported for deploying a new VI Workload Domain into an existing VCF environment. You can also add other supported storage types after deploying the VI Workload Domain.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-management-domain-design/GUID-11177D00-C8BE-4CEC-B997-659CC03B6D12.html

According to the VMware KB article Understand vMotion networking requirements (59232), a successful Long Distance vMotion requires a RTT (round-trip time) latency of 150 milliseconds or less, between hosts. This is the maximum accepted latency supported by vMotion across long distances1

An architect is decommissioning a host from a VI Workload Domain and wants to reuse it in a VMware Cloud Foundation environment.

Which statement accurately describes this process?

A. Use the decommission host workflow against a host with an unassigned state, and then run the commission host workflow.

B. Use the decommission host workflow against a host with an unassigned state, re-image the host, and then run the commission host workflow.

C. Use the decommission host workflow against a host with an assigned state, re-image the host, and then run the commission host workflow.

D. Use the decommission host workflow against a host with an assigned state, and then run the commission host workflow.

Answer: B

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-2C3E06BA-7B77-4F4B-958C-1BFCB3E9CBA7.html Removing hosts from the SDDC Manager inventory is called decommissioning. If you want to re-use a host in a different workload domain, you must decommission, re-image, and commission the host before adding it to the workload domain. The hosts that you want to decommission must not be assigned to a workload domain. If a host is assigned to a workload domain, you must remove it before you can decommission it. See Remove a Host from a vSphere Cluster in a Workload Domain.

Use the decommission host workflow against a host with an unassigned state, re-image the host, and then run the commission host workflow. According to the VMware Cloud Foundation documentation1, removing hosts from the SDDC Manager inventory is called decommissioning. If you want to re-use a host in a different workload domain, you must decommission, re-image, and commission the host before adding it to the workload domain. The hosts that you want to decommission must not be assigned to a workload domain. If a host is assigned to a workload domain, you must remove it before you can decommission it.

References: 1: Decommission Hosts - VMware Docs

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-177C23C4-ED81-4ADD-89A2-61654C18201B.html#:~:text=be%20in%20a-,DNS%2Dcompliant,-format .

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

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-2C4653EB-5654-45CB-B072-2C2E29CB6C89.html

• According to the VMware Cloud Foundation Specialist (v2) exam guide1, one of the objectives is to “Identify the supported storage types for VMware Cloud Foundation”.
• According to the VMware Cloud Foundation Design Guide2, the supported storage types for VI workload domains are vSAN, vVols, NFS v3, and VMFS on FC as principal storage, and vSAN, vVols, NFS v3 and v4.1, iSCSI, and NVMeoF/TCP as supplemental storage.
• Therefore, when deploying an additional cluster within a VI workload domain that has been created with vSAN as a principal storage, the administrator can choose any of the supported principal storage types for the new cluster.
• The only option that contains only valid principal storage types is D. vVols, vSAN, NFS v3, VMFS on FC.

References:

1: VMware Cloud Foundation Specialist (v2) Exam Guide 2: Supported Storage Types for VMware Cloud Foundation

According to the VMware Cloud Foundation documentation1, vVols supports FC, NFS, and iSCSI storage protocol types for principal storage. These are the protocols that are supported for the new commissioned hosts that will be used for the VI workload domain.

SCSI, FCoE, and SAS are not supported storage protocols for vVols in VMware Cloud Foundation.

References: 1: vVols Storage with VMware Cloud Foundation