KCNA study plan: breadth over depth, on purpose
A sensible KCNA study plan has four phases: get a cluster running so the vocabulary has something to attach to, study the four domains with Kubernetes fundamentals taking the lion's share, broaden across the cloud-native landscape, then rehearse with timed mocks. KCNA is multiple choice rather than hands-on, and its weightings are lopsided — one domain is worth more than the other three combined — so an evenly-distributed study schedule wastes your time.
KCNA is not a small CKA
The most useful thing to understand before you start is that KCNA and the CKA are different kinds of exam, not two difficulties of the same one. The CKA is a hands-on performance test in a live terminal. KCNA is multiple choice, taken in a browser, testing whether you understand what the pieces are and how they fit together.
This does not make it trivial, but it does change the preparation. You are building a broad conceptual map of Kubernetes and the surrounding cloud-native ecosystem rather than muscle memory for kubectl. Study material aimed at the CKA will over-prepare you on operations and under-prepare you on the architecture, delivery and observability material that KCNA also covers.
Phase 1 — Get a cluster and orient (a few days)
Run a cluster locally — a single-node distribution on your laptop is enough — and deploy something to it. You are not practising for a practical exam, but the abstractions are much easier to hold onto once you have watched a pod get scheduled, a deployment roll out and a service route traffic.
Then read the four domain weightings and let them shock you into a sensible plan: Kubernetes fundamentals dominates, container orchestration is a clear second, and application delivery and architecture share what is left. Answer a short practice session cold to see where you stand.
Phase 2 — Study in weight order (the bulk of the plan)
Kubernetes fundamentals is where the marks are, and it means both the architecture — control-plane components, the API server, etcd, the scheduler, controllers, kubelet — and the core objects you would meet in a first week: pods, deployments, services, config maps and secrets, namespaces. You should be able to say what each component does and what breaks if it stops.
Container orchestration comes next and is broader than it sounds: networking and the container network interface, storage and its interface, security and role-based access control, scheduling and resource management, and the runtime layer beneath Kubernetes itself. The remaining two domains — application delivery and cloud-native architecture — cover the ecosystem around Kubernetes, and they are where candidates from an operations background usually have the biggest gaps.
- Kubernetes fundamentals: the control-plane and node components, the API and its objects, and the declarative model.
- Container orchestration: networking, storage, security, scheduling and the container runtime interfaces.
- Cloud-native application delivery: GitOps, continuous delivery patterns, and how applications get from a repository to a cluster.
- Cloud-native architecture: autoscaling, serverless, observability, service meshes, and the CNCF project landscape and its maturity levels.
Phase 3 — Broaden across the landscape (about a week)
The domains outside Kubernetes fundamentals are essentially a vocabulary test over the cloud-native ecosystem. You need to know what the major projects are for — what a service mesh solves, what Prometheus and OpenTelemetry each do, what GitOps means in practice, what the CNCF graduation levels signify — rather than how to operate any of them.
This is genuinely different work from the first two domains and deserves its own phase. Rebuild practice sessions from your incorrect and flagged questions, and pay particular attention to any project name you can recognise but not explain: that is exactly the gap the exam is designed to find.
Phase 4 — Mock week: rehearse, then book
Sit full-length timed mocks under real conditions. KCNA is not a long exam and most candidates finish comfortably, so the thing being rehearsed is coverage rather than pacing — you are checking that no domain has been quietly neglected.
Between mocks, work the incorrect answers. Book once you are clearing the pass mark consistently across consecutive mocks, and keep the daily practice habit until the day.
Signals you are ready
Book the exam when all of these are true:
- Consecutive full-length mocks above the pass mark, across different question draws.
- You can name each control-plane component and say what fails without it.
- You can explain what each major CNCF project in the syllabus is for, in a sentence, without looking it up.
- The two lighter domains are not dragging — they are small, so gaps there are cheap to close and expensive to ignore.