CKA vs CKAD: Which Kubernetes Certification Should You Take?

Take the CKA if your job is operating Kubernetes clusters (platform, DevOps, SRE) and the CKAD if your job is building applications that run on them (backend and full-stack development). Both are 2 hour, performance-based exams from the Linux Foundation, both cost US$445 with one free retake included, both pass at 66%, and both are valid for 2 years. The difference is not difficulty, it is the job being certified: the CKA tests whether you can install, operate, and repair a cluster, while the CKAD tests whether you can design, deploy, configure, and debug workloads on a cluster somebody else keeps alive.

CKA vs CKAD at a glance

What is the difference between CKA and CKAD?

Scope, not format. The CKA's five domains put 55% of the score on cluster operations: Troubleshooting at 30% and Cluster Architecture, Installation and Configuration at 25%, which includes kubeadm installs, highly available control planes, and the CNI, CSI, and CRI extension interfaces. You get handed broken clusters and the clock keeps running.

The CKAD never asks you to build or repair a cluster. Its five domains stay inside the developer workflow: Application Environment, Configuration and Security leads at 25% (ConfigMaps, Secrets, ServiceAccounts, SecurityContexts, resource limits), followed by Application Design and Build at 20% (container images, workload resources, multi-container Pod patterns), Application Deployment at 20% (rolling updates, blue/green and canary strategies, Helm, Kustomize), Services and Networking at 20%, and Application Observability and Maintenance at 15% (probes, logs, debugging, API deprecations).

There is real overlap in the middle. Both exams expect fluency with Deployments, rolling updates, Helm, Kustomize, services, NetworkPolicies, and Ingress. If you prepare for either one seriously, you are roughly halfway to the other.

Is CKAD easier than CKA?

Narrower, not easier. Engineers who hold both usually describe the CKAD as a sprint (many small tasks, brutal time pressure per item) and the CKA as a harder course (fewer topics you can dodge, and a 30% troubleshooting domain that hands you failures to diagnose cold). The passing bar is 66% on both, the format is identical, and neither can be passed on recognition the way a multiple choice exam sometimes can. Pick based on the job, not on perceived difficulty, because the difficulty is comparable.

Which one do US employers actually ask for?

Read the job postings, not the forums. Platform engineer, SRE, DevOps engineer, and Kubernetes administrator roles overwhelmingly name the CKA when they name anything. Backend and cloud-native developer postings name the CKAD, though less often, because developer hiring leans more on portfolio and interview performance than on certifications. If your resume says "operates infrastructure," the CKA carries more weight per dollar. If it says "ships services," the CKAD signals that your Kubernetes claims survive contact with a real cluster.

One more asymmetry worth knowing: the CKS security certification requires a valid CKA to sit, and postings for platform security roles increasingly list CKS. The CKAD does not open that door. If you might ever want the security track, the CKA is the only entry.

Can you take both, and in what order?

Plenty of engineers do, and the shared surface makes the second exam much cheaper to prepare for. The sensible order follows your current role. Developers usually take the CKAD first because it certifies work they already do daily, then add the CKA when their role drifts toward the platform. Ops-side engineers take the CKA first and add the CKAD only if they want to demonstrate the developer perspective too, which is less commonly needed. Taking both back to back works because the exam format, the simulator workflow, and half the objects involved are identical: budget most of your second prep block for the non-overlapping domains.

Teams running small estates sometimes discover mid-preparation that they do not need cluster surgery skills at all. If your production footprint is a handful of app servers rather than an orchestrated fleet, a platform that handles zero-downtime deploys and server provisioning covers the operations story without a control plane in sight, and the CKAD-style development skills matter more than cluster administration.

Does the free retake carry across both exams?

No. Each US$445 registration is for one exam and includes one retake of that same exam within its 12 month eligibility window, plus two sessions of that exam's simulator. Buying the CKA does not bank you an attempt at the CKAD or vice versa. Budget-wise that means the both-certs path costs US$890 at list price, though the Linux Foundation runs frequent sales and sells bundles at US$625 to US$645 that attach training to a single exam. The practical takeaway is simpler: treat each exam's included retake as insurance, not as a plan, because the seven weeks of evenings you spend preparing are worth more than the fee either way.

What about the KCNA for beginners?

If both hands-on exams feel out of reach, the Linux Foundation also runs the Kubernetes and Cloud Native Associate (KCNA), a written multiple choice exam that covers the ecosystem at a conceptual level. It is a legitimate first rung for career changers and students, but understand what it is not: US job postings for engineering roles rarely list it, and it does not substitute for either the CKA or CKAD in hiring conversations. Engineers with any production exposure should go straight to the hands-on exam that matches their role. The KCNA earns its keep mainly as a structured on-ramp for people who have never touched a cluster and need the vocabulary before the terminal.

How to prepare for either exam

The preparation logic is the same for both because the failure mode is the same: time. Every task decomposes into recall (which object, which field, which command) plus typing. Slow recall is what actually fails candidates, so drill it separately and first. Upload your course notes or the official CNCF curriculum to a quiz generator and grind question sets until service types, probe kinds, volume modes, and RBAC verbs come back in under five seconds. Then spend the two included simulator sessions purely on speed, because by then the knowledge is no longer the bottleneck.

Weight your drilling like the exam weights its domains. For the CKA that means troubleshooting scenarios above all: symptom, cause, first command. For the CKAD it means configuration and security objects: ConfigMap versus Secret consumption, requests versus limits, SecurityContext fields. The dedicated CKA practice exam generator and CKAD practice exam generator pages carry the full current domain tables, verified against the official CNCF curriculum for v1.35, so you can check any course you already own against what the exam actually tests.

The bottom line

Same price, same format, same bar, different job. Operate clusters: CKA, and it is the only path to CKS. Build on clusters: CKAD. Both expire after 2 years and both track Kubernetes releases, so whichever you pick, prepare from current material rather than a course recorded several versions ago. And since each fee already includes a free retake and two simulator sessions, the only genuinely expensive mistake is walking in with slow recall.