VMware VMware vSphere with Tanzu Specialist 5V0-23.20 Exam Dumps: Updated Questions & Answers (October 2025)

A dedicated IP range for virtual IPs. The HAProxy VM must be the only owner of this virtual IP range. The range must not overlap with any IP range assigned to any Workload Network owned by any Supervisor Cluster.

You can deploy an application on a namespace on a Supervisor Cluster. Once the application is deployed, the respective number of vSphere Pods are created on the Supervisor Cluster within the namespace.

Common kubectl commands include the apply, get, describe, and delete commands:

• The kubectl apply command applies the contents of a YAML file. Typically, this command is used to create a pod or deployment: —

kubectl apply -f /path/to/my.yaml

• The kubectl get command returns basic information about an object: — kubectl get pod

Create an example pod spec with the details about the private registry.

apiVersion: v1

kind: Pod

metadata:

name:

namespace:

spec:

containers:

- name: private-reg-container

image: //:

imagePullSecrets:

- name:

Replace  with the name of the pod workload.

Replace  with the Kubernetes namespace in the cluster where the pod will be created. This must be the same Kubernetes namespace where the Registry Service image pull secret is stored in the Tanzu Kubernetes cluster (such as the default namespace).

Replace  with the IP address for the embedded Harbor Registry instance running on the Supervisor Cluster.

Replace with the vSphere Namespace where the target Tanzu Kubernetes is provisioned.

Replace  with an image name of your choice.

Replace  with an appropriate version of the image, such as "latest".

Replace  with the name of the Registry Service image pull secret that you created previously.

NSX Container Plugin (NCP) runs as a pod on the control plane VMs. It listens for requests for network objects to the API server and interfaces with the NSX Manager to create, update, or delete those objects:

• A request to create a namespace results in a new NSX segment.

• A request to deploy a pod results in a segment port request and IP assignment.

• A request to create a service results in a new virtual server.

• A request to create a network policy results in a new distributed firewall rule.

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 of the need for a disk with storage class Gold.

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 created 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.

Graphical user interface Description automatically generated

The vSphere administrator defines and assigns VM storage policies to a namespace:

• VM storage policies are translated into Kubernetes storage classes.

• Developers can access all assigned VM storage policies in the form of storage classes.

• Developers cannot manage storage classes.

Storage class names are created in the following way:

• Spaces in VM Storage Policy names are replaced with hyphens (-).

• Special characters are replaced with a digit. A VM Storage Policy called My Gold Policy $ is called my-gold-policy-0 as a storage class.

https://docs.vmware.com/en/VMware-vSphere/7.0/vsphere-esxi-vcenter-server-702-vsphere-with-tanzu-guide.pdf

Configuring Workload Networks You configure one or more workload networks and their respective IP address ranges.

Each workload network is assigned a vSphere Distributed Switch port group and uses a defined IP range to allocate IP addresses to workloads (VMware Tanzu Kubernetes clusters).