Free VMware 5V0-31.22 Practice Exam with Questions & Answers | Set: 2

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.

The vSphere Lifecycle Manager (LCM) function that is supported in VMware Cloud Foundation (VCF) is D. Install and update third-party software on ESXi hosts. According to the VMware Cloud Foundation documentation1, vSphere Lifecycle Manager images can include components that are created and published by third-party software vendors, such as drivers, patches, and solutions. These components can be added to the image to install and update the third-party software on the ESXi hosts in a cluster. VMware Cloud Foundation allows you to manage all images in a single place and re-use them for clusters across workload domains2

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.

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

This is because according to VMware documentation, these are some of the storage options that can be used for a new VI Workload Domain:

• vSAN principal storage with VMFS on FC supplemental storage: You can use vSAN as your primary storage platform and add VMFS on FC as an additional storage option.
• vSAN principal storage with NFS supplemental storage: You can use vSAN as your primary storage platform and add NFS as an additional storage option.

https://infohub.delltechnologies.com/l/dell-storage-with-vmware-cloud-foundation-1/principal-and-supplemental-storage-for-workload-domains-1

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

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/

To expand storage capacity in a vSAN cluster with one disk group, you can either add more drives to hosts in the cluster, which is commonly referred to as scaling up, or add capacity drives to existing disk groups 

Option B: Add an additional disk group - According to search result [1], adding additional drives to a host will increase both capacity and performance [1], and each disk group contains one flash cache device and one or multiple capacity devices for persistent storage [2]. Therefore, adding an additional disk group to each host would increase the storage capacity of the vSAN cluster.

Option D: Increase the number of capacity disks in the existing disk group - Search result [1] explains that vSAN clusters require capacity and cache devices to function, and each disk group can contain multiple capacity devices for persistent storage [2]. Thus, an additional way to expand storage capacity in the vSAN cluster would be to increase the number of capacity disks in the existing disk group.