VMware 5V0-31.22 Practice Test - Questions Answers, Page 10

https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-installation-configuration/GUID-544286A2-A403-4CA5-9C73-8EFF261545E7.html

After creating storage policies, a vSphere administrator can perform the following tasks: Assign the storage policies to the Supervisor. The storage policies configured on the Supervisor ensure that the control plane VMs, pod ephemeral disks, and container images are placed on the datastores that the policies represent. Assign the storage policies to the vSphere Namespace. Storage policies visible to the namespace determine which datastores the namespace can access and use for persistent volumes. The storage policies appear as matching Kubernetes storage classes in the namespace. They are also propagated to the Tanzu Kubernetes cluster on this namespace. DevOps engineers can use the storage classes in their persistent volume claim specifications.

The storage policies appear as matching Kubernetes storage classes in the namespace. They are also propagated to the Tanzu Kubernetes cluster on this namespace. DevOps engineers can use the storage classes in their persistent volume claim specifications https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-with-tanzu-installation-configuration/GUID-544286A2-A403-4CA5-9C73-8EFF261545E7.html

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

According to the VMware Cloud Foundation documentation1, an external SFTP server is recommended for storing backups of SDDC Manager and NSX-T Manager for the following reasons:

It provides better protection against failures because it decouples NSX-T backups from SDDC Manager.

It is a prerequisite for restoring SDDC Manager file-based backups.

Therefore, statements B and D are correct and should be shared with the customer.

1:Backup and Restore of VMware Cloud Foundation

https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-F8634D37-FA26-40DF-A135-62D0265DA4FA.html

By default, NSX Manager file-based backups are taken and stored on an SFTP server that is built into the SDDC Manager appliance. It is recommended that you configure an external SFTP server as a backup location for the following reasons: An external SFTP server is a prerequisite for restoring SDDC Manager file-based backups. Using an external SFTP server provides better protection against failures because it decouples NSX backups from SDDC Manager.

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

SDDC Manager is the tool that can be used to add a new vSphere cluster to an existing VI workload domain. SDDC Manager provides a unified interface for managing the lifecycle of the VMware Cloud Foundation components, including creating and expanding workload domains.

VMware Cloud Foundation Administration Guide, Expand a Workload Domain section

VMware Cloud Foundation Specialist (v2), Objective 4.1: Given a scenario, identify the steps to add a new vSphere cluster to an existing VI workload domain.

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.

Prerequisites for a Workload Domain, License Keys section

About VI Workload Domains, The workflow automatically section

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.

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.

According to the VMware Cloud Foundation documentation1, the default CPU and memory requirements for the VCF components in the management domain are as follows:

SDDC Manager: 2 vCPUs, 16 GB RAM

vCenter Server: 4 vCPUs, 16 GB RAM

NSX-T Manager: 4 vCPUs, 16 GB RAM

NSX-Edge Node: 2 vCPUs, 8 GB RAM

Therefore, only vCenter Server and NSX-T Manager have a default requirement of at least four vCPUs.