mediumMultiple Choice
CKS Practice Question: An admin runs 'kubectl auth reconcile -f…
An admin runs 'kubectl auth reconcile -f rbac.yaml' and gets an error that the user does not have permission to create ClusterRoleBindings. What is the most likely cause?
⚠ Common exam trap
Candidates often confuse a permission error with a resource conflict (Option A) or a connectivity issue (Option C), but the specific error message 'does not have permission to create ClusterRoleBindings' directly points to insufficient RBAC privileges in the current kubeconfig context.
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
✓
The user's kubeconfig context does not have RBAC permissions to create ClusterRoleBindings.
The error indicates that the user's current kubeconfig context lacks RBAC permissions to create ClusterRoleBindings. The `kubectl auth reconcile` command attempts to apply the RBAC resources defined in the YAML file, and if the user's credentials (typically from a certificate or token) do not include the `create` verb on `clusterrolebindings` in the RBAC authorization layer, the API server will reject the request with a 403 Forbidden error. This is a direct permission issue, not a connectivity or syntax problem.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The ClusterRoleBinding already exists.
Why it's wrong here
An 'AlreadyExists' error would only occur if kubectl were issuing a bare create against an existing object. However, 'kubectl auth reconcile' is specifically designed to idempotently create or update RBAC resources, so a pre-existing ClusterRoleBinding would be detected, compared, and patched rather than rejected. The 403 Forbidden response indicates that the API server never reached the point of checking object existence; authorization failed first.
- ✗
The YAML file has a syntax error.
Why it's wrong here
A YAML syntax or schema error is caught by kubectl's client-side parsers before any API request is dispatched, producing messages like 'error unmarshaling JSON' or 'ValidationError'. The presence of an 'Error from server (Forbidden)' response proves the request was successfully serialized, transmitted, and processed by the API server's RBAC middleware. Therefore the failure cannot stem from a malformed document; the file's contents are irrelevant to an authorization denial.
- ✗
The Kubernetes API server is not reachable.
Why it's wrong here
Connectivity failures manifest as transport-level messages, such as 'Unable to connect to the server: dial tcp 10.0.0.1:6443: connect: connection refused' or an i/o timeout. A Forbidden error requires a completed HTTP round-trip, meaning the kubeconfig's server address was reachable, TLS was negotiated, and the API server authenticated the user and evaluated RBAC rules. The authorization decision is made after a successful connection, so an unreachable API server would never yield this specific error.
- ✓
The user's kubeconfig context does not have RBAC permissions to create ClusterRoleBindings.
Why this is correct
The 'Forbidden' error is the API server's authorization rejection: the user identified by the current kubeconfig context has not been granted 'create' permission on 'clusterrolebindings' in the 'rbac.authorization.k8s.io' API group at cluster scope. 'kubectl auth reconcile' attempts to create the binding when it does not exist, triggering this RBAC denial. To resolve it, the operator must either switch to a context with sufficient permissions (e.g., cluster-admin) or have an administrator grant the required RBAC rule.
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
This CKS question is part of Courseiva's 845-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.