KCNA, CKA, CKAD, CKS: Which Kubernetes Certification, and in What Order

The Kubernetes certification family has grown to the point where choosing between its members is a real decision rather than an obvious one. Four exams carry the recognizable names, they share a vocabulary, and their marketing copy blurs together into a general suggestion that you should buy all of them. You should not buy all of them.

Here is what each actually measures, taken from the Linux Foundation’s own pages rather than from anyone’s summary.

The four, side by side

	KCNA	CKAD	CKA	CKS
Price	$250	$445	$445	$445
Duration	90 minutes	2 hours	2 hours	2 hours
Format	Multiple choice	Performance based	Performance based	Performance based
Prerequisite	None	None	None	A passed CKA
Valid for	2 years	2 years	2 years	2 years

Every one of them currently tests against Kubernetes v1.35. The Linux Foundation states that exams realign to the most recent Kubernetes minor version within roughly four to eight weeks of that version’s release, which is a detail worth holding on to if you are booking several months out. Study material written against an older minor version ages faster than most candidates expect.

KCNA is a different kind of exam

The KCNA is the only one of the four that is multiple choice, and at $250 it is the only one priced like an entry point. Ninety minutes, no prerequisites, and a curriculum weighted like this:

• Kubernetes Fundamentals: 44%
• Container Orchestration: 28%
• Cloud Native Application Delivery: 16%
• Cloud Native Architecture: 12%

Nearly three quarters of the exam sits in the first two domains. It is a vocabulary and concepts credential, and it is honest about that.

Who it suits: people who work near Kubernetes without operating it. Managers, analysts, sales engineers, developers on teams where somebody else runs the platform, and career changers who want a structured reason to learn the landscape before committing to a hands-on exam.

Who it does not suit: anyone who already runs clusters. If you can debug a failing Pod today, the KCNA will teach you very little and the certificate will not impress anyone evaluating you for an operations role.

CKAD and CKA are siblings, not steps

This is the most common misreading. Candidates assume CKAD comes before CKA because “developer” sounds junior. They are peers with different subject matter.

The CKAD is about running applications on a cluster somebody else maintains. Pods, Deployments, ConfigMaps, Secrets, probes, resource requests, and the parts of networking a developer touches.

The CKA is about the cluster itself. Installation with kubeadm, etcd backups, certificate rotation, node lifecycle, RBAC, and above all troubleshooting, which alone accounts for 30% of the exam.

Pick by job, not by seniority. If you ship applications, CKAD. If you keep the platform up, CKA. If you genuinely do both, CKA is the harder and more transferable of the two, and its troubleshooting weighting makes it the better single credential to hold.

CKS is the only one with a gate

The CKS requires a passed CKA before you may attempt it. Note the exact wording: it requires having taken and passed the CKA, which is a slightly different thing from holding an unexpired certificate.

It covers cluster hardening, supply chain security, runtime detection, and the security-adjacent parts of the platform. It is the narrowest and most specialized of the four, and it is worth having when security is your actual remit rather than an interest.

Do not treat it as the natural next purchase after the CKA. Treat it as the exam you take when someone is paying you to secure clusters.

A defensible order

For most people the sequence is shorter than the catalogue implies.

If you do not yet operate clusters: KCNA, then decide. The $250 is a cheap way to find out whether the subject holds your interest before spending $445 on an exam that assumes fluency.

If you already operate clusters: go straight to the CKA. Skipping the KCNA costs you nothing, because no employer treats it as a prerequisite and the CKA does not check for it.

If you write the applications rather than run the platform: CKAD, and stop there unless your role changes.

If security is your job: CKA, then CKS, because the gate leaves no alternative.

The order nobody needs is all four in sequence. Two years of validity means every certificate you collect is a renewal obligation you have signed up for. Collecting credentials you will not use turns into a recurring bill and a recurring evening.

What the certificate is actually worth

A performance-based exam is one of the few credentials where the badge and the skill are hard to separate. You cannot pass the CKA by recognizing terminology, which means the certificate is genuine evidence that you did the thing at least once under time pressure.

That is a narrower claim than “certified professionals earn more,” and it is the one I would make in an interview. The exam proves you can operate a cluster on a bad day. Everything else is your job history’s problem.

If the CKA is the one you land on, our CKA Study Guide covers the current v1.35 environment, and what the exam format demands is worth reading first.

Sources: KCNA, CKAD, CKA, and CKS certification pages, Linux Foundation.