About the exam
KCNA Exam structure
KCNA prep with 601 individually authored practice questions, 100 flashcards, CNCF-domain weighted mocks, Kubernetes and cloud-native topic drills, and detailed answer rationales.
Issuer and path
Kubernetes and Cloud Native Associate Exam Prep is administered through Linux Foundation / CNCF. Check official resources before booking, retesting, or relying on a stale requirement.
Kubernetes Fundamentals
44 scored + 0 pretest
Kubernetes core concepts, administration basics, scheduling, containerization, Pods, nodes, namespaces, clusters, and control plane responsibilities.
Container Orchestration
28 scored + 0 pretest
Networking, security, troubleshooting, storage, runtimes, service discovery, workload health, and Kubernetes orchestration behavior.
Cloud Native Application Delivery
16 scored + 0 pretest
Application delivery, CI/CD, GitOps concepts, debugging, releases, container images, rollouts, rollbacks, and health validation.
Cloud Native Architecture
12 scored + 0 pretest
Observability, telemetry, cloud native ecosystem principles, CNCF community, collaboration, microservices, and architectural tradeoffs.
Before you schedule
KCNA is currently a 60-question, 90-minute, closed-book remote-proctored exam with a 75% passing score. Verify identity requirements, system checks, scheduling windows, retake terms, and policy updates in your Linux Foundation candidate portal before exam day.
Official Outline Coverage Map
Coverage is mapped to official outline item counts so content depth can be checked without hard-coding a single exam.
| Topic | Official outline items | Your questions | Your flashcards | Confidence |
|---|---|---|---|---|
| Kubernetes Core Concepts, Pods, Nodes and Control Plane | 15 | 89 | 10 | Priority |
| Administration, API Objects, Labels and Namespaces | 15 | 88 | 10 | Strong |
| Scheduling, Containerization and Workload Basics | 14 | 88 | 10 | Strong |
| Networking, Services and Discovery | 10 | 56 | 10 | Priority |
| Security, Troubleshooting and Health | 9 | 56 | 10 | Priority |
| Storage, Runtimes and Orchestration Behavior | 9 | 56 | 10 | Good |
| CI/CD, GitOps and Release Flow | 8 | 48 | 10 | Strong |
| Debugging Delivery and Runtime Health | 8 | 48 | 10 | Strong |
| Observability, Telemetry and CNCF Ecosystem | 6 | 36 | 10 | Strong |
| Cloud Native Principles, Community and Architecture | 6 | 36 | 10 | Good |
How to use this guide
How to study for Kubernetes and Cloud Native Associate
Treat each question as a foundation check: identify the Kubernetes primitive, connect it to the cloud native pattern, then choose the least surprising operational behavior.
1. Identify the primitive
Decide whether the question is about a Pod, node, Service, controller, namespace, volume, policy, delivery step, or ecosystem tool.
2. Check the responsibility
Match the behavior to the correct Kubernetes component, cloud native pattern, or delivery responsibility.
3. Remove overreach
Eliminate answers that jump to destructive fixes, skip desired state, or confuse adjacent resources.
4. Choose the stable concept
Prefer the answer that explains durable platform behavior over a one-off command or vendor-specific shortcut.
Kubernetes Core Concepts, Pods, Nodes and Control Plane
KCNA fundamentals start with what Pods, nodes, clusters, namespaces, the API server, scheduler, controllers, kubelet, and etcd each do.
Key rules
Rule 1
Kubernetes records desired state through the API and relies on independent control loops to move observed state toward it.
Exam cue: Ask whether the behavior belongs to the API server, scheduler, a controller, kubelet, etcd, or the runtime.
Rule 2
The control plane makes cluster-wide decisions, while kubelet and the container runtime realize assigned Pods on each Node.
Exam cue: Separate Pod-level container restart from a controller creating an entirely new Pod.
Rule 3
Pods are replaceable workload instances; stable discovery, durable storage, and higher-level controllers live in separate abstractions.
Exam cue: Use spec for desired configuration and status or conditions for observed state.
Common traps
Treating a Pod as a durable machine with a permanent identity or IP address.
Prevention: Avoid answers that rely only on habit, ignore the stated source, skip safety or compliance steps, or choose convenience over the professional standard.
Assuming a Namespace automatically provides network isolation, encryption, or a separate physical cluster.
Prevention: Avoid answers that rely only on habit, ignore the stated source, skip safety or compliance steps, or choose convenience over the professional standard.
Confusing API persistence in etcd with container execution or application data storage.
Prevention: Avoid answers that rely only on habit, ignore the stated source, skip safety or compliance steps, or choose convenience over the professional standard.
Memory anchors
Pod
A Pod is the smallest deployable Kubernetes unit and wraps one or more tightly coupled containers.
Node
A node is a worker machine that runs Pods through kubelet and a container runtime.
Cluster
A cluster combines control plane components and worker nodes into one Kubernetes environment.
Namespace
A namespace scopes names, policies, quotas, and access boundaries inside a cluster.
API Server
The API server is the front door for Kubernetes object requests and validation.
Scheduler
The scheduler assigns unscheduled Pods to suitable nodes based on constraints and available resources.
Controller Manager
Controllers watch desired state and reconcile actual cluster state toward that desired state.
Etcd
etcd stores Kubernetes cluster state and must be protected because it is the source of truth.
Kubelet
Kubelet is the node agent that reconciles assigned PodSpecs through the container runtime.
Reconciliation
Reconciliation repeatedly compares desired and observed state and acts to reduce the difference.
Next best moves
Quick check-up
Use a short quiz to confirm the rule pattern is actually sticking.
Check-up Questions
A web application needs two tightly coupled containers that must share one IP address and communicate over localhost. Which Kubernetes unit should contain them?
Which control-plane component exposes the Kubernetes API used by kubectl, controllers, and node components?
Answer all questions to submit.
Next step personalized recommendations
Open another topic next
Official resources
Verify the details with the official sources
Use these links for eligibility, scheduling, handbook rules, and issuer updates. Our guide helps you study; official sources tell you what the testing partner currently requires.
Kubernetes and Cloud Native Associate (KCNA)
Official CNCF KCNA page with program description, online multiple-choice format, public domains, weights, and resources.
KCNA Linux Foundation certification page
Linux Foundation KCNA page with domains, competencies, exam duration, prerequisites, and exam resources.
Official KCNA Curriculum
The current CNCF curriculum PDF with the four domains, weights, and detailed competency areas.
Linux Foundation multiple-choice exam instructions
Official instructions covering question count, exam duration, proctoring, and exam-day requirements.
Linux Foundation multiple-choice exam FAQ
Official FAQ covering the passing score, results, credential validity, retake policy, and remote-proctoring details.
Linux Foundation allowed resources
Official policy explaining that external resources are not allowed during multiple-choice certification exams.
Kubernetes Documentation
Official Kubernetes documentation for core concepts, workloads, Services, configuration, networking, storage, and security.
CNCF Landscape
CNCF landscape for understanding the broader ecosystem around Kubernetes, observability, service mesh, registries, runtimes, and delivery tools.
FAQ
Common KCNA questions
Is this the official KCNA exam?
No. These are original practice questions aligned to public CNCF and Linux Foundation KCNA domains. They are not copied from secure exam items.
What does KCNA measure?
KCNA measures foundational Kubernetes and cloud native knowledge, including core concepts, orchestration, application delivery, architecture, observability, and ecosystem awareness.
How many questions are on KCNA, and how long is the exam?
The current Linux Foundation multiple-choice exam instructions list 60 questions and a 90-minute exam duration for KCNA.
What score do I need to pass KCNA?
Linux Foundation currently lists 75% as the passing score for its multiple-choice certification exams, including KCNA.
Can I use Kubernetes documentation during KCNA?
No. KCNA is a closed-book multiple-choice exam, and Linux Foundation's allowed-resources policy does not permit external sites or tools during this exam format.
Do I need Kubernetes experience before KCNA?
Linux Foundation lists no prerequisites, but candidates should be comfortable with Pods, nodes, clusters, namespaces, control plane concepts, Services, Deployments, storage, networking, and basic security.
How is the mock weighted?
The 60-question mock follows the public 44/28/16/12 KCNA domain split.
Does the KCNA purchase include a retake?
Under the current Linux Foundation policy, the purchase includes one exam attempt and one retake. Verify the current terms in your candidate portal before scheduling.
How long is the KCNA credential valid?
Linux Foundation currently lists the KCNA credential as valid for two years after a passing result.
How should I use the 601 questions?
Start with Kubernetes Fundamentals because it is the largest domain, then rotate through orchestration, delivery, and architecture while keeping terminology precise.