easyMultiple Choice
CKS Practice Question: The default authorization mode for a new…
What is the default authorization mode for a new Kubernetes cluster?
⚠ Common exam trap
CNCF often tests the misconception that ABAC is the default because it was the original authorization mode in early Kubernetes versions, but RBAC has been the default since v1.8 and is the recommended standard for security.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
RBAC
RBAC (Role-Based Access Control) is the default authorization mode for new Kubernetes clusters since version 1.8. When you initialize a cluster with kubeadm, the API server is automatically configured with the `--authorization-mode=RBAC` flag, enabling fine-grained access control based on roles and bindings.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
ABAC
Why it's wrong here
ABAC (Attribute-Based Access Control) is not the default authorization mode for a new Kubernetes cluster. It requires manually creating and maintaining JSON policy files, and it lacks the flexibility and auditability of RBAC. Although ABAC was used in early Kubernetes versions, modern distributions have moved to RBAC as the default due to ABAC's complexity and security limitations.
- ✗
Node
Why it's wrong here
Node authorization is a specialized authorization mode that grants permissions to kubelets based on their node identity. It is never used as a standalone default; instead, it is typically enabled alongside RBAC in the kube-apiserver's authorization chain. The Node mode only handles node-to-API requests, making it insufficient for managing user or service account access across the cluster.
- ✗
AlwaysDeny
Why it's wrong here
AlwaysDeny is a basic authorization mode that rejects every API request, and it cannot be the default because it would render the cluster completely unusable. It is only intended for testing or temporary lockdown scenarios, not for normal operation. In practice, the default must allow legitimate cluster components and administrators to function, which AlwaysDeny does not permit.
- ✓
RBAC
Why this is correct
RBAC (Role-Based Access Control) is the default authorization mode in most modern Kubernetes distributions, including kubeadm and managed offerings like EKS, AKS, and GKE. It enables fine-grained control through Roles and ClusterRoles, bound to users, service accounts, and groups via RoleBindings and ClusterRoleBindings. This default provides a secure baseline and supports least-privilege access for both human administrators and in-cluster workloads.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
About these practice questions
Courseiva writes every CKS question from scratch — 845 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKS practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKS exam.