Important VMware 5V0-23.20 Exam Questions

Answer: B

Explanation:

A Supervisor Cluster namespace is a combination of resource allocations and permissions set within the Supervisor Cluster. When you create a Supervisor Namespace, you'll assign who has access to use it, and how many of the ESXi cluster's resources you can use (much like a resource pool).

When you enabled the Workload Management components, you created a special Kubernetes cluster called the ''Supervisor Cluster''. You can continue to deploy virtual machines in this cluster, and you can also deploy kubernetes pods as a ''pod vm'' which is basically a container with some special wrapping so they are better isolated, like a virtual machine is.

Answer: D

Explanation:

Certain Kubernetes workloads require persistent storage to store data permanently. To provision persistent storage for Kubernetes workloads, vSphere with Tanzu integrates with Cloud Native Storage (CNS), a vCenter Server component that manages persistent volumes.

Persistent storage is used by vSphere Pods, Tanzu Kubernetes clusters, and VMs. The following example illustrates how persistent storage is used by a vSphere Pod.

vSphere Pods use different types of storage depending on the objects that are stored. The types of storage are ephemeral virtual machine disks (VMDKs), persistent volume VMDKs, and containers image VMDKs:

* Storage policies for container image and ephemeral disks are defined at the cluster level.

* Storage policies for persistent volumes are defined at the namespace level.

* Networking for vSphere Pods uses the topology provided by NSX.

Answer: A

Explanation:

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

Answer: A

Explanation:

Acontextelement in a kubeconfig file is used to group access parameters under a convenient name. Each context has three parameters: cluster, namespace, and user. By default, thekubectlcommand-line tool uses parameters from thecurrent contextto communicate with the cluster.

To choose the current context:

kubectl config use-context ctx001

Answer: B

Explanation:

As a vSphere administrator, you can replace the certificate for the virtual IP address (VIP) to securely connect to the Supervisor Cluster API endpoint with a certificate signed by a CA that your hosts already trust. The certificate authenticates the Kubernetes control plane to DevOps engineers, both during login and subsequent interactions with the Supervisor Cluster.

Prerequisites

Verify that you have access to a CA that can sign CSRs. For DevOps engineers, the CA must be installed on their system as a trusted root.

Procedure

In the vSphere Client, navigate to the Supervisor Cluster.

ClickConfigurethen underNamespacesselectCertificates.

In theWorkload platform MTGpane, selectActions > Generate CSR.

Provide the details for the certificate.

Once the CSR is generated, clickCopy.

Sign the certificate with a CA.

From theWorkload platform MTGpane, selectActions > Replace Certificate.

Upload the signed certificate file and clickReplace Certificate.

Validate the certificate on the IP address of the Kubernetes control plane.