CKA Certification: Official Exam Format, Cost, and the Domain That's Worth 30% of Your Score

What This Certification Actually Certifies

CKA is fundamentally different in format from nearly every other certification covered on this site, and CNCF is direct about that difference: it is an online, proctored, performance-based test that requires solving multiple issues from a command line. There's no multiple choice, no drag-and-drop, no scenario-question format — you're working inside a live Kubernetes cluster environment for the full two hours, actually configuring, troubleshooting, and fixing infrastructure problems rather than answering questions about them.

The stated purpose is to provide assurance that CKAs have the skills, knowledge, and competency to perform the responsibilities of Kubernetes administrators. Because Kubernetes itself moves fast as an open-source project, CNCF explicitly plans quarterly exam updates to match Kubernetes releases — meaning the exact tooling version and environment you're tested against genuinely shifts over time, and candidates should check the current exam environment version directly through CNCF's FAQ before scheduling rather than assuming last year's prep material reflects today's environment.

Who This Exam Is For (and Who It's Not For)

There's no formal prerequisite, and CNCF places no experience or prior-certification gate on registration. That's a  contrast to how demanding the exam actually is in practice — third-party analysis consistently cites a first-attempt pass rate around 60–65%, and recommends candidates have a strong command of the Linux CLI and basic networking concepts before attempting it, even though nothing stops someone without that background from registering and sitting the exam.

It's a strong fit for DevOps engineers, SREs, and platform engineers who work with Kubernetes clusters hands-on and want to formalize that experience — CKA has become something close to a default table-stakes credential for anyone claiming serious hands-on Kubernetes experience, with CNCF reporting the exam passed 250,000 lifetime enrollments and remains the single most-taken cloud-native certification worldwide. It's a poor starting point for someone who's only read about Kubernetes conceptually or completed a course without  cluster practice — the exam's entirely hands-on format has no tolerance for candidates who understand Kubernetes in theory but haven't actually run kubectl commands under time pressure.

Exam Format and Structure

The exam runs 2 hours and consists entirely of performance-based items  problems to solve directly in a command-line environment against a live cluster, not questions to answer about one. Candidates have access to official Kubernetes documentation during the exam itself, which is a genuinely useful detail: this isn't a closed-book memorization test, and knowing how to efficiently navigate the docs under time pressure is itself part of the tested skill.

Because it's entirely hands-on, pacing works differently than a multiple-choice exam. With 15–20 tasks commonly reported across the two-hour window, each task can require multiple sequential steps (writing a YAML manifest, applying it, verifying it worked, troubleshooting if it didn't), so time management across tasks — knowing when to move on from a stuck task rather than losing disproportionate time on it — is a skill candidates specifically need to practice, not something that comes naturally from conceptual study alone.

Domains and Topics Covered

CNCF's official exam page publishes these five domains and their exact weights:

Troubleshooting is the single largest domain by a  margin, and that weighting reflects something genuine about the job itself rather than an arbitrary exam design choice —world cluster administration is largely about identifying and resolving issues as they come up, not just standing up a cluster once and walking away. Candidates who spend the bulk of their prep time on initial cluster setup and installation while treating troubleshooting as an afterthought are consistently the ones who underperform relative to their conceptual knowledge.

CNCF has also open-sourced the full curriculum behind the exam, available directly on GitHub, which is worth reviewing directly as the authoritative breakdown of what's actually in scope within each domain rather than relying solely on third-party summaries.

Cost Breakdown

The exam costs $445 USD and includes one free retake — a detail worth genuinely valuing given the exam's  difficulty and the roughly one-in-three chance third-party data suggests a first attempt doesn't succeed. That retake needs to be used within 12 months of your initial exam date; miss that window and you'd need to purchase a new attempt at full price. Exam fees are non-refundable regardless of outcome. CNCF also offers bundle pricing through Linux Foundation Training that pairs the exam with training courses or subscription access, and notes that U.S. government employees are eligible for a 5% discount, with other regional government discounts sometimes available.

Prerequisites and Eligibility

None are formally required — anyone can register and sit the exam without any prior certification or documented experience. In practice, though, the exam's difficulty functions as its own filter: strong command-line comfort with Linux and  hands-on Kubernetes cluster experience are effectively necessary even though CNCF doesn't check for either at registration.

How the Exam Is Scored and What Passing Requires

CNCF does not publish an exact passing percentage on its official exam page. A commonly repeated third-party estimate puts the passing threshold around 66%, with scoring based on the absolute number of tasks correctly completed rather than any curve relative to other candidates — but this specific figure isn't confirmed directly in CNCF's own materials, so treat it as a reasonable study target rather than a documented official cutoff.

Renewal and Recertification

CKA certification is valid for 2 years, a change from the original 3-year validity period that applied to certifications earned before April 1, 2024 (those older certifications retain their original 36-month validity from the date earned). Recertification currently requires retaking the exam.

One genuinely useful recent change is worth flagging: CNCF's CARE program (Certification Automatic Renewal & Extension) now offers a smarter path for candidates advancing toward Kubernetes security work. Effective June 18, 2026, passing or recertifying the CKS (Certified Kubernetes Security Specialist) exam automatically reinstates or extends your CKA certification as part of this program — worth knowing if you're already planning to pursue CKS, since CKS itself requires an active CKA as a prerequisite anyway.

How This Exam Compares to Its Closest Alternative

Within CNCF's own certification family, CKA sits alongside two closely related credentials: CKAD (Certified Kubernetes Application Developer), which focuses on building and deploying applications on Kubernetes rather than administering the cluster itself, and CKS (Certified Kubernetes Security Specialist), which requires an active CKA first and layers on security-specific hardening and threat-response skills. All three share the same hands-on, performance-based exam format and roughly the same $445 price point, positioned as a genuine credential ladder rather than competing alternatives — CKA is the administration-focused entry point, CKAD the developer-focused parallel track, and CKS the advanced security specialization built on top of CKA.

Outside the Kubernetes-specific ecosystem, the natural comparison candidates weigh is a cloud-provider certification (AWS Solutions Architect, Azure Administrator, Google Professional Cloud Architect) instead of or alongside a Kubernetes credential. The practical distinction: cloud-provider certifications validate platform-specific infrastructure knowledge tied to one vendor's ecosystem, while CKA validates vendor-neutral Kubernetes administration skills that transfer across any cloud (or on-premises) environment running Kubernetes. Many DevOps and platform engineering roles increasingly expect both rather than treating them as either/or.

 Preparation Timeline

For someone with genuine hands-on Kubernetes cluster experience already — deploying workloads, managing networking and storage, troubleshooting  cluster issues in a job context — a commonly cited preparation window is 6 to 8 weeks of focused practice specifically against exam-style timed scenarios, with particular attention to the Troubleshooting domain given its outsized 30% weight.

For someone with mostly conceptual Kubernetes knowledge or limited production cluster time, stretching that to 10 to 12 weeks (some sources suggest up to 150 hours of structured study) is more , and hands-on lab time is non-negotiable given the exam's entirely performance-based format — reading about Kubernetes concepts without extensive kubectl practice under timed conditions is a common, avoidable reason candidates fail their first attempt despite solid conceptual understanding.