Linux Foundation CKA cheat sheet for cluster ops, networking, storage, traps, and final review.
Use this cheat sheet for Certified Kubernetes Administrator (CKA) after you know the basics but before you start a timed practice block. The goal is not to memorize a vendor catalog; the goal is to classify the scenario and reject attractive wrong answers quickly.
For performance-based exams, treat this as a command-and-task triage sheet. It helps decide what to do first, but it does not replace live lab repetition.
Use this when the stem mixes manifest creation, troubleshooting, services, storage, or security.
flowchart TD
S["Scenario"] --> O["Name the object or control plane lane"]
O --> T["Check rollout, service, or storage behavior"]
T --> S2["Check selectors, ports, and resources"]
S2 --> V["Verify with status, logs, or events"]
| Lane | Decision rule | Reject when |
|---|---|---|
| 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. |
| Trap | Better instinct |
|---|---|
| Reading-only prep | Use MCQ review for concepts, but rehearse commands and manifests in a real cluster. |
| Wrong context or namespace | Check context and namespace before every change. |
| Fixing the wrong object | Trace deployment to pod to service to endpoint to ingress before editing. |
| No verification | After a change, prove readiness, endpoints, logs, rollout, or connectivity. |
| If the stem says | Start with |
|---|---|
| least privilege, private access, compliance, or audit | identity scope, data boundary, policy enforcement, logging, and ownership |
| least operational effort | managed service, native integration, simple workflow, and fewer moving parts |
| high availability, recovery, or outage | failure domain, recovery objective, health check, rollback, and validation |
| performance, scale, or cost | bottleneck evidence, traffic pattern, sizing, caching, batching, and quotas |
| troubleshoot, diagnose, or investigate | symptom, recent change, logs, metrics, status, dependency, and smallest safe test |
Use IT Mastery for objective recognition and scenario drills, then validate speed in the real performance environment.
Open the exact IT Mastery route here: CKA on MasteryExamPrep.
Performance-based Kubernetes pages require hands-on practice. Use the cheat sheet for decision order, then prove every skill in a live lab.