CKAD (Certified Kubernetes Application Developer): Cost, Exam Format, and Renewal Math

The CKAD and the CKA look almost identical on paper. Same vendor, same $445 price, same two-hour performance-based format in the same remote terminal, same 66 percent pass mark, same two-year clock. The difference is which side of the platform you stand on, and getting that split wrong is the most common way people waste this exam. The CKA certifies the person who runs the cluster. The CKAD certifies the person who ships applications onto it.

The role split that decides which one you sit

If your job is deploying, configuring, and troubleshooting workloads, defining Deployments and Services, wiring up ConfigMaps and Secrets, setting resource limits and probes, and debugging why a pod will not start, the CKAD is your credential. It is the developer’s Kubernetes exam. The CKA, by contrast, lives one layer down: node management, the control plane, etcd backups, cluster networking, and the administration a developer never touches. A backend or full-stack engineer whose team runs on Kubernetes, a DevOps engineer who owns the delivery pipeline, or a software developer moving into a cloud-native shop all map to the CKAD. Someone responsible for keeping the cluster itself alive maps to the CKA.

Skip the CKAD if you have never actually deployed to Kubernetes. CNCF sets no prerequisite, but the exam is a live keyboard test that assumes you have written and applied real manifests under time pressure before, and a candidate who has only read about kubectl apply will not finish. Skip it too if your responsibility is the platform rather than the workloads on it, because then you are paying $445 to prove the wrong half of the job; the CKA is the honest match, and the two are not interchangeable on a resume.

What it costs all-in

The exam is $445, and the fee includes two exam attempts, so a failed first sitting comes with a second one already paid for, provided you take it within 12 months of the original purchase. That built-in retake is worth naming plainly, because it is not how CompTIA, Cisco, or Red Hat price their exams, where a fail means buying the whole thing again. The purchase also bundles two Killer.sh simulator sessions, each with its own set of tasks and 36 hours of access, and the simulator runs harder than the real exam by design.

Prep costs almost nothing beyond your time. Kubernetes is open source, so a local kind or minikube cluster is the whole lab, and the official kubernetes.io documentation is both the free syllabus and a resource you are allowed to consult during the exam. The Linux Foundation runs frequent site-wide promotions (one was live on the date at the top), so treat $445 as the list price to plan around. A disciplined path is the $445 fee plus an optional video course on sale, with the genuine cost paid in hours spent writing and applying manifests until the workflow is muscle memory. The ROI Index shows how that figure compares across every credential we track.

The exam itself

CKAD is a two-hour, online-proctored, performance-based test on Kubernetes v1.37, aligned to each new minor release within roughly four to eight weeks. You solve a set of hands-on problems in a live command line, and 66 percent passes. There is no multiple choice. You may keep one browser tab on the official documentation, but the exam rewards speed, and the candidates who pass comfortably are the ones who have set up shell aliases and know the imperative kubectl shortcuts cold rather than hand-writing YAML for every task.

Time is the real adversary here. The task list is long for two hours, and the difference between passing and failing is usually how fast you generate manifests, not whether you know the concepts. CNCF does not publish a pass rate, so treat any percentage you see quoted as an estimate; the only official number is the 66 percent threshold you have to clear.

Renewal math over 9 years

The CKAD’s validity quietly changed. It was three years, and as of April 1, 2024 it is two, with certifications earned before that date grandfathered at the old three-year length. The Linux Foundation shortened it because the exam turns over almost completely every two years as Kubernetes evolves, and recertification means passing the current exam again. There is no continuing-education alternative.

Across nine years the arithmetic mirrors the CKA exactly. Continuous certification is the initial $445 plus a recertification sitting roughly every two years, about four of them in a nine-year window, which comes to around $2,225 in exam fees. The floor is $445 to earn it once and let it lapse when it stops earning its keep. That two-year retake is a recurring live exam, not a paperwork renewal, which is a heavier long-run commitment than the CE-credit ladders behind most CompTIA and Cisco credentials. Certification renewal costs explained places it in that wider context.

Nine-year cost of ownership: $445 to about $2,225, the exam once and allowed to lapse, up to the exam plus four full-price recertification sittings to stay continuously certified.

What it does for the occupation you are entering

The CKAD maps most directly to the software developers occupation (SOC 15-1252), the BLS category that covers the engineers who build and deploy the applications this exam is about. The panel on this page shows that occupation’s current national median wage and its very large headcount, and both describe the field rather than a raise the certificate hands you. What the CKAD concretely signals is that a developer can operate confidently inside Kubernetes, deploying and debugging real workloads instead of merely naming the objects, which is a specific, demonstrable competence a multiple-choice cloud badge cannot vouch for. The pay follows the role and the experience you bring, not the exam score.

Common mistakes

Sitting the wrong exam. The CKAD and CKA are not two difficulty levels of one credential; they certify different jobs. Confirm you want the developer’s exam, not the administrator’s, before you pay, because switching after the fact means a second $445.

Hand-writing YAML for everything. Two hours is tight, and candidates who type full manifests from scratch run out of time. Learn the imperative kubectl generators and --dry-run=client -o yaml workflow so the boilerplate writes itself.

Ignoring the included simulator. The fee already covers two Killer.sh sessions harder than the real test. Skipping them means meeting the exam’s time pressure for the first time when it counts.

Trusting version-stale material. The exam tracks current Kubernetes releases closely. Prep built for an older version drills deprecated APIs and syntax, so verify the version any course or practice set targets before relying on it.