Which RBAC object grants namespace-scoped permissions to users or service accounts?

Which RBAC object grants namespace-scoped permissions to users or service accounts?

• A. Role
• B. RoleBinding
• C. ClusterRole
• D. ClusterRoleBinding

Answer: (A)

Role defines a set of permissions that apply within a single namespace. It specifies what actions (verbs) can be performed on which resources inside that namespace. To give someone or a service account those permissions, you bind the Role to the subject using a RoleBinding, also scoped to that namespace. ClusterRole, on the other hand, holds permissions that can apply cluster-wide or across multiple namespaces, and is bound with a ClusterRoleBinding (which can operate at the cluster level). So for namespace-scoped access, the Role is the object that encapsulates the permissions, with a RoleBinding tying them to users or service accounts in that namespace.

Role defines a set of permissions that apply within a single namespace. It specifies what actions (verbs) can be performed on which resources inside that namespace. To give someone or a service account those permissions, you bind the Role to the subject using a RoleBinding, also scoped to that namespace.

ClusterRole, on the other hand, holds permissions that can apply cluster-wide or across multiple namespaces, and is bound with a ClusterRoleBinding (which can operate at the cluster level). So for namespace-scoped access, the Role is the object that encapsulates the permissions, with a RoleBinding tying them to users or service accounts in that namespace.