KCA
More study resources
Cheat sheet
Keep the key ideas within reach.
ExploreKey terms
Get comfortable with the vocabulary.
ExploreStudy plan
Give each week a clear focus.
ExploreCommon mistakes
Understand the traps and how to avoid them.
ExploreCase studies
Put your knowledge to work in context.
ExploreExam-day guide
Prepare for the day ahead.
ExploreAbout this exam
The KCA is a hands-on certification for Kubernetes practitioners who want independent, third-party evidence of their ability to operate clusters day to day. It suits platform engineers, DevOps and SRE staff, and developers who already deploy workloads and now need to prove they can install, secure, network, and repair a cluster under time pressure. The published blueprint splits the exam into six domains: core concepts (25%), installation, configuration and validation (15%), security (20%), networking (15%), troubleshooting (15%), and workloads and scheduling (10%). Questions are multiple choice, but the weighting signals where depth pays off: core objects and security together account for nearly half the score, so kubectl fluency with Pods, Deployments, Services, RBAC, and Secrets matters more than trivia. Prepare by building a small cluster (kind, minikube, or k3s), then deliberately breaking it: misconfigure a Service selector, remove a kubelet certificate, exhaust a node, and practise reading events, logs, and describe output to diagnose each fault. Work through each domain against the official Kubernetes documentation, which is the reference candidates can use during the exam, and time yourself on practice sets so recall becomes fast. Confirm current exam logistics, including the number of questions, duration, passing score, fee, and retake rules, on the certifying body's official site before booking, since those details change. This page is an independent study resource and is not affiliated with or endorsed by the certification body.
What you'll study
About KCA preparation
What is the exam format?
The KCA is delivered as multiple-choice questions, so there is no live cluster to operate. Expect scenario-style items that describe a manifest, command, or failure and ask for the correct outcome or next step. The certifying body publishes the current question count and time limit on its official site.
How difficult is the KCA?
Most candidates find it moderate: the questions reward people who have actually built and broken clusters rather than memorized flags. Core concepts and security carry the most weight, so weak spots there hurt most. If you can explain why a Pod is Pending and fix it without looking it up, you are close to ready.
How long should I study, and in what order?
A common plan is six to ten weeks part-time: start with core concepts, then workloads and scheduling, then networking, then security, then installation and validation, finishing with troubleshooting as a synthesis of everything. Practise on a real cluster throughout; reading alone rarely builds the diagnostic instincts the exam rewards.
Can I retake the exam if I fail?
Retake rules, waiting periods, and any fees are set by the certifying organization and can change. Check the official certification page for the current policy before you book, and note whether a retake is bundled with your initial purchase.
How much does the exam cost, and how long is it valid?
Fees and certificate validity are published by the certifying body and are not fixed here. Visit the official site for the current price, any regional variation, and the validity period, which determines when you would need to recertify.
What are the most common failure modes?
Candidates typically lose points on security specifics (RBAC verbs and resources, ServiceAccount token behavior, Secret handling), on networking details (Service types, DNS names, NetworkPolicy defaults), and on ordering commands under pressure. Shallow, memorized knowledge of kubectl flags without understanding the underlying object is the usual root cause.
Do I need prior production experience?
Not strictly, but familiarity with containers and Linux helps enormously. Candidates with only tutorial exposure often struggle with troubleshooting items. Running a multi-node cluster locally and deliberately causing failures compresses months of production exposure into a few weeks of practice.
What resources should I use to prepare?
The official Kubernetes documentation is the primary reference, and it is worth knowing its structure since it is the same reference used during many hands-on Kubernetes exams. Pair it with a local cluster for practice and the published exam blueprint to make sure every domain gets coverage proportional to its weight.