Linux Foundation KCNA exam guide covering Kubernetes basics, cloud native tooling, and architecture decisions.
This Kubernetes and Cloud Native Associate guide helps KCNA candidates focus on what the exam tests, where close answers usually split, and which review page to use next.
Use the study plan to group Kubernetes, Linux, and platform choices, the cheat sheet for scenario decisions, the sample questions for mixed practice, the FAQ for scope checks, the resources page for Linux Foundation exam references, and the glossary when cluster terms blur together.
| Item | Guide value |
|---|---|
| Vendor | Linux Foundation / CNCF |
| Exam or credential | Kubernetes and Cloud Native Associate |
| Code or shorthand | KCNA |
| Study level | Associate cloud native |
| IT Mastery page | KCNA exam page |
| Guide shape | Start-here page, study plan, cheat sheet, sample questions, FAQ, resources, and glossary. |
| Lane | What to master | Common weak answer |
|---|---|---|
| Kubernetes fundamentals | Know pods, deployments, services, config, storage, scheduling, controllers, and cluster architecture. | Memorizing object names without understanding what controller reconciles what state. |
| Cloud native architecture | Understand containers, orchestration, microservices, autoscaling, observability, and service discovery. | Calling every container system Kubernetes without recognizing responsibilities. |
| Security basics | Reason about RBAC, namespaces, secrets, network policy, image trust, and least privilege. | Assuming default namespace and broad permissions are harmless. |
| Operations and troubleshooting | Read symptoms through events, logs, readiness, probes, scheduling, service routing, and resource pressure. | Restarting everything without identifying failed layer. |
Kubernetes MCQ pages reward object relationships: desired state, controller, selector, network path, security boundary, and evidence.
Use the current Linux Foundation exam page for live exam details, including name, status, pricing, duration, delivery method, languages, retirement or beta changes, and domain weights where applicable.