7 Rules for Passing the CKA Kubernetes Exam on v1.35

Effective CKA Kubernetes exam preparation is a scheduling problem as much as a knowledge problem. You pass by weighting study time to the official domain weights, drilling hands-on tasks on a live cluster until kubectl feels like muscle memory, and rehearsing under real exam conditions with only the allowed documentation. The exam itself is an online, proctored, performance-based test that gives you 2 hours to solve hands-on tasks from a command line running Kubernetes, and the current version is based on Kubernetes v1.35. There are no multiple-choice questions anywhere on the test.

Scoring rewards completeness over perfection. The Linux Foundation requires a score of 66% or above to pass, and tasks are graded on the state your cluster is left in, not on the commands you typed along the way. That combination of a generous threshold with binary task scoring means the winning strategy is to attempt everything, flag the hardest tasks, and circle back to them with whatever time remains. The seven rules below map directly to how the exam is built.

What the CKA Actually Tests

The Certified Kubernetes Administrator credential, created by the Linux Foundation together with the Cloud Native Computing Foundation, validates that you can operate a cluster: install it, configure it, network it, store data in it, and repair it when it breaks. The curriculum is public, versioned to track Kubernetes releases, and organized into five weighted domains.

Troubleshooting alone carries 30% of the score, followed by cluster architecture, installation and configuration at 25% and services and networking at 20%. Together those three domains are 75% of the exam, which is exactly where your calendar should go. The exam-only registration lists at $445 on the Linux Foundation portal, with bundles available that add the LFS258 course or the THRIVE-ONE subscription if you want structured training alongside it.

Weight Study to Domain Weights

Most failed attempts come from flat, unweighted study: reading documentation cover to cover and treating every topic as equal. Build your plan as an ordered procedure instead:

1. Allocate roughly a third of all study hours to troubleshooting drills on deliberately broken clusters.
2. Give cluster architecture and installation the second-largest block, with repeated kubeadm build-and-tear cycles on two or more virtual machines.
3. Reserve dedicated blocks for networking and workloads, in that order.
4. Cover storage last but completely; it is the smallest domain, yet its tasks are among the fastest points on the exam.
5. Close every study block with a timed task, because the exam measures speed as much as knowledge.

A eight-to-ten week cadence at ten hours per week is enough for candidates who already administer Linux systems; newcomers to containers should add four weeks of foundations before starting the clock.

Drill on Kubernetes v1.35

Because grading inspects the final cluster state, practice producing correct end states quickly rather than memorizing theory. Stand up disposable clusters with kubeadm, kind or Minikube at the exam’s version and rehearse the mechanics you will actually use: imperative kubectl commands for one-off objects, YAML manifests saved and reapplied for anything you might need to correct, and fast switching between kubeconfig contexts with kubectl config use-context before every task. Configure vim or your preferred editor once, in your shell profile, on day one, because fighting the editor is a real time loss with roughly fifteen to twenty tasks in two hours. Time-box every practice task to about six minutes; that is the sustainable per-task budget the format imposes.

Master the Allowed Documentation

The exam is not closed book, but the open part is narrow. During the exam, the browser inside the exam VM can only reach task-specific documentation provided in the Quick Reference box, plus the Gateway API documentation for CKA candidates. Nothing else on the internet is reachable, so treat documentation navigation as a scored skill: learn where the kubectl cheat sheet, NetworkPolicy examples, StorageClass examples and kubeadm upgrade guides live inside the allowed set, and practice finding copy-paste-ready YAML with browser search before exam day rather than writing manifests from scratch under pressure.

Use Both Killer.sh Attempts

Registration is more than a single sitting. Your registration includes 12 months to schedule and take the exam, two exam attempts, and two simulator sessions, so budget the calendar deliberately: take the first simulation roughly three weeks out as a diagnostic, and hold the second for the final week as a dress rehearsal. Each simulator session opens a 36-hour access window from activation and serves 17 questions that are calibrated to feel harder than the real exam; a comfortable pass there is the most reliable readiness signal available. Also prepare the environment itself: one monitor only, a private room, government-issued photo ID, and a machine you are allowed to install the PSI Secure Browser on, because technical friction at check-in burns minutes you will want back.

Know When to Skip CKA

The CKA has no formal prerequisites, but it is an intermediate-to-advanced credential, and sitting it before you are ready mostly burns a retake. If your background is in security rather than operations, an entry credential may be the better first step: our comparison of Security+ versus Pentest+ and which to take first maps the decision, and the CEH eligibility and path requirements matter because that exam gates on documented experience. Come back to the CKA once you can bootstrap a cluster unaided; every hour of prior hands-on time compounds into exam-day speed.

Sources

• Linux Foundation — Certified Kubernetes Administrator (CKA) official page
• Linux Foundation Candidate Docs — CKA, CKAD and CKS FAQ
• Linux Foundation Candidate Docs — Resources Allowed During Certification Exams