How to pass KCNA in 2026: a study plan, the domains and a practice strategy

What KCNA tests, in numbers

KCNA is delivered online with a remote proctor. The multiple-choice instructions list 60 questions and the FAQ gives 90 minutes and a 75% pass mark. The list price is $250 and the certification is valid for 2 years. The exam has four domains, and their weights are the most useful planning tool you have: they say how much of the exam each area is expected to cover.

Topics are quoted from the CNCF KCNA curriculum PDF; weights are from the official certification page. Both were read on 30 October 2026.

How to read the domain weights

The two largest domains, Kubernetes Fundamentals at 44% and Container Orchestration at 28%, carry most of the exam. That has two consequences. First, your study time should follow the same proportions: a week on community and governance at the expense of Pods and Services is a bad trade. Second, the small domains still matter at a 75% pass mark, because there is little room for a domain you skipped entirely.

Treat the weights as a budget. If you have twenty hours, roughly nine belong to Kubernetes Fundamentals, five or six to Container Orchestration, three to delivery and two or three to architecture. Adjust after your first practice set shows where you actually stand.

Kubernetes Fundamentals: what to know cold

This domain is the vocabulary of everything after it. You should be able to name what each core object is for, which component owns which job, and what happens when you apply a manifest. Questions often describe a situation and ask which object or component is responsible, so knowing the boundaries between similar things matters more than memorising field names.

• The control plane components (API server, etcd, scheduler, controller manager) and the node components (kubelet, container runtime, kube-proxy), and what each one does.
• Pods, ReplicaSets, Deployments, StatefulSets, DaemonSets, Jobs and CronJobs: which one fits a described workload.
• Namespaces, labels and selectors, and how Services find Pods through them.
• Declarative versus imperative management, and what kubectl apply does compared with create.
• Scheduling basics: requests, limits, taints, tolerations and node affinity at the level of what they achieve.
• Container images, registries and what a container runtime does under the kubelet.

Container Orchestration, delivery and architecture

The other three domains widen the view from a single cluster to how applications run and are delivered. Container Orchestration covers networking, security, troubleshooting and storage; expect questions on Service types, Ingress, NetworkPolicy, PersistentVolumes and claims, and how you would find out why a Pod is not running. Application delivery is about GitOps, CI/CD and debugging; architecture is about observability, cloud native principles and the CNCF community itself.

A six-week KCNA study plan

The plan below assumes a few hours a week and follows the domain weights. Each week mixes reading the official material with daily practice questions, so the review schedule has time to bring missed questions back. If you already run clusters, compress weeks one and two into one; if containers are new to you, add a week at the start.

How to practise without memorising answers

A question bank helps only if every question teaches something you could use on a different question. Answer before reading the options closely, then read the explanation whether you were right or not, and ask what the question was really testing. If you can say why each wrong option is wrong, you have learned the concept; if you only remember which letter was right, you have learned the question.

• Cover the options and answer from memory first; then check whether your answer is among them.
• For every miss, write one line: the concept, not the answer.
• Treat a lucky guess as a miss and bookmark it.
• Watch first-attempt accuracy on new questions; review results flatter you because you have seen those questions before.

Traps in KCNA question wording

Most lost points come from reading, not from not knowing. KCNA options are often all true statements about Kubernetes, and only one answers the question as asked. Read the last line first, check for a negative such as "which is NOT", and match the scope: a question about a Pod is not answered by a feature of a Deployment, and a question about a project is not answered by a description of the category it belongs to.

• Component versus object: the scheduler is a component, a Deployment is an object; questions mix them deliberately.
• Concept versus tool: "GitOps" is a practice; Argo CD and Flux are tools that implement it.
• Absolute words: options with "always" or "never" are often wrong in a system with this many configuration choices.
• Two right-sounding options: choose the one that is specifically true for the scenario, not generally true.

Exam day and the readiness test

On the day you have about 90 seconds per question and no documentation at all, because the Linux Foundation allows no resources during multiple-choice exams. Answer what you know on the first pass, flag the rest and come back. Before booking, run a simple readiness test: your accuracy on new questions, not reviews, should sit above 75% in every one of the four domains for a week, and a timed mock should finish with time to spare.

The exam must be taken within 12 months of purchase, a booking can be changed up to 24 hours before the start, and one retake is included if you do not pass. The shared guide on how Linux Foundation multiple-choice exams work covers check-in and the room rules. GoldenKube's KCNA bank has 288 explained questions to run the readiness test on.