KCNA · Question #209
Which of the following best describes the way kubernetes Role-based access control (RBAC) works?
The correct answer is B. Kubernetes RBAC states which users can perform which actions against which re-source. Kubernetes RBAC (Role-Based Access Control) specifies what actions authenticated users, groups, or service accounts are permitted to perform on specific resources within the cluster.
Question
Which of the following best describes the way kubernetes Role-based access control (RBAC) works?
Options
- AKubernetes does not do RBAC
- BKubernetes RBAC states which users can perform which actions against which re-source
- CKubernetes RBAC lists which operations on which resources are denied to users
- DKubernetes RBAC is responsible for authenticating subjects such as users and groups
How the community answered
(54 responses)- A2% (1)
- B89% (48)
- C7% (4)
- D2% (1)
Why each option
Kubernetes RBAC (Role-Based Access Control) specifies what actions authenticated users, groups, or service accounts are permitted to perform on specific resources within the cluster.
Kubernetes fundamentally implements RBAC as a robust security mechanism for authorization.
Kubernetes RBAC serves as an authorization layer that explicitly defines permissions, determining what actions (verbs like get, create, delete) a subject (user, group, or service account) is allowed to perform on specific Kubernetes API resources (like pods, deployments, secrets). It controls the operations permitted within the cluster.
Kubernetes RBAC is primarily an 'allow-list' system, defining what is permitted, rather than explicitly listing forbidden operations.
RBAC is an *authorization* mechanism that determines what an *authenticated* subject can do; it is not responsible for authenticating subjects themselves.
Concept tested: Kubernetes RBAC authorization definition
Source: https://kubernetes.io/docs/reference/access-authn-authz/rbac/
Topics
Community Discussion
No community discussion yet for this question.