What are two ways a Namespace helps organize a Kubernetes cluster? (Choose two.)

Question

Options

• ADivides cluster resources across users
• BPools cluster resources between users
• CProvides a naming API
• DPrevents object name collisions
• EShares objects within a cluster

• A
  93% (41)
• B
  2% (1)
• C
  5% (2)

Explanation

Namespaces serve as virtual sub-clusters that let administrators carve up a single Kubernetes cluster for multiple teams or projects. Option A is correct because Namespaces are the scope at which ResourceQuota objects apply, allowing admins to allocate CPU, memory, and object counts to specific groups of users. Option E is correct because within a Namespace, resources like ConfigMaps and Services are accessible to all workloads sharing that Namespace, enabling teams to share common objects without exposing them cluster-wide.

B is wrong because Namespaces partition resources rather than pool them - each group gets its own bounded slice, not a shared pool. C is wrong because Namespaces don't provide a "naming API"; they are a scoping mechanism, not an API endpoint. D is a common trap: while it's true that the same name can appear in different Namespaces without conflict, the Kubernetes docs frame this as a side effect of scoping, not as one of the two primary organizational benefits the question is testing.

Memory tip: Think of a Namespace as a department in a company - the company (cluster) divides its budget across departments (A), and colleagues in the same department share their workspace and tools (E).

No community discussion yet for this question.