Certification guide
CKACertified Kubernetes Administrator: the honest guide
CKA is a hands-on exam against live clusters. You are given tasks and a terminal, it is open book against the Kubernetes documentation, and you either complete the work or you do not. There is nothing to recognise and no options to eliminate.
It is the most respected Kubernetes credential for a reason: the format makes it very difficult to pass without genuinely being able to operate a cluster. Registration includes a free second attempt and two sessions of an exam simulator, which changes how you should approach booking it.
Who CKA is for
A good fit if
- You run or are about to run Kubernetes in production and want the credential that matches.
- You work in platform engineering, DevOps or SRE and Kubernetes is on your roadmap.
- You want a certification that demonstrably cannot be passed by memorisation.
- Your employer needs certified staff for a partner requirement or a customer commitment.
Probably not, if
- You have never used containers. Learn Docker and container fundamentals first; this exam assumes them entirely.
- You want Kubernetes theory or architecture knowledge. This is an operations exam and every task is something you type.
- You want a developer-focused credential. CKAD covers building and deploying applications rather than administering the cluster.
Is CKA worth it?
For anyone operating Kubernetes, this is one of the most credible certifications in the catalog precisely because of the format. Hiring managers who know the exam know it cannot be crammed, and that reputation is the value.
The price looks high at $445 until you count what is in it. A free second attempt and two Killer.sh sessions are included, and priced against a comparable exam plus a retake plus a simulator it is competitive rather than expensive.
It is a poor choice if Kubernetes is aspirational rather than current. The exam is practical and time-pressured, and there is no way to prepare for it that does not involve running clusters regularly.
What the exam actually asks you to do
Entirely hands-on. There are no multiple choice questions at all: you get a terminal against live Kubernetes clusters and are scored on the state of the cluster when time runs out.
Item formats
- Hands-on lab
The highlighted formats are the ones you cannot answer from memory alone. Linux Foundation, CKA exam details ↗
Domain breakdown and official weightings
From the official published CNCF curriculum. Troubleshooting is the heaviest domain at 30 percent, followed by Cluster Architecture, Installation and Configuration at 25 percent.
- Cluster Architecture, Installation and Configuration25%
- Workloads and Scheduling15%
- Services and Networking20%
- Storage10%
- Troubleshooting30%
Where to focus: Troubleshooting is the single largest domain at 30 percent and it is the one you cannot cram. Break a cluster deliberately, then fix it, and do that more often than you read.
Study plans by experience level
Running Kubernetes at work
4 to 6 weeksat 6 hours
- 1Week 1: read the curriculum and mark what your platform does for you. Managed clusters hide the installation and upgrade work that the exam tests directly.
- 2Weeks 2 to 3: kubeadm cluster building, upgrades and etcd backup and restore. This is the biggest gap for people who only use managed Kubernetes.
- 3Week 4: speed. Practise imperative commands and generating manifests with dry-run rather than writing YAML by hand, because time is the real constraint.
- 4Weeks 5 to 6: both Killer.sh sessions, spaced apart, treating each as a real sitting.
Containers understood, new to Kubernetes
10 to 12 weeksat 8 hours
- 1Weeks 1 to 3: core objects on a local cluster with kind or minikube. Pods, deployments, services and configuration, built by hand.
- 2Weeks 4 to 6: scheduling, networking and storage, which together are 45 percent of the curriculum.
- 3Weeks 7 to 8: cluster installation with kubeadm on virtual machines, plus upgrades and etcd backup.
- 4Weeks 9 to 10: troubleshooting, which is the largest domain at 30 percent. Break your own cluster deliberately and fix it.
- 5Weeks 11 to 12: both simulator sessions and documentation navigation drills.
Linux administrator, no container experience
16 weeksat 8 hours
- 1Weeks 1 to 4: containers first. Images, registries, networking and storage at the container level, because Kubernetes assumes all of it.
- 2Weeks 5 to 9: Kubernetes core objects and workloads on a local cluster.
- 3Weeks 10 to 12: networking, storage and scheduling in depth.
- 4Weeks 13 to 14: cluster lifecycle with kubeadm, and etcd backup and restore.
- 5Weeks 15 to 16: troubleshooting practice and both simulator sessions.
Common mistakes
- Practising away from the documentation
- The exam is open book against the Kubernetes docs, so finding a manifest example quickly is part of the skill being tested. Candidates who study from a course and meet the documentation for the first time in the exam lose time they cannot recover.
- Writing YAML by hand
- Time is the binding constraint. Generating a manifest with an imperative command and dry-run output and then editing it is several times faster than typing one from nothing, and candidates who have not practised that habit run out of time on tasks they knew how to do.
- Only using a managed cluster
- Managed Kubernetes hides exactly what the exam tests: kubeadm installation, upgrades, and etcd backup and restore. Somebody who has only ever used a cloud provider's control plane has a large blind spot over a well-weighted part of the curriculum.
- Saving the simulator for the end
- Two Killer.sh sessions are included with registration and it is harder than the real exam. Used as a final confidence check it is demoralising; used as scheduled study with a fortnight between sessions it is the best preparation available.
- Underestimating troubleshooting
- It is 30 percent of the curriculum, the largest domain, and it cannot be prepared by reading. Breaking a cluster deliberately and fixing it is the only practice that transfers, and it is what a second failure usually comes down to.
What comes after passing
CKS, the security specialisation, is the usual next step and it requires an active CKA to sit. CKAD is the sideways move toward the developer perspective.
The certification lasts two years, which is shorter than most here, and there is no continuing education route. Renewal means passing the current exam again, so plan for it rather than being surprised.
The Linux Foundation discounts certifications several times a year, and those discounts apply to renewals. Timing a renewal purchase is worth real money.
Kubernetes moves quickly enough that a two-year-old pass genuinely is out of date. Deprecated APIs are exactly the sort of thing a hands-on exam notices, so treat renewal as study.
Costs across the full renewal cycle are on the CKA cost page.
Frequently asked questions
Is the CKA retake really free?
Registration includes a second attempt at no extra cost, which is why the retake line on the cost page is zero. It changes how you should book: on an exam where a retake is another full fee the advice is to wait until you are ready, whereas here a first attempt carries no marginal cost and seeing the format for real has value.
How important is the Killer.sh simulator?
It is the single best preparation available and two sessions come with your registration. It is deliberately harder than the real exam, so a poor score on it is not a reliable signal of failure. Use both sessions as scheduled study rather than as a final check.
Can I really use the Kubernetes documentation during the exam?
Yes, the exam is open book against the official documentation, and that is why documentation navigation is a skill worth practising. What it does not give you is time, so knowing where an example lives matters more than knowing that one exists.
Do I need to know YAML by heart?
No, and trying to is a mistake. The efficient approach is generating manifests with imperative commands and dry-run output, then editing what comes back. Candidates who write everything by hand tend to run out of time rather than out of knowledge.
How long does CKA last?
Two years, which is shorter than the three-year cycle most certifications here use, and there is no continuing education alternative. Renewal means sitting the current exam again, though the Linux Foundation discounts exams often enough that paying list price is usually avoidable.
Keep reading
- CKA practice questions
Free sample questions with the full explanation on every answer.
- Free CKA practice test
Ten real questions, playable now. No account, no card.
- CKA passing score
The exact cut score, what kind of number it is, and the retake terms.
- How hard is CKA?
An honest difficulty read from the format, the clock and the weights.
- What CKA costs
The voucher price, the retake, and what renewal costs across the cycle.
Practise CKA for free while you decide
Original questions written from the published objectives, with the concept, the reasoning, and a note on every wrong option. No account needed to start.
Start free CKA questions