KCNA · Question #75
Which authorization-mode allows granular control over the operations that different entities can perform on different objects in a Kubernetes cluster?
The correct answer is B. Role Based Access Control. Role-Based Access Control (RBAC) is the Kubernetes authorization mode that enables granular permission management for users and service accounts to interact with cluster resources.
Question
Which authorization-mode allows granular control over the operations that different entities can perform on different objects in a Kubernetes cluster?
Options
- AWebhook Mode Authorization Control
- BRole Based Access Control
- CNode Authorization Access Control
- DAttribute Based Access Control
How the community answered
(38 responses)- A5% (2)
- B92% (35)
- D3% (1)
Why each option
Role-Based Access Control (RBAC) is the Kubernetes authorization mode that enables granular permission management for users and service accounts to interact with cluster resources.
Webhook Mode Authorization Control delegates authorization decisions to an external HTTP service, but RBAC is the standard for defining the granular rules themselves within Kubernetes.
Role Based Access Control (RBAC) allows administrators to define `Roles` or `ClusterRoles` with specific permissions (verbs like `get`, `list`, `create` on resources like `pods`, `deployments`) and then bind these roles to users or service accounts using `RoleBindings` or `ClusterRoleBindings`. This provides a powerful and flexible way to control who can do what in the cluster.
Node Authorization Access Control is a specialized authorization mode primarily used by kubelets to authorize API requests for resources they manage, not general user/service account granularity.
Attribute Based Access Control (ABAC) is an older, less flexible authorization mode that uses attributes for policies and is generally deprecated in favor of RBAC.
Concept tested: Kubernetes RBAC Authorization
Source: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
Topics
Community Discussion
No community discussion yet for this question.