A vSphere administrator is required to provide a developer with read/write permissions on a vSphere Namespace.

• A.It exposes a Kubernetes API for use by DevOps teams.
• B.It enables vSphere High Availability and Distributed Resource Scheduler.
• C.It aggregates hosts across vSphere clusters to form a Kubernetes cluster on vSphere.
• D.It is a Kubernetes cluster deployed by developers using a YAML specification file.

Comment: *

Name: *

Email: *

Verification: *

An organization is preparing to deploy vSphere with Tanzu and will be using the vSphere Networking stack.
How should the administrator allocate management network IP addresses for the Kubernetes Control Plane within the Supervisor Cluster?

• A.Five IP addresses are required, one for each of the Control Plane VMs. one for the floating IP address of the Control Plane VM, and one spare for performing rolling cluster upgrades
• B.Four IP addresses are required, one for each of the Control Plane VMs and one spare for performing rolling cluster upgrades
• C.Three IP addresses are required, one for each of the Control Plane VMs
• D.Six IP addresses are required, one for each of the Control Plane VMs, one for the floating IP address of the Control Plane VM. one for performing rolling cluster upgrades and one for the image Registry VM.

Comment: *

Name: *

Email: *

Verification: *

On which cluster can a Supervisor Namespace be created?

• A.A Tanzu Kubernetes Grid Integrated cluster
• B.A vSphere 7 cluster enabled with Workload Management
• C.A Tanzu Kubernetes cluster
• D.A vSphere 6.7 cluster enabled with Workload Management

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

Comment: *

Name: *

Email: *

Verification: *

An administrator working in a vSphere with Tanzu environment wants to ensure that all persistent volumes configured by developers within a namespace are placed on a defined subset of datastores The administrator has applied tags to the required datastores in the vSphere Client Which action should the administrator take next to meet the requirement?

• A.Create a storage policy containing the tagged datastores. and apply it to the vSphere Namespace.
• B.Create a storage class containing the tagged datastores. and apply it to the Supervisor Cluster
• C.Create a persistent volume claim containing the tagged datastores, and apply it to the vSphere Namespace.
• D.Create a storage Policy containing the tagged datastores. and apply it to the Supervisor Cluster.

Correct Answer: A

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

Comment: *

Name: *

Email: *

Verification: *

What is the proper way to delete a Persistent Volume Claim?

• A.By using the kubectl delete persistentvolumeclaim command
• B.By using the kubectl remove pvc command
• C.Through the SPBM policy engine using the vSphere Client
• D.By unmounting the volume from the VM and deleting it from the vSphere datastore

Correct Answer: A

Explanation
Diagram Description automatically generated

Also, kubectl delete pvc, which is much shorter.
DevOps engineers create persistent volume claims to request persistent storage resources. The request provisions a persistent volume object and a matching virtual disk. In the vSphere Client, the persistent volume claim manifests as an FCD virtual disk that can be monitored by vSphere administrators.
The claim is bound to the persistent volume. The workloads can use the claim to mount the persistent volumes and access storage.
When the DevOps engineers delete the claim, the corresponding persistent volume object and the provisioned virtual disk are also deleted.

Comment: *

Name: *

Email: *

Verification: *