2V0-16-25 practice question 14 of 15

An administrator has enabled a Supervisor on a vSphere cluster. The DevOps team has requested access to vSphere resources such as virtual machines…

Full set: 60 questions
An administrator has enabled a Supervisor on a vSphere cluster. The DevOps team has requested access to vSphere resources such as virtual machines, storage, and networking using Kubernetes tooling. To meet this request, the administrator must provide secure, policy-based access that sets clear boundaries for compute and storage consumption. Which function is provided by Supervisor services to support this use case?
Answer options
A: Allow access to vSphere resources through Kubernetes in a configured Supervisor Namespace. Correct answer
B: Enable virtual machine backup using native Kubernetes ConfigMaps.
C: Enable vSphere Replication between Supervisor Namespaces.
D: Grant DevOps users administrator access to the vCenter Server system namespace.
Correct Answer:
A. Allow access to vSphere resources through Kubernetes in a configured Supervisor Namespace.
Explanation

A Supervisor Namespace is the fundamental unit of multi-tenancy and resource allocation in a vSphere with Tanzu environment. When an administrator creates a Supervisor Namespace, they assign specific permissions, storage policies, and resource quotas (for CPU, memory, and storage). This creates a secure, isolated environment for the DevOps team. The team can then use standard Kubernetes tools, such as kubectl, to interact with the Kubernetes API endpoint for that namespace to self-service deploy and manage vSphere resources like virtual machines (using the VM Service) and containerized workloads. This directly fulfills the requirement for secure, policy-based access with clear consumption boundaries.

Why Incorrect

B. Kubernetes ConfigMaps are used to store non-confidential configuration data in key-value pairs for pods; they are not a mechanism for backing up virtual machines.
C. vSphere Replication is a hypervisor-based disaster recovery solution for virtual machines, not a function for providing DevOps access to cluster resources via Kubernetes.
D. Granting administrator access to a system namespace would be a severe security risk, violating the principle of least privilege and contradicting the goal of providing bounded access.

References

1. VMware vSphere 8.0 Documentation

"vSphere with Tanzu Configuration and Management"

Chapter: Supervisor Namespaces.

Section: Supervisor Namespaces: "A Supervisor Namespace is a namespace that you create on a Supervisor. A Supervisor Namespace provides a namespace for DevOps engineers to run their workloads. When you create a Supervisor Namespace

you configure it for access by developers and set resource limits." This directly supports the concept of providing a bounded space for DevOps.

2. VMware vSphere 8.0 Documentation

"vSphere with Tanzu Configuration and Management"

Chapter: Managing Supervisor Namespaces.

Section: Configure Resource Quotas for a Supervisor Namespace: "You can edit the configuration of a Supervisor Namespace to set limits on the consumption of CPU

memory

and storage resources." This confirms the "clear boundaries for compute and storage consumption" requirement.

3. VMware vSphere 8.0 Documentation

"VM Service"

Chapter: Introduction to the VM Service.

Section: What is the VM Service?: "The VM service enables DevOps engineers and developers to deploy and manage virtual machines in a namespace by using Kubernetes APIs." This confirms that vSphere resources like VMs are accessible through Kubernetes tooling within the namespace.

Scroll to Top