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

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.

This is because according to VMware documentation2, these are some of the components that are configured as part of the Supervisor Cluster control plane after enabling Workload Management on a VMware Cloud Foundation Workload Domain:

Tanzu Kubernetes Grid Service: This service enables you to create and manage Tanzu Kubernetes clusters on vSphere with Tanzu.

Kubernetes Grid Orchestrator: This component manages the lifecycle of Tanzu Kubernetes clusters on vSphere with Tanzu.

Spherelet: This component runs on each ESXi host and acts as a kubelet agent that communicates with the Supervisor Cluster control plane.

This is because according to VMware documentation3, developers can only access Kubernetes storage classes that are mapped from VM Storage Policies. They cannot modify or delete them.

This is because according to VMware documentation, this is the procedure for deleting a VMware Cloud Foundation Workload Domain and re-using its ESXi hosts:

Decommission all ESXi hosts in a cluster

Delete all clusters in a workload domain

Delete workload domain

Re-image ESXi hosts using SDDC Manager

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

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

This is because according to VMware documentation1, a VI workload domain consists of one or more vSphere clusters that run customer workloads.To enable workload management for a VI workload domain, you need to have an NSX-T edge cluster that provides north-south connectivity and load balancing for Kubernetes clusters2.The minimum requirement for creating an NSX-T edge cluster is two edge nodes34.The size of the edge nodes depends on the throughput and features required, but for high availability, large size is recommended5.

https://docs.vmware.com/en/VMware-Cloud-Foundation/4.5/vcf-getting-started/GUID-C68FD810-D270-43F2-AEBF-D522BA1F402B.html

This is because according to VMware documentation6, when integrating Microsoft Certificate Authority with SDDC Manager, you need to configure basic authentication on the Microsoft Certificate Authority Server and provide valid credentials when establishing a connection from SDDC Manager.

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.