Linux Foundation CKAD exam guide covering Kubernetes application design, manifests, and deployment decisions.
This Certified Kubernetes Application Developer guide helps CKAD candidates focus on what the exam tests, where close answers usually split, and which review page to use next.
This route is performance-based. Use the guide for concept readiness and objective triage, but plan hands-on app-deployment practice before scheduling.
| Item | Guide value |
|---|---|
| Vendor | Linux Foundation / CNCF |
| Exam or credential | Certified Kubernetes Application Developer |
| Code or shorthand | CKAD |
| Study level | Performance-based Kubernetes development |
| IT Mastery page | CKAD exam page |
| Guide shape | Start-here page, study plan, cheat sheet, FAQ, resources, and glossary. |
| Lane | What to master | Common weak answer |
|---|---|---|
| Resource creation and editing | Create, inspect, patch, and apply Kubernetes objects quickly and safely. | Knowing concepts but not being able to produce valid manifests under time pressure. |
| Troubleshooting flow | Use describe, logs, events, endpoints, rollout status, exec, and resource metrics to isolate the failed layer. | Guessing fixes without observing pod, service, scheduler, or network evidence. |
| Networking and services | Validate labels, selectors, ports, endpoints, ingress, DNS, and network policy. | Changing deployments when the service selector or target port is wrong. |
| Storage and scheduling | Reason about PVCs, storage classes, node selectors, affinity, taints, tolerations, and resource requests. | Ignoring scheduler events and volume binding conditions. |
| Security and operations | Apply RBAC, contexts, service accounts, secrets, upgrades, backups, and maintenance workflows. | Using cluster-admin or unsafe shortcuts without understanding scope. |
Performance-based Kubernetes application pages require hands-on practice. Use the cheat sheet for decision order, then prove every skill in a live lab.
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.