CNCF

The Cloud Native Computing Foundation hosts open-source projects focused on container orchestration. Its performance-based certifications validate practical skills in the administration, configuration, and troubleshooting of Kubernetes clusters.

2Exams

Available Exams

The Foundation of Modern Infrastructure

The Cloud Native Computing Foundation (CNCF) formed in 2015 as a subsidiary of the Linux Foundation. Its creation aligned with Google donating Kubernetes—an open-source container orchestration platform—as the foundation's initial seed project. Before this, the industry was fragmented. Engineers deployed containers using a mix of competing orchestrators, custom scripts, and manual processes. Kubernetes established a standard model for deploying, scaling, and managing containerized applications.

Today, the CNCF hosts over 150 projects, including prominent technologies like Prometheus for monitoring and Envoy for network proxying. Yet Kubernetes remains the core of the cloud-native ecosystem. A 2025 CNCF survey reports that 82 percent of container users run Kubernetes in production. This widespread adoption has created a massive market demand for engineers who possess the practical skills to build, maintain, and repair these distributed systems.

Continue Reading

A Departure from Multiple Choice

Most enterprise IT certifications rely on multiple-choice formats. Candidates memorize trivia, eliminate incorrect options, and guess their way through difficult scenarios. The CNCF takes a different approach.

CNCF certification exams are entirely performance-based. Candidates do not answer questions; they complete tasks. The testing environment consists of a browser-based terminal connected to live, running Linux virtual machines and Kubernetes clusters. You are asked to configure resources, fix broken deployments, or extract specific cluster information. If you do not know the command-line syntax or how to navigate the operating system, you will fail.

The CNCF allows candidates to access the official Kubernetes documentation during the exam. This mirrors real-world engineering. You do not need to memorize every line of a YAML specification, but you must know how to search the documentation, copy the relevant template, and modify it in a terminal text editor like Vim or Nano. This open-book policy shifts the focus from rote memorization to execution speed and problem-solving.

The CKA: Certified Kubernetes Administrator

The foundation's flagship credential is the CKA: Certified Kubernetes Administrator. It targets platform engineers, cloud administrators, and DevOps professionals responsible for keeping Kubernetes clusters running in production environments.

The exam places candidates in a live, proctored command-line environment for exactly two hours. During this time, you must complete roughly 17 practical tasks. Each task carries a specific weight toward your final score, and you must achieve a 66 percent to pass.

The CKA tests your ability to operate raw, vanilla Kubernetes. It ignores vendor-specific abstractions like Amazon EKS, Google Kubernetes Engine, or Azure Kubernetes Service. Instead, it focuses on the core components. You must know how to use the kubectl command-line tool, write YAML manifests from scratch, and manipulate underlying system services. The exam environment aligns with a recent Kubernetes minor release, usually updating within a few weeks of a new version dropping.

Core Exam Domains

The CKA divides its tasks across five specific domains, each testing a different layer of cluster administration.

Troubleshooting carries the heaviest weight at 30 percent. You can expect broken clusters. A task might require you to find out why a worker node is stuck in a NotReady state, or why a pod is crashing in a continuous loop. You will need to inspect system logs, check the status of the kubelet service on the node, and repair misconfigurations on the fly. Time management is critical here. With only 120 minutes for 17 tasks, spending 20 minutes debugging a single node will jeopardize the rest of the exam.

Cluster Architecture, Installation, and Configuration makes up 25 percent of the exam. This involves managing the control plane. You will use tools like kubeadm to upgrade cluster versions without disrupting running workloads. You must also know how to back up and restore the etcd key-value store, which holds the entire state of the Kubernetes cluster. If the etcd backup fails in a production environment, the cluster cannot be recovered from a disaster.

Services and Networking accounts for 20 percent. Kubernetes networking relies on complex routing rules. Candidates must demonstrate they can expose applications internally and externally, configure ingress resources to route HTTP traffic, and enforce network policies. A network policy task might require you to write rules that restrict pod-to-pod communication, isolating a database so only a specific backend service can reach it.

Workloads and Scheduling (15 percent) covers the mechanics of deploying applications. This includes creating Deployments, configuring DaemonSets to run logging agents on every node, and writing node affinity rules. Affinity rules ensure pods land on the correct servers—for example, forcing a machine learning workload to schedule only on nodes equipped with GPUs.

Storage (10 percent) rounds out the exam. Containers are ephemeral; when they crash, their local data disappears. You will configure PersistentVolumes and PersistentVolumeClaims, ensuring that stateful applications like databases retain their data if a pod restarts or moves to a different physical server.

Career Weight and Market Position

Over 100,000 IT professionals have tackled the CKA exam. While this number is growing, it remains a fraction of the millions who hold entry-level networking or cloud certifications. The difficulty of the performance-based format acts as a natural filter in the job market.

For organizations running containers at scale, this certification serves as a baseline requirement for infrastructure roles. Seventy-seven percent of Fortune 100 companies deploy Kubernetes in production. These enterprise environments cannot afford to hand the keys to their clusters to administrators who only understand the theory. A misconfigured network policy or a botched etcd backup can take down an entire application suite.

Holding the CKA: Certified Kubernetes Administrator proves you have the muscle memory to handle these situations. When hiring managers see this credential, they know the candidate has typed the commands, read the logs, and implemented fixes under time pressure. It signals practical competence rather than theoretical familiarity.

The Reality of CNCF Recertification

The CNCF recently tightened its renewal policies. CKA certifications achieved after April 2024 remain valid for two years, down from the previous three-year window. This change reflects the aggressive release cycle of the Kubernetes project itself, which pushes out three minor versions annually.

Because the technology shifts quickly, resting on past knowledge leads to outdated practices. Deprecated APIs disappear, new gateway standards emerge, and default security postures change. The two-year expiration forces administrators to stay engaged with the ecosystem. When your credential expires, you must return to the terminal, face a new set of live clusters, and prove your command-line skills against the current release.