CKA Study Plan

The CKA is graded on one thing: the state you leave a live cluster in after two hours, not the commands you typed to get there. That should change how you study for it. A plan built around this exam can't be five equal weeks for five equal-looking domains — it has to mirror the exam's own math, where one domain, Troubleshooting, is worth as much as the two smallest domains put together and very nearly a third of the whole score. This page lays out a nine-week plan that puts study time where the exam puts marks: two full weeks on Troubleshooting alone, roughly a week each on the other four domains sized to their weight, and a final week of nothing but timed mock exams and speed drills. Every week points at real pages and labs already on this course — blueprint domains, deep dives, tool guides, and the seven hands-on drills — so none of it is studying in the abstract. Adjust the pace to your calendar; don't adjust the proportions.

The domain-weighted study budget

☺ Like you're 10: The exam doesn't grade every topic equally, so your calendar shouldn't either — a week spent on the biggest domain is worth more than a week spent on the smallest.

These are the five domains and weights exactly as published in the CNCF's Certified Kubernetes Administrator (CKA) Exam Curriculum, version 1.35. There are five, they carry no sub-weights, and they sum to exactly 100% — 30 + 25 + 20 + 15 + 10. (The curriculum PDF prints the 20% domain as "Servicing and Networking"; this course follows the more common phrasing "Services & Networking" for the same domain — see the Troubleshooting blueprint page for the full note.) Treat that shape as a budget, not a checklist: it tells you almost exactly how many of your study hours belong to each domain.

Underneath those five percentages sit 27 published competencies — the individual bullet points the curriculum actually lists, one exam task usually maps to one or two of them. Turning weight and competency count into an hours budget gives a plan you can actually schedule against:

That ~100-hour core doesn't include getting a lab running or sitting mock exams — budget another ~25–30 hours for those, for a full plan of roughly 125–130 hours. Spread across nine weeks that's about 14–15 hours a week, which is a genuine part-time-study pace, not a crash course. Compress the same proportions into five or six weeks if you already run clusters daily; stretch them to twelve if study time is scarce. The ratio between domains is what matters, not the total.

A nine-week roadmap

☺ Like you're 10: Here's the actual calendar — which week you spend on which topic, and exactly which pages on this course to use that week.

Nine weeks, sized to the budget above. D1 gets two weeks because 25% of the exam and eight competencies is genuinely a lot of ground — kubeadm, RBAC, HA control planes, and extension interfaces don't fit in one week without skimming. D5 gets two weeks for the same reason, at the top of the scale. The other three domains get one week each, and the plan opens and closes with weeks that aren't scored domains at all: a foundations week to get a real lab running, and a final week that's entirely timed practice.

What grading on end state changes about how you study

☺ Like you're 10: The exam never sees your reasoning, only the cluster you leave behind — so studying by watching is worth less than studying by typing and checking.

A performance-based exam rewards a specific kind of practice, and it's not re-watching video lessons. Three habits pay off disproportionately, and all three are worth building into every week of this plan, not saving for week 9.

# build these into your fingers this week, not exam week
alias k=kubectl
export do="--dry-run=client -o yaml"     # scaffold real YAML instead of typing it from memory
# e.g.: k create deploy web --image=nginx $do > deploy.yaml   then edit the two lines that need it

# never trust that a fix worked — the exam only grades what's actually true, not what you meant to do
k apply -f deploy.yaml && k rollout status deploy/web
k get pods -o wide                        # confirm Running, not just "no error from apply"

First, type, don't read — every command in this plan's linked pages should be run on your own lab, not just read on the page. Second, verify every claimed fix — a fix you believe you made but never confirmed with kubectl get or describe scores nothing, because grading only sees the end state, exactly as covered in the Troubleshooting blueprint page. Third, practice against a visible clock — a two-hour exam with roughly 15–20 tasks gives you well under ten minutes a task on average, and the only way to know if you're fast enough is to time yourself now, not discover it on the day.

Resources: official, this course, and timed practice

☺ Like you're 10: Three different kinds of resource do three different jobs — don't use a video for the thing only a live cluster can teach you.

Studying "everything you can find" wastes hours; studying the right kind of resource for each stage of the plan doesn't.

Keep a running weak-spot log as you go rather than trusting memory — the Field Notes page on this course is built for exactly that, and rereading it in week 9 is usually faster than re-doing every domain from scratch.

Readiness checkpoint — are you actually ready to book

☺ Like you're 10: Don't book the exam because the calendar says week 9 — book it once you can actually do these things, cold, under a clock.

Booking on a date rather than on readiness is the single most common way people waste the exam fee. Before you pay, you should be able to answer "yes" to all of these without hesitating:

If more than one or two of those still feels shaky, that's not a reason to panic — it's a precise list of what to re-run before you spend the fee. Loop back to the matching week above, not to the whole plan.

Exam logistics — verify these yourself before you pay

☺ Like you're 10: The shape of the test changes now and then — read the official page before you hand over any money.

The details below are what the Linux Foundation and CNCF publish and what candidates consistently report. They're here to help you plan a calendar, not to be quoted back at anyone.