VMware 5V0-31.22 Exam Questions

https://docs.vmware.com/en/VMware-vSphere/7.0/vmware-vsphere-with-tanzu/GUID-EC79A6DE-477A-40C1-A90C-9DF96465CDA6.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.

https://docs.vmware.com/en/VMware-Validated-Design/6.2/sddc-architecture-and-design-for-a-vsphere-with-tanzu-workload-domain/GUID-8E524188-65F6-4FF2-B8A3-2D9B0C86FE2A.html

A NSX Tier-1 Gateway provides the functionality of a downlink connection to segments in a vSphere with Tanzu deployment.According to the VMware documentation1, a segment is a virtual layer-2 domain that can be either overlay-backed or VLAN-backed. A NSX Tier-1 Gateway connects to one or more segments and provides routing and security services for the workloads attached to those segments.A NSX Tier-1 Gateway also connects to a NSX Tier-0 Gateway, which provides uplink connectivity to external networks2

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

To create a VI workload domain with VMFS on FC storage, the hosts must be commissioned with VMFS on FC as the storage type and must be associated with a vMotion only or vMotion and NFS network pool. https://docs.vmware.com/en/VMware-Cloud-Foundation/5.0/vcf-admin/GUID-4EBF9094-F732-4800-86FF-30C5D88B9758.html

To deploy a VI Workload Domain with VMFS on FC storage, the hosts must be associated with a network pool that contains the vMotion network information. This is because the vMotion network is required for adding a host to the SDDC Manager inventory and for migrating workloads between hosts.

A NFS only network pool, a network pool with vMotion and iSCSI, or an iSCSI only network pool are not valid options for deploying a VI Workload Domain with VMFS on FC storage. These network pools are used for different types of storage, such as NFS, vVols on iSCSI, or vSAN.

The references are:

Network Pool Management, section ''Information Required for a Network Pool''

Hosts | VMware Cloud Foundation API Reference Guide APIs, section ''The hosts, if intended to be used for VMFS on FC, domain must be associated with either a NFS enabled or vMotion enabled network pool.''