Skip to content
beginner Phase 15 · CKA Certification Prep

CKA Exam Overview

Understand the CKA exam format, domains, and preparation strategies.

30m
0 problems
Topic Progress 0%

Exam Format

Exam Format

The Certified Kubernetes Administrator (CKA) is a performance-based exam from the Linux Foundation / CNCF: you perform tasks in a command line against real clusters, not multiple-choice questions. Delivery is proctored online (or at test centers), typically two hours with roughly 15–20 questions, and a cut score commonly around 66%.

Current curriculum weights (memorize these — they drive your study allocation):

Domain Weight
Troubleshooting 30%
Cluster Architecture, Installation & Configuration 25%
Services & Networking 20%
Workloads & Scheduling 15%
Storage 10%

Questions are independently scored: partial completion earns partial credit, and unattempted questions earn nothing — never leave a task blank.

Building Study Momentum

Building Study Momentum

Practice beats reading. The exam allows the Kubernetes documentation, GitHub, and the Kubernetes blog — train by finding answers under time pressure, not memorizing YAML.

Core muscle memory to build:

kubectl explain pod.spec.containers.resources   # fastest YAML recall
kubectl diff -f manifest.yaml                   # preview edits
kubeadm init/join/upgrade                       # cluster lifecycle

The registration bundle typically includes Killer.sh practice environments — use them as full dress rehearsals with a timer. Supplement with a disposable cluster (kind/minikube) where you break things on purpose: CrashLoopBackOff, broken CoreDNS, expired certs, failed upgrades.

Exam-Day Strategy

Exam-Day Strategy

  • Budget time: ~5–6 minutes per question; flag and return rather than sinking twenty minutes
  • Read constraints twice: tasks hide requirements ("do not restart the cluster", "do not modify Y") that fail scoring if violated
  • Start fast, finish deep: bank quick wins (scale, label, cordon) first, save time for troubleshooting
  • Verify everything: run the suggested check (kubectl get, rollout status) after each fix — unconfirmed fixes are risks
  • Context awareness: tasks may share a cluster; destructive actions can break later questions — prefer additive changes
  • Docs search is a skill: know where upgrade, etcd, and NetworkPolicy examples live in kubernetes.io

Interview angle: without the cert, narrating this workflow — explain, diagnose, apply the minimal fix, verify — is how senior Kubernetes questions are evaluated.

Quiz

1. Which domain carries the highest weight on the CKA?

Question 1 options

2. What kind of questions does the CKA contain?

Question 2 options

3. Which resource can you consult during the exam?

Question 3 options

Flashcards

Question

CKA format

Answer

Proctored, terminal-based, ~2 hours, ~15–20 tasks, roughly 66% cut, partial credit per task.

Question

Domain weights

Answer

Troubleshooting 30%, Architecture/Install/Config 25%, Services & Networking 20%, Workloads & Scheduling 15%, Storage 10%.

Question

Allowed exam resources

Answer

Kubernetes documentation, GitHub, Kubernetes blog — train doc-search speed, not memorization.

Question

kubectl explain

Answer

Live field-level YAML reference in the exam — faster and more accurate than recalling structure from memory.

Revision Notes

Key Takeaways

  • 1. Weight study by curriculum: troubleshooting first, then install/config, networking, workloads, storage
  • 2. Practice under time pressure with mock environments and doc-search workflows
  • 3. Exam discipline: budget, flag, verify each fix, and never skip a question

Interview Tips

  • • Describe your diagnostic workflow the same way you would in a real incident — method matters as much as the cert
  • • Use domain weights to explain how you prioritize study — signals structured thinking

Cheat Sheet

CKA: ~2h proctored terminal, ~15–20 tasks, ~66% cut, partial credit. Weights: troubleshoot 30 / install 25 / net 20 / workloads 15 / storage 10. Allowed: k8s docs, GitHub, blog. Budget, flag, verify.

Continue Learning

Before You Start

  • No prerequisites listed.