Free VMware 2V0-16.25 Actual Exam Questions - Question 14 Discussion
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?
It’s A because Supervisor Namespaces let DevOps use Kubernetes tools to access vSphere resources securely with policies defining compute and storage limits. The other options don’t match this kind of scoped access control.
A - It sets up secure, policy-driven Kubernetes access within a Supervisor Namespace.
A. The Supervisor Namespace is designed to let admins expose vSphere resources securely through Kubernetes APIs, while also enabling policy enforcement like resource quotas and access control. It’s not just about giving access but controlling it within clear boundaries, which fits the question’s requirement for secure, policy-based access to compute and storage. The other options don’t really address both access and resource policies together like A does.
A imo, since Supervisor Namespaces let you control resource use and access via Kubernetes.
This isn’t about backups or replication, so B and C are out. D doesn’t fit either since giving admin access to the system namespace would be too broad and not secure. The key part is providing scoped, policy-based access with clear boundaries—which aligns with what Supervisor Namespaces do. They allow Kubernetes tooling to access vSphere resources while enforcing limits on compute and storage, making A the best fit here.
D imo, giving admin access to the vCenter Server system namespace is way too broad and doesn't really meet the "policy-based" or "clear boundaries" part. A fits better for scoped control.
A imo, since Supervisor Namespaces provide that controlled access environment for Kubernetes users, letting them work within set limits without full admin rights. D is too broad and risky for this scenario.
Maybe D could be a trap since giving admin access to the system namespace seems risky and doesn't really set boundaries on resource use. B and C don’t really relate to access or policy controls, just backup and replication. So, probably A still stands out because Supervisor Namespaces are designed exactly for scoped, policy-based access that isolates what DevOps teams can do with resources in vSphere. It’s the cleanest way to meet the request without opening up everything.
Totally agree with the focus on secure, scoped access. The Supervisor Namespace (A) is definitely the right pick because it isolates resources for Kubernetes users without giving full admin rights.
A makes the most sense here since Supervisor Namespaces let Kubernetes access vSphere resources securely with policies. The other options don’t really fit the use case.