KCNA Study Guide: Cloud Native Associate

What the KCNA exam is

KCNA (Kubernetes and Cloud Native Associate) is an entry-level certification from CNCF and The Linux Foundation. Unlike the hands-on CKA and CKAD exams, KCNA is a multiple-choice, knowledge-level test. You are proving that you understand how Kubernetes and the broader cloud native landscape fit together, not that you can debug a live cluster under pressure. That makes it an excellent first step before the performance-based certifications.

This is independent study material. Skills Tech Certified is not affiliated with, endorsed by, or sponsored by CNCF or The Linux Foundation. Confirm the current curriculum and exam format on their official sites before booking.

Who it is for

KCNA suits developers, operations and platform engineers, students, and anyone moving into cloud native roles who wants a credible foundation. No formal prerequisites exist, but comfort with the command line and basic container ideas will make the material land faster. If you have run a container locally, you have already started.

The domains you must know

• Kubernetes fundamentals: the API and API server, core objects (Pods, Deployments, Services, ConfigMaps, Secrets, Namespaces), the control plane (scheduler, controller manager, etcd) versus the worker nodes (kubelet, kube-proxy, container runtime), and what happens when you apply a manifest.
• Container orchestration: how the scheduler places workloads, networking basics (the Pod network model, Services, Ingress, DNS), storage (volumes, persistent volumes and claims, the CSI idea), and security surfaces (RBAC, service accounts, the principle of least privilege).
• Cloud native application delivery: building and shipping with CI/CD, the declarative approach, and GitOps where Git is the source of truth and tools reconcile the cluster to match it.
• Cloud native architecture: autoscaling and serverless, observability (metrics, logs, traces), open standards, and the role of the CNCF community, its project maturity levels, and the wider ecosystem.

How to prepare

Even though the exam is not hands-on, a little practice cements the vocabulary. Spin up a local cluster with kind or minikube, then create a Deployment, expose it with a Service, and inspect objects using kubectl get and kubectl describe. Read a few real manifests and name every field. For the cloud native breadth, browse the CNCF landscape and note which project solves observability, which handles service mesh, and which does GitOps, so the categories are second nature.

How long it takes

Newcomers usually need three to five weeks, roughly 25 to 40 hours, especially if containers are new. If you already work with Kubernetes, a focused week or two of review across the four domains is often enough. Because the breadth is wide but shallow, steady daily study beats cramming.

How to know you are ready

You are ready when you can sketch the control plane and worker components from memory, explain how a Pod gets scheduled and reaches the network, describe GitOps in a sentence, and place common CNCF tools into their categories. If you can walk a colleague through the journey of a manifest from kubectl apply to a running Pod, the exam will feel approachable. A quick check of where you stand across all four domains will show which topics deserve your final review.