How the CKA exam works

The format, the grading, the proctored environment, what you may open, how results and retakes work, and two study plans that map this course onto the five domains.

Foundations25 min1 task

After this lesson

  • 01You can describe the exam format, the pass mark and what the grader actually checks.
  • 02You can list what is allowed in the exam environment and what will get a session flagged.
  • 03You can pick a study plan and say which modules you will finish in which week.

The CKA is a two-hour, hands-on exam on live clusters. Nobody fails it for not knowing what a Pod is; people fail it on time, on reading, and on surprises in the environment. This lesson removes the surprises. Every number below was checked against the Linux Foundation exam page and candidate handbook on the date in the file header; where the official pages are silent, this lesson says so instead of guessing.

The format and the grading

  • Performance-based. 15 to 20 tasks solved in a terminal against real clusters. No multiple choice.
  • 2 hours. The clock starts after the short interface tour, shows alerts at 30, 15 and 5 minutes, and never pauses: not for a break, not for a disconnect.
  • Pass mark 66%. Each task shows its weight in percent. Your score is the weight you earned out of the total.
  • Scored automatically, on end state. The handbook says any path that produces the correct result is acceptable. The grader reads the objects in the cluster and the files you wrote; it cannot see which commands you typed, whether you used vim or kubectl edit, or how many times you got it wrong before you got it right.
  • Partial credit is not described in the official documentation. Work as if only the checks you complete count: a task half done may be worth nothing, so finish what you start or flag it and come back.
  • Kubernetes v1.37 is the exam version at the time of writing. The environment tracks the latest minor release within four to eight weeks of it shipping, so check the official page the week you book.
  • Languages: English, Simplified Chinese and Japanese for the questions. The terminal and the proctor chat stay in English.

The exam environment

The exam is proctored remotely through PSI's Bridge platform. At launch you install the PSI Secure Browser (Chrome-based), which checks for a second monitor and other disallowed software, and then shows a Linux remote desktop. On that desktop you get a terminal emulator, a Firefox window reserved for the allowed documentation, VSCodium (extensions disabled) and a virtual keyboard. Everything happens inside that one desktop: your own terminal, your own browser and your own notes are out. Each task opens with an infobox telling you which host to ssh into. You start on a base host that has no tools; the task hosts have kubectl with the k alias and bash completion already set up, plus yq, curl, wget and man pages. sudo -i gives you root. When a task is done, exit back to base before starting the next one; nested ssh is not supported, and you must never reboot the base host. The official instructions do not publish how many clusters there are. Expect more than one and treat the infobox as part of the question.

AllowedNot allowed
kubernetes.io/docs, including its search box and translationsOpening search results that lead outside the allowed sites
kubernetes.io/blogAny other website, including forums and GitHub
helm.sh/docsNotes, books, a second screen, a phone or smart watch
gateway-api.sigs.k8s.io (CKA only)Headphones or earbuds, unless medically necessary
Links in the Quick Reference box of a task, and man pages on the hostReading questions aloud, leaving the camera view without permission
Clear water in a label-free bottle or glassEating, chewing gum, anyone else in the room

Results, retakes, validity and scheduling

  • Results: the score report is emailed within 24 hours of finishing, barring exceptions, and also appears in My Portal. The Linux Foundation does not report how you did on individual tasks. The formal certificate notice follows within three business days and a Credly digital badge is issued to everyone who passes.
  • Retake: one retake is listed with the registration. You claim it from the Exam Preparation Checklist after a No Pass, and it must be used inside your eligibility window. A no-show forfeits the fee and the retake.
  • Validity: 2 years from the pass date. Renewing means passing the exam again before it expires.
  • Scheduling: 12 months from registration to schedule and sit the exam. Slots open up to 90 days ahead with a 24-hour lead; you can reschedule or cancel up to 24 hours before the start, not later.
  • Launch window: the Take Exam button activates 30 minutes before your slot; start more than 30 minutes late and you are a no-show.
  • Simulator: standard registrations include two 36-hour sessions of the Killer.sh simulator. The exam-only SINGLE products do not.
  • Price: changes with promotions and bundles; see the official page for current pricing.

The five domains and where this course covers them

DomainWeightModule in this course
Troubleshooting30%Module 5: method, application, control plane, nodes, services and DNS, logs, metrics, kubectl debug
Cluster Architecture, Installation & Configuration25%Module 1: components, kubeadm, upgrades, etcd, HA, certificates, RBAC, Helm, Kustomize, CRDs, CNI/CSI/CRI
Services & Networking20%Module 3: pod networking, Services, CoreDNS, Ingress, Gateway API, NetworkPolicies
Workloads & Scheduling15%Module 2: Pods, Deployments, config, resources, scheduling, controllers, probes, HPA, admission
Storage10%Module 4: volumes, PV and PVC, StorageClasses, StatefulSets

How the readiness meter on /cka works. Every task in this course belongs to one domain. For each domain the meter takes the share of that domain's tasks you have verified with a passing script, multiplies it by the domain's exam weight, and adds the five together. Verifying every troubleshooting task moves the needle by 30 points; every storage task by 10. The weights are the exam's, so the meter also tells you where an hour of study is worth most. Tasks in this foundations module count toward the domain they practice. The plans below are sized for the whole course: 40 lessons, a lightning lab and two mocks.

4 weeks, about 1.5 h per dayModules
Week 1Module 0 (all four lessons, lab built); Module 1 lessons 1 to 6: components through certificates
Week 2Module 1 lessons 7 to 11: RBAC, Helm, Kustomize, CRDs, extension interfaces; Module 2 (all nine)
Week 3Module 3 (all six); Module 4 (all four); Module 5 lessons 1 to 4
Week 4Module 5 lessons 5 to 8; lightning lab; Mock 1; re-run the weakest domain by the meter; Mock 2; cheat sheet and final checklist
8 weeks, about 45 min per dayModules
Week 1Module 0: exam format, lab, kubectl fluency, exam-day habits
Week 2Module 1 lessons 1 to 6: components, kubeadm install, upgrades, etcd, HA, certificates
Week 3Module 1 lessons 7 to 11: RBAC, Helm, Kustomize, CRDs, CNI/CSI/CRI
Week 4Module 2: all nine workloads and scheduling lessons
Week 5Module 3: all six networking lessons
Week 6Module 4: storage; Module 5 lessons 1 to 3
Week 7Module 5 lessons 4 to 8; lightning lab
Week 8Mock 1; revisit the weakest domain; Mock 2; cheat sheet; final checklist

In the docs · the tab you get on exam day

Taskfd-exam-1
Architecture2%~2 min

context · kubectl config use-context kind-cka

Write the domain weights to a file

Write the five CKA exam domains and their weights to /tmp/cka/domains.txt, one per line, in the form domain=weight. Use the lowercase single-word domain names this course uses: troubleshooting, architecture, networking, workloads, storage. Example line: troubleshooting=30. The file must contain exactly those five lines and nothing else.
  1. 01

    Set up the scenario

    curl -fsSL https://codewithmuh.com/labs/cka/t/fd-exam-1/setup | bash
  2. 02

    Solve it in your terminal

    Work the way the exam makes you: kubectl, the docs, nothing else. Put any answer files under /tmp/cka/.

  3. 03

    Check your work

    curl -fsSL https://codewithmuh.com/labs/cka/t/fd-exam-1/verify | bash
    Counts toward your readiness score.
  4. 04

    Clean up

    curl -fsSL https://codewithmuh.com/labs/cka/t/fd-exam-1/cleanup | bash

Finished reading?

0 of 1 tasks passed. Readiness counts tasks, so run them before you move on.