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…

Question

Options

• AAllow access to vSphere resources through Kubernetes in a configured Supervisor Namespace.
• BEnable virtual machine backup using native Kubernetes ConfigMaps.
• CEnable vSphere Replication between Supervisor Namespaces.
• DGrant DevOps users administrator access to the vCenter Server system namespace.

• A
  84% (16)
• B
  11% (2)
• C
  5% (1)

Explanation

Option A is correct because Supervisor Namespaces are the core mechanism that allows DevOps teams to interact with vSphere resources (VMs, storage, networking) using native Kubernetes tools - each namespace acts as a secure boundary with configurable resource quotas (CPU, memory, storage limits) and role-based access control, satisfying exactly the policy-based, bounded-access requirement described.

B is wrong because VM backup is not a function of Supervisor Namespaces, and ConfigMaps are Kubernetes objects for storing configuration data - they have no native backup capability for virtual machines. C is wrong because vSphere Replication is a disaster recovery feature that replicates VMs between sites, not between Supervisor Namespaces, and is unrelated to DevOps tooling access. D is wrong because granting DevOps users administrator access to the system namespace would violate the requirement for secure, bounded access - it would give unrestricted control over the entire vSphere infrastructure.

Memory tip: Think of a Supervisor Namespace as a "fenced yard" - DevOps teams get their own Kubernetes-native playground inside vSphere, with a fence (resource quotas + policies) that prevents them from consuming more than allowed or reaching into other teams' yards.

No community discussion yet for this question.