What should you memorize and what should you learn?
Memorize the shape of commands, not every flag. kubectl is the command line tool that talks to your cluster. You should reach for the right subcommand without thinking, and flags like -n for namespace, -o yaml for output, and --selector should feel automatic.
Facts to memorize before exam day
- The four service types and what each one does
- What a readiness probe and a liveness probe each control
- The difference between a Deployment, a ReplicaSet, and a StatefulSet
- How a role and a role binding fit together
Skills to build with your own hands
- Run a deployment with a rolling update and then roll it back
- Create a persistent volume claim and bind it to a workload
- Expose the same app as ClusterIP, NodePort, and LoadBalancer
- Set a resource limit and a network policy on a namespace
You do not need to memorise a Deployment manifest. You need to know what each field does. That is the line between reading Kubernetes docs and running a cluster.
Managed services change some answers. If your job uses Amazon EKS, Azure AKS, or Google GKE, read EKS vs AKS vs GKE managed Kubernetes compared. Some tasks will ask you to read cloud resources instead of raw nodes.
How do you practice in the same environment as the real exam?
The Linux Foundation bundles a simulator with the CKA. It runs through Killer.sh and it is the closest thing to exam day you can get at home. The Linux Foundation CKA page says you get two simulation attempts, that each session holds 17 questions, and that you get a different set of questions each time. You also get 36 hours of access for each attempt, and the simulator returns a graded score.
Two sessions is not many, so save them. Take the first one at the end of week four. Write down every task where you went over seven minutes and every task you could not finish. Any cka study guide that skips the simulator is guessing at the clock.
For everything else, build a local cluster. The official Kubernetes documentation has a setup page for each common local tool. Make sure you can destroy and rebuild it in under five minutes, because many troubleshooting tasks begin from a broken state.
Do not memorise answers to old practice questions. The exam draws fresh tasks each time, so learning the shape of a task beats recalling one fix.
What does a week by week cka study plan look like?
Six weeks works if you touch the cluster most days. If you only have four, cut weeks one and four and keep the rest. Treat the table below as the backbone of any cka study guide you buy.
| Week | Focus | Lab target |
| Week 1 | Cluster setup and cluster architecture | Build a cluster with kubeadm, add a worker node, and read the control plane pod logs |
| Week 2 | Workloads and scheduling | Deploy, scale, roll out a new version, and roll back using only working commands |
| Week 3 | Services, networking, and storage | Expose three service types, write one Ingress rule, and bind one claim to one volume |
| Week 4 | Troubleshooting drill and first simulator | Break a cluster on purpose ten times and fix it ten times, then sit the simulator |
| Week 5 | Weak domains and speed work | Every task under six minutes, with one full simulator session held in reserve |
| Week 6 | Final mock and exam day logistics | One full mock on the real PSI system check, plus a run through of the exam day checklist |
Keep a lab notebook and write down every error you hit with the command that fixed it. Troubleshooting rewards pattern matching, and a notebook is how you build patterns fast.
What do you need to pass and what happens if you fail?
The Linux Foundation candidate FAQ says a CKA score of 66 percent or above is a pass. The same FAQ says the exam is scored automatically and your report arrives by email within 24 hours of finishing.
You do not have to pay for a second try. The Linux Foundation CKA page says your purchase gives you 12 months to schedule and take the exam, plus two exam attempts. Fees, bundles, and discounts move around, so read our CKA exam cost 2026 price breakdown before you buy anything.
Two attempts inside 12 months is plenty if you take the first one honestly. Do not spend both in your first week. Run the simulator, then book.
One last piece of career context. Teams that ship fast often blur the line between building and running software. The difference between Agile and DevOps in 2026 shows where the CKA sits in that picture. If you already run clusters for a living, our Kubernetes cluster cost optimization 2026 guide covers the money side of the job that the exam never tests.