CKA vs CKAD: Which Kubernetes Certification Should You Take?

Put the CKA and the CKAD side by side and the usual deciding factors disappear. Both are performance-based: you solve real tasks in a live environment instead of picking answers. Both run two hours, both are listed at $445 for the exam alone, both require 66 % to pass, both include one retake inside a twelve-month eligibility window, both stay valid for two years, both have no prerequisites, and both are currently set on the same Kubernetes release. There is no harder one hiding in the logistics.

The fact that actually reframes the choice sits in the blueprints, and it is not the one people repeat. Everyone says CKA is operations and CKAD is development. The sharper version is this: Troubleshooting is 30 % of the CKA — its single largest domain — and it does not exist as a domain on the CKAD at all. Close to a third of the CKA is diagnosing a cluster somebody else broke, with a clock running. Nothing on the CKAD asks you to do that; its largest domain, at 25 %, is Application Environment, Configuration and Security.

There is a second, quieter difference, and it is in the rulebook rather than the syllabus: the two exams do not permit exactly the same documentation. This page works through both blueprints, the allowed resources, and what each credential does for you after you pass. For the whole field including KCNA and CKS, see which Kubernetes certification should you choose; if you are still deciding whether to sit an associate exam first, KCNA vs CKA covers that fork. Gnoseed does not sell or proctor these exams — it is a free study companion.

Both exams are open-documentation in a narrow, specific sense. The Linux Foundation publishes an allowed-resources list, and for CKA and CKAD it is the same three entries with one exception: the Kubernetes documentation, the Kubernetes blog and the Helm documentation are permitted on both, and the Gateway API documentation is permitted on the CKA only. That one line is the Linux Foundation telling you which exam expects Gateway API — treat it as a study signal, not a footnote.

The permission is narrower than "you can look things up". You may use the search box on the Kubernetes documentation site, but you must not open external search results — no jumping out to a blog post, a Stack Overflow answer or a GitHub issue. In practice that means your lookup is only as fast as your memory of where a thing lives in the docs tree. Knowing that the page you need is under Tasks rather than Concepts saves more time than knowing the flag itself.

Beyond the websites you also get task-specific material in the Quick Reference boxes inside the exam, the documentation the distribution installs under /usr/share, and the distribution packages. And because the whole session is proctored, no other applications or browser windows may be running. Confirm the current allowed-resources list on the Linux Foundation site before you book — it is revised alongside the curriculum.

The overlap is real but smaller than the shared "Kubernetes certification" label implies. Services and Networking appears on both at 20 %, and the workload objects — Pods, Deployments, ConfigMaps, Secrets, probes, resource requests — are examinable on both, though the CKA folds them into a 15 % Workloads and Scheduling domain while the CKAD spreads them across three domains totalling 65 %. If you sit one and then the other within the same two-year window, that shared ground is the part you will not have to relearn.

The non-overlap is where the preparation diverges. The CKA has 25 % on cluster architecture, installation and configuration — etcd, control-plane components, cluster upgrades, node lifecycle — none of which the CKAD touches. The CKAD has an entire 25 % domain on application environment, configuration and security that goes deeper into the developer-facing surface than the CKA ever does.

And then there is the asymmetry that decides it for most people: 30 % versus nothing. Troubleshooting is not a topic you can finish reading about. It is the domain that rewards having broken things before, which is why CKA candidates who have never operated a cluster tend to be surprised by it, and why CKAD candidates never meet it at all.

Both certifications are valid for two years, and both now feed the Linux Foundation CARE program: passing either the CKA or the CKAD automatically renews an active KCNA, for certifications earned or recertified on or after 1 January 2026. If you already hold the KCNA, that is a renewal you get for free by doing something you were going to do anyway.

The CKA has one thing the CKAD does not: it is the gateway to the CKS, which requires an active CKA to sit. Since June 2026 that relationship runs both ways — passing or recertifying the CKS reinstates or extends the CKA, aligning the CKA expiry to the new CKS date. So the CKA is not just an exam, it is the entry point to a renewal chain; the CKAD sits outside it.

None of this makes the CKAD the lesser credential. It makes the CKA the more load-bearing one in a certification plan. If you have no interest in the CKS and no KCNA to renew, the chain argument is worth nothing and you should pick purely on the blueprint.