Bird
0
0

Why is it important to configure RBAC (Role-Based Access Control) separately for each cluster in a multi-cluster environment?

hard📝 Conceptual Q10 of 15
Kubernetes - Production Best Practices
Why is it important to configure RBAC (Role-Based Access Control) separately for each cluster in a multi-cluster environment?
ABecause RBAC settings automatically sync across clusters
BBecause each cluster has its own API server and security context
CBecause RBAC is only needed on the primary cluster
DBecause RBAC is deprecated in multi-cluster setups
Step-by-Step Solution
Solution:
  1. Step 1: Understand RBAC scope

    RBAC controls access per cluster since each has its own API server and security model.
  2. Step 2: Explain why separate configuration is needed

    Settings do not sync automatically; each cluster requires its own RBAC setup for security.
  3. Final Answer:

    Because each cluster has its own API server and security context -> Option B
  4. Quick Check:

    RBAC is cluster-specific due to separate API servers [OK]
Quick Trick: Configure RBAC per cluster for proper security [OK]
Common Mistakes:
  • Assuming RBAC syncs automatically
  • Thinking RBAC is only on one cluster
  • Believing RBAC is deprecated

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes