Why does Kubernetes require separate RoleBindings and ClusterRoleBindings instead of using a single binding type for all scopes?

hard📝 Conceptual Q10 of 15

Kubernetes - RBAC and Security

ATo clearly separate namespace-scoped and cluster-scoped permissions for security and clarity

BBecause ClusterRoleBindings are deprecated and replaced by RoleBindings

CTo allow RoleBindings to create users and ClusterRoleBindings to delete users

DBecause RoleBindings can only bind to ServiceAccounts

Step-by-Step Solution

Solution:

Step 1: Understand RBAC design
Kubernetes separates RoleBindings and ClusterRoleBindings to distinguish between namespace-scoped and cluster-scoped permissions.
Step 2: Security and clarity reasons
This separation helps enforce security boundaries and makes permission management clearer.
Final Answer:
To clearly separate namespace-scoped and cluster-scoped permissions for security and clarity -> Option A
Quick Check:
Separate bindings = clear scope and security [OK]

Quick Trick: RoleBindings = namespace scope; ClusterRoleBindings = cluster scope [OK]

Common Mistakes:

Master "RBAC and Security" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes