Which statement about Kubernetes Namespaces is true?

Which statement about Kubernetes Namespaces is true?

• A. Namespaces isolate resources and limit privileges.
• B. Namespaces are a single global namespace
• C. Namespaces are used only for DNS domains
• D. Namespaces have no impact on RBAC

Answer: (A)

Namespaces provide a way to partition a Kubernetes cluster into separate, isolated environments. They scope all namespaced objects (like pods, services, and deployments) so that what you create in one namespace stays contained there. This scoping also controls access: you can grant users permissions that apply only within a specific namespace, so their privileges don’t automatically extend to other parts of the cluster. That’s why the statement about isolating resources and limiting privileges is the best fit. By design, a Role and its associated RoleBinding grant access only inside a particular namespace, so users or teams can operate independently in their own spaces without affecting others. If you need cross-namespace access, you’d typically use cluster-wide roles or bindings, but the default and common usage is namespace-scoped. The other ideas don’t align with how namespaces work: there isn’t just one global namespace, as you can create many. Namespaces aren’t merely for DNS domain organization, though DNS services can run inside a namespace; the purpose is broader—scope and isolation. And namespaces do affect RBAC, because you apply Roles and RoleBindings per namespace (while ClusterRoles and ClusterRoleBindings can grant access cluster-wide).

Namespaces provide a way to partition a Kubernetes cluster into separate, isolated environments. They scope all namespaced objects (like pods, services, and deployments) so that what you create in one namespace stays contained there. This scoping also controls access: you can grant users permissions that apply only within a specific namespace, so their privileges don’t automatically extend to other parts of the cluster.

That’s why the statement about isolating resources and limiting privileges is the best fit. By design, a Role and its associated RoleBinding grant access only inside a particular namespace, so users or teams can operate independently in their own spaces without affecting others. If you need cross-namespace access, you’d typically use cluster-wide roles or bindings, but the default and common usage is namespace-scoped.

The other ideas don’t align with how namespaces work: there isn’t just one global namespace, as you can create many. Namespaces aren’t merely for DNS domain organization, though DNS services can run inside a namespace; the purpose is broader—scope and isolation. And namespaces do affect RBAC, because you apply Roles and RoleBindings per namespace (while ClusterRoles and ClusterRoleBindings can grant access cluster-wide).