How to prepare for the KCNA exam: a practical study plan

Know what you’re studying: the five domains

The KCNA curriculum covers five domains: Kubernetes Fundamentals, Container Orchestration, Cloud Native Architecture, Cloud Native Observability and Cloud Native Application Delivery. The weighting leans toward the Kubernetes side — fundamentals and orchestration together are the core of the exam — so that is where your depth should be: pods, nodes, the control plane, the API, scheduling, services and networking, storage, and the basic security model, all understood well enough to explain rather than merely recognise.

But do not let the Kubernetes weighting fool you into ignoring the other three domains. They are the ones candidates under-prepare, because generic Kubernetes tutorials barely touch them. Observability (logs, metrics, traces and the tools around them), application delivery (CI/CD and GitOps concepts) and cloud-native architecture (autoscaling, serverless, open standards, the CNCF’s role) are all examinable, and a pass mark of 75% leaves little room to write off whole domains. Map your study plan to the official curriculum, not to whatever a tutorial happens to cover.

The study stack

You can prepare well without expensive materials. A sensible stack looks like this:

• The Kubernetes documentation — free, authoritative and closer to the exam’s framing than most courses; the concepts section is the backbone of the two biggest domains.
• CNCF and Linux Foundation training — the official KCNA-aligned courses follow the curriculum directly; check the Linux Foundation site for current free and paid options and exam bundles.
• Community study guides — the KCNA has a healthy ecosystem of open study guides and curated resource lists that map to the curriculum; useful for the ecosystem domains in particular.
• A small real cluster — minikube or kind on your own machine, or a free-tier managed cluster, to deploy something, break it and watch Kubernetes reconcile it.
• Practice questions and mock exams — the fastest way to find weak domains and to calibrate against the 75% pass mark before you spend the exam fee.

Why hands-on still matters for a multiple-choice exam

It is tempting to treat a multiple-choice exam as a reading exercise, and honestly, you can pass the KCNA that way if your understanding is strong. But a few hours with a real cluster is the highest-leverage study time available, for two reasons. First, retention: the difference between reading that a Service gives pods a stable address and watching your own deployment stay reachable while its pods are replaced is the difference between a fact you revise and a fact you own. Concepts you have seen happen do not need memorising.

Second, speed on scenario questions. A fair share of KCNA questions describe a situation — a pod that will not schedule, traffic that is not arriving — and ask what is going on or which component is responsible. Candidates who have poked at a cluster answer these on recognition; candidates who have only read about one reason from first principles under exam conditions. You do not need CKA-level fluency, and you should not build your plan around the terminal. But an evening or two of deploying, scaling and deliberately breaking things in minikube repays itself many times over on exam day.

What trips people up

The most common failure mode is preparing for a Kubernetes exam when the KCNA is a cloud-native exam. The ecosystem breadth is the trap: candidates arrive fluent in pods and deployments and then meet questions about telemetry types, GitOps, serverless concepts, open standards or the CNCF itself — topics from the observability, delivery and architecture domains that a Kubernetes-only study plan never covered. If a mock exam shows a lopsided score, strong on fundamentals and weak everywhere else, that is the signature of this mistake, and the fix is simply to study the curriculum’s outer domains deliberately.

The second trap is vocabulary. As a conceptual exam, the KCNA leans on precise terminology — the difference between a pod and a container, a metric and a trace, a Deployment and a Service — and distractor options are often terms from the right neighbourhood but the wrong concept. Sloppy definitions that would never matter in day-to-day work cost real marks here. When you revise, be able to define each term in a sentence, not just use it loosely.

Exam mechanics, so nothing surprises you

The KCNA is taken online with remote proctoring, administered by the Linux Foundation: you will need a quiet room, a machine that passes their environment checks, and identification. The exam itself is around 60 multiple-choice questions in 90 minutes with a passing score of 75% — a comfortable pace of roughly a minute and a half per question, so read carefully rather than racing. There is no live terminal and nothing to install for the exam content itself.

The fee — about $250 USD at the time of writing — typically includes one free retake, which is worth knowing when you decide whether to book: a narrow miss is not money gone. Confirm the current price, bundle offers and retake policy on the Linux Foundation’s KCNA page before paying, because all of these change. Certification is valid for three years. For the wider context of what the KCNA is and how it compares to the hands-on CKA and CKAD, see our KCNA certification guide.

The readiness signal

Book the exam when your mock results are consistently — not occasionally — clear of the 75% pass mark across full-length practice runs, with no single domain dragging far behind the rest. Consistency matters more than a personal best: one strong mock can be luck, three in a row is preparation. If your scores are close but wobbling, the free-retake cushion makes booking a reasonable gamble; if one domain is persistently weak, a few targeted days on it move the needle faster than another general pass through everything. Our KCNA revision section covers the domains lesson by lesson, and the practice questions and mock exams there are built to give you exactly this signal.