ITGSS Certified DevOps Engineer Practice Test

What does the integrated Role-Based Access Control (RBAC) component in Kubernetes do?

1. Defines resource limits

2. Matches users/groups to permissions

3. Configures network policies

4. Creates service accounts

The correct answer is: Matches users/groups to permissions

The integrated Role-Based Access Control (RBAC) component in Kubernetes is designed to manage and enforce permissions for users and groups within the Kubernetes environment. It achieves this by defining roles that specify what actions can be taken on which resources and then binding these roles to users or groups. This ensures that only authorized individuals or services can perform certain operations, promoting security and control over the cluster. In Kubernetes, RBAC consists of roles and role bindings. A role defines a set of permissions, while role bindings assign that role to users or groups. This mechanism provides a flexible way to grant access and manage permissions based on the principle of least privilege, ensuring users and applications only have access to the resources they need to perform their functions. The other options, while important in the Kubernetes ecosystem, do not pertain specifically to the function of RBAC. Resource limits define how much of a given resource (like CPU or memory) a pod may consume, network policies dictate how pods communicate with each other, and service accounts represent identities for processes in pods, but these do not involve the management of user permissions in the same way RBAC does.