In Kubernetes, which authorization mode is known for offering detailed control over what specific actions can be performed on different resources within the cluster?

In Kubernetes, which authorization mode is known for offering detailed control over what specific actions can be performed on different resources within the cluster?

• A. Role-Based Access Control
• B. Resource-Based Access Control
• C. Rule-Based Access Control
• D. Read-Only Access Control

Answer: (A)

Role-Based Access Control in Kubernetes provides fine-grained control over who can perform which actions on which resources in a cluster. With RBAC, you define Roles that list the specific resources and the allowed verbs (such as get, list, watch, create, update, patch, delete). These Roles can be scoped to a namespace or be cluster-wide. Subjects like users, groups, and service accounts are granted those permissions by attaching the Roles to them through RoleBinding or ClusterRoleBinding. This setup lets you tailor permissions very precisely—for example, allowing a user to manage Deployments in one namespace while preventing changes in another, or permitting read-only access to certain resources while restricting destructive actions. The other options don’t fit Kubernetes’ built-in authorization model. Resource-Based Access Control isn’t a standard Kubernetes mode for per-resource permissions, and terms like Rule-Based or Read-Only Access Control aren’t official modes used to describe Kubernetes authorization. RBAC uniquely provides the structured, scalable way to control exactly which actions are allowed on which resources across the cluster.

Role-Based Access Control in Kubernetes provides fine-grained control over who can perform which actions on which resources in a cluster. With RBAC, you define Roles that list the specific resources and the allowed verbs (such as get, list, watch, create, update, patch, delete). These Roles can be scoped to a namespace or be cluster-wide. Subjects like users, groups, and service accounts are granted those permissions by attaching the Roles to them through RoleBinding or ClusterRoleBinding. This setup lets you tailor permissions very precisely—for example, allowing a user to manage Deployments in one namespace while preventing changes in another, or permitting read-only access to certain resources while restricting destructive actions.

The other options don’t fit Kubernetes’ built-in authorization model. Resource-Based Access Control isn’t a standard Kubernetes mode for per-resource permissions, and terms like Rule-Based or Read-Only Access Control aren’t official modes used to describe Kubernetes authorization. RBAC uniquely provides the structured, scalable way to control exactly which actions are allowed on which resources across the cluster.