5V0-23-20 Sample Questions & Answers

The kubectl vsphere login command authenticates the user against vCenter SSO and retrieves a temporary token. It then adds a new context, cluster, and user entry to the user's local kubeconfig file (typically located at ~/.kube/config), allowing subsequent kubectl commands to be authenticated against the target cluster.

The standard Kubernetes method for requesting storage is to create a PersistentVolumeClaim (PVC). In a vSphere with Tanzu environment, vSphere storage policies are automatically exposed as StorageClasses. The developer creates a PVC manifest that specifies the size requirement (50 GiB) and sets the storageClassName field to 'fast-ssd'. This tells vSphere to provision a persistent volume on a datastore that complies with the 'fast-ssd' policy.

The Spherelet is a VMware-developed equivalent of a Kubelet that is integrated directly into the ESXi hypervisor. It allows the Supervisor Cluster's Kubernetes control plane to communicate with the ESXi host, register it as a node, and manage the lifecycle of vSphere Pods directly on the hypervisor, providing a secure and performant way to run containers.

Tanzu Kubernetes Clusters are managed declaratively via a Custom Resource Definition (CRD). The supported method to trigger a rolling upgrade is to edit the cluster's manifest, change the Kubernetes version specified in the distribution.version field to a supported, available version, and then re-apply the manifest. The TKG controllers will then orchestrate a rolling update of the control plane and worker nodes.

Permissions on the vSphere Namespace (like 'Edit' or 'View') do not automatically grant access to the integrated Harbor registry. Harbor maintains its own authentication. Users must perform a separate docker login command using their vCenter SSO username and password. This authenticates their client session specifically with the registry service.

Each vSphere Pod is encapsulated in its own lightweight virtual machine (CRX VM) with a dedicated kernel. This provides the same strong hardware-virtualization security and isolation boundary as a traditional VM.

From a developer's perspective, a vSphere Pod is a standard Kubernetes pod. It can be created, inspected, and managed using familiar kubectl commands like kubectl apply, kubectl get pods, and kubectl describe pod.

vSphere Pods fully support Kubernetes persistent storage concepts. They can use PersistentVolumeClaims to dynamically provision and mount VMDKs from vSphere datastores (vSAN, VMFS, NFS) for stateful applications.

This is the correct and intended method for storage governance in vSphere with Tanzu. The process is: 1) Tag the datastores (e.g., 'usage=finance'). 2) Create a vSphere Storage Policy that includes datastores with that tag. 3) In the vSphere Namespace configuration, add this storage policy. This ensures that any persistent volume claim created within that namespace will be satisfied only by datastores matching the policy.

The TanzuKubernetesCluster is the Custom Resource (CR) used to declaratively define and manage the lifecycle of a guest cluster. The manifest would specify details like the Kubernetes version, number of nodes, VM classes, and storage classes.

This is true. A vSphere Namespace is a unit of management and resource allocation within the Supervisor Cluster. It can be used to host vSphere Pods, Tanzu Kubernetes Clusters, and virtual machines (if VM Service is enabled), all within the same namespace boundary.

This is the correct approach. vSphere CNS (Cloud Native Storage) supports ReadWriteMany (RWX) access mode for persistent volumes provisioned on NFS datastores. The administrator creates the StorageClass pointing to the NFS-backed storage policy. The developers then create a PVC requesting this StorageClass with the ReadWriteMany access mode. This allows the resulting Persistent Volume to be mounted and used concurrently by multiple pods across different worker nodes in the TKC.