5V0-31.22 VMware Cloud Foundation Specialist (v2) Questions and Answers

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.

after deploying the VMware Cloud Builder appliance, the next step a systems administrator should take when deploying VMware Cloud Foundation (VCF) is Option D: Upload the Deployment Parameter Workbook 1. After uploading and validating the deployment parameter workbook, you can perform bring-up of the management domain 1.

According to the VMware Cloud Foundation documentation, after deploying the VMware Cloud Builder appliance, the next step is to create a deployment parameter workbook that defines the parameters required for the deployment. This workbook can be created manually or generated using the VMware Cloud Foundation Deployment Parameter Workbook Generator tool. Oncethe workbook is created, it must be uploaded to the VMware Cloud Builder appliance before deploying the Management Domain [1].

Therefore, the correct sequence of steps would be:

• Deploy the VMware Cloud Builder appliance
• Create or generate the Deployment Parameter Workbook
• Upload the Deployment Parameter Workbook to the VMware Cloud Builder appliance
• Deploy the Management Domain using VMware Cloud Builder.

According to NSX Manager VM and Host Transport Node System Requirements23, an NSX-T management cluster formed using a medium-sized appliance can support up to 128 hypervisors. Since each VI Workload Domain has 36 hosts (18 x 2), and there are three VI Workload Domains, the total number of hosts is 108 (36 x 3), which is within the limit of a medium-sized NSX-T Manager cluster.

This is because vSphere Lifecycle Manager images can include firmware updates and third-party software components that can be applied to all hosts in a cluster12. These options are only available when using vSphere Lifecycle Manager images, not when using vSphere Lifecycle Manager baselines2.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere-lifecycle-manager.doc/GUID-9A112231-AD7C-4EF5-AB6A-A8DAA704D307.html

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.

A quote from reference [1] states that, "To add permissions to users or groups from vCenter Single Sign-On identity sources, the Tanzu Kubernetes cluster administrator can use either the vSphere Client or kubectl."

Another quote from reference [1] states that, "By default, a Tanzu Kubernetes cluster includes a set of predefined roles that provides granular permission control for Kubernetes objects. The predefined roles enable cluster groups to be created with specific permissions across the Kubernetes namespace hierarchy. Administrators can also create custom roles to provide more granular permission control that is specific to their organization's requirements."

References: [1] Tanzu Kubernetes Cluster or Supervisor Cluster[1]: Which do I choose? -https://blogs.vmware.com/virtualblocks/2022/06/23/tanzu-kubernetes-cluster-or-supervisor-cluster-which-do-i-choose/

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.