Certification guide
CKADCertified Kubernetes Application Developer: the honest guide
CKAD is a hands-on exam against live clusters. You get 15 to 20 tasks, a terminal, and 120 minutes, open book against the Kubernetes documentation. You either make the application run the way the task says or you do not; there are no options to eliminate and nothing to recognize.
It is the developer's Kubernetes exam. Where CKA certifies the person who builds and repairs the cluster, CKAD certifies the person who builds and runs applications on a cluster someone else operates: deployments, configuration, probes, services, and the debugging in between. Registration includes a free second attempt and two sessions of the Killer.sh simulator, which changes how you should approach booking it.
Who CKAD is for
A good fit if
- You write or deploy software that runs on Kubernetes and someone else runs the cluster.
- You work in a team moving services onto Kubernetes and you are the one wiring up the manifests, config, and probes.
- You want a credential that demonstrably cannot be passed by memorization, at the application level rather than the cluster level.
- You are comfortable with containers and want the fastest route to a respected Kubernetes certification, since CKAD's curriculum is narrower than CKA's.
Probably not, if
- You have never used containers. Learn Docker and container fundamentals first; this exam assumes them entirely.
- You operate clusters: installation, upgrades, etcd, node management. That is CKA, and CKAD will not test any of it.
- You want Kubernetes theory or architecture knowledge for its own sake. Every task on this exam is something you type into a terminal under a clock.
Is CKAD worth it?
For a developer shipping onto Kubernetes, yes. The format is the value: hiring managers who know the exam know it cannot be crammed, because every mark comes from making something actually work on a live cluster in limited time.
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 the practice environment is a free local cluster, so the all-in cost of a real chance at passing is lower than most proctored exams at this level.
It is a poor choice if your interest is running clusters rather than running applications on them. CKA is the operator's exam and carries more weight for platform and SRE roles. Taking CKAD as a stepping stone to CKA works, but they are siblings, not a sequence, and neither requires the other.
What the exam actually asks you to do
Entirely hands-on: tasks in a terminal against live clusters, open book against the Kubernetes documentation. No multiple choice at all.
Item formats
- Performance-based
The highlighted formats are the ones you cannot answer from memory alone. Linux Foundation, CKAD exam details ↗
Domain breakdown and official weightings
From the official published CNCF curriculum. Application Environment, Configuration and Security is the heaviest domain at 25 percent, followed by Application Design and Build at 20 percent.
- Application Design and Build20%
- Application Deployment20%
- Application Observability and Maintenance15%
- Application Environment, Configuration and Security25%
- Services and Networking20%
Study plans by experience level
Deploying to Kubernetes at work
3 to 4 weeksat 6 hours
- 1Week 1: read the curriculum and mark what your CI pipeline does for you. If deploys happen through a template you never touch, the gap is writing and fixing manifests yourself, under time pressure.
- 2Week 2: the configuration and security domain, which is 25 percent of the exam and the most common weak spot. ConfigMaps, Secrets, SecurityContexts, ServiceAccounts, and resource requests and limits, built by hand on a kind or minikube cluster.
- 3Week 3: speed. Drill kubectl imperative commands and generate every manifest with dry-run output instead of writing YAML from nothing. Work this site's free CKAD questions to check you can read a manifest and spot what is wrong with it quickly.
- 4Week 4: both Killer.sh sessions, spaced apart, each treated as a real sitting against the clock.
Containers understood, new to Kubernetes
8 to 10 weeksat 8 hours
- 1Weeks 1 to 3: core workloads on a local kind or minikube cluster. Pods, Deployments, Jobs, CronJobs, and multi-container patterns, each built by hand and then rebuilt from an imperative command with dry-run.
- 2Weeks 4 to 5: configuration and security, the 25 percent domain. ConfigMaps, Secrets, SecurityContexts, and quotas, wired into running applications rather than studied as definitions.
- 3Weeks 6 to 7: services, networking, and deployment strategies. Expose applications, break the connection deliberately, and fix it. Add probes and rolling updates, and roll one back.
- 4Week 8: observability and maintenance. Logs, exec, describe, and debugging a pod that will not start. Practice finding the relevant page in the Kubernetes docs fast, because the exam is open book and the clock does not stop while you search.
- 5Weeks 9 to 10: both Killer.sh sessions and timed runs through practice tasks, including this site's free questions with realistic YAML.
Developer, no container experience
12 to 14 weeksat 8 hours
- 1Weeks 1 to 3: containers first. Build images, understand layers, registries, and container networking, because CKAD assumes all of it without teaching any of it.
- 2Weeks 4 to 7: Kubernetes workloads and configuration on a local cluster, with the configuration and security domain given the most repetition.
- 3Weeks 8 to 10: services, networking, ingress basics, and deployment strategies, plus observability: probes, logs, and debugging broken pods.
- 4Weeks 11 to 12: speed work. Imperative kubectl, dry-run manifest generation, and documentation lookups against the clock.
- 5Weeks 13 to 14: both simulator sessions, spaced apart, and a final pass over whichever domain the first session exposed.
Common mistakes
- Writing YAML by hand
- Time is the binding constraint: 15 to 20 tasks in 120 minutes leaves only a few minutes per task. Generating a manifest with kubectl and dry-run output and then editing it is several times faster than typing one from nothing, and candidates who skip that habit run out of time on tasks they knew how to do.
- No kubectl speed work
- Knowing what to do and doing it quickly are different skills, and the exam only pays for the second. Aliases, imperative commands, and fast context switching between tasks need dedicated drilling, and everyday exposure does not build them. If a Deployment with a specific image and replica count takes you more than a minute to create, that is the study gap.
- Skimming the configuration and security domain
- Application Environment, Configuration and Security is 25 percent of the exam, the largest single domain, and the least glamorous. SecurityContexts, ServiceAccounts, quotas, and Secrets are exactly the material a developer's day job touches least, which is why the exam weights them and why candidates lose marks there.
- Meeting the documentation for the first time in the exam
- The exam is open book against the Kubernetes docs, so finding the right example page quickly is part of the tested skill. Candidates who study from a course and never practice inside the docs spend exam minutes searching for what a prepared candidate bookmarks in their head.
- Saving the simulator for the end
- Two Killer.sh sessions are included with registration and it runs harder than the real exam. Used as a final confidence check the night before, it demoralises. Used as scheduled study with time between sessions to fix what it exposes, it is the best preparation available.
What comes after passing
CKAD lasts two years, shorter than most certifications here, and renewal means passing the current exam again. The Linux Foundation discounts exams heavily and often, and those discounts apply to renewals, so timing the purchase is worth real money.
CKA is the natural sibling if your work drifts toward operating clusters rather than deploying onto them. There is meaningful overlap in tooling and none in emphasis, so the second exam is cheaper in study time than the first.
CKS, the security specialization, requires an active CKA to sit, not CKAD. If CKS is the goal, CKA is the required intermediate step.
Kubernetes moves fast enough that a two-year-old pass genuinely goes stale. Deprecated API versions are exactly what a hands-on renewal exam notices, so treat the renewal as study rather than paperwork.
Where people go next
Costs across the full renewal cycle are on the CKAD cost page.
Frequently asked questions
Is the CKAD 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 booking strategy: a first attempt carries no marginal cost, so sitting slightly early to experience the time pressure for real is defensible here in a way it is not on exams that charge per try.
What is the difference between CKAD and CKA?
CKAD is the developer's exam: building, configuring, deploying, and debugging applications on a cluster someone else runs. CKA is the operator's exam: installing, upgrading, and repairing the cluster itself. Both are terminal-only and open book. Neither is a prerequisite for the other, and CKAD's narrower curriculum makes it the faster of the two to prepare for.
Can I use the Kubernetes documentation during the exam?
Yes, the exam is open book against the official docs, and documentation lookup speed is part of what the exam effectively tests. What it does not give you is time: 15 to 20 tasks in 120 minutes means knowing where an example lives matters more than knowing that one exists.
Do I need my own cluster hardware to prepare?
No. CKAD has no cluster installation content, so kind or minikube on a laptop covers the entire curriculum for free. That is a real difference from CKA, where kubeadm cluster building wants separate nodes.
How hard is CKAD?
The pass mark is 66 percent and the difficulty is time, not depth. Most tasks are things a working Kubernetes user can do; doing 15 to 20 of them in 120 minutes is the exam. Candidates who drill kubectl speed and manifest generation pass, and candidates who only know the material tend to run out of clock.
How long does CKAD last?
Two years. There is no continuing education route, so renewal means sitting the current exam again, though the Linux Foundation discounts exams often enough that paying list price for a renewal is usually avoidable.
Keep reading
- CKAD practice questions
Free sample questions with the full explanation on every answer.
- Free CKAD practice test
10 original questions, playable now. No account, no card.
- CKAD exam format
How many questions, how long, what the items look like, and how long it stays valid.
- CKAD passing score
The exact cut score, what kind of number it is, and the retake terms.
- How hard is CKAD?
An honest difficulty read from the format, the clock and the weights.
- What CKAD costs
The voucher price, the retake, and what renewal costs across the cycle.
Practice CKAD 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 CKAD questions