How to Pass the CKAD Exam in 2026: A 6-Week Study Plan for the New Kubernetes v1.35 Curriculum

Working out how to pass the CKAD in 2026 comes down to one uncomfortable truth: this is not an exam you can read your way through. The Certified Kubernetes Application Developer exam is entirely hands-on, and you have two hours to solve real tasks in a live cluster from the command line. Reading the docs is not enough. You have to build genuine speed with kubectl until the commands come from muscle memory.

The good news is that CKAD is very learnable in six weeks if you practise the right way. This plan breaks the current Kubernetes v1.35 curriculum into a week-by-week schedule, tells you exactly what to drill, and shows you how to use the free killer.sh simulator so exam day feels familiar rather than frightening. If you have deployed anything to Kubernetes before, six weeks of focused study is realistic.

What Is the CKAD Exam in 2026?

The CKAD is a performance-based certification from the Cloud Native Computing Foundation (CNCF) and the Linux Foundation. Instead of multiple-choice questions, you are dropped into a set of real Kubernetes clusters and asked to complete practical tasks: create pods, configure deployments, expose services, set resource limits, and troubleshoot broken workloads.

Here are the current exam facts for 2026.

Exam Tip: The 66% pass mark sounds generous, but tasks are weighted. A single high-value task you leave unfinished can cost you the exam, so triage by points, not by question order.

The exam registration bundles two big advantages that many candidates forget to use: one free retake valid for 12 months, and two sessions on the killer.sh simulator, which is deliberately harder than the real thing. Both are covered in your 445 USD fee, so build them into your plan rather than treating them as extras.

The Five CKAD Domains and Their Weights

The v1.35 curriculum is split across five domains. Knowing the weights tells you where to spend your practice time.

Application Environment, Configuration and Security (25%)

The largest domain. Expect ConfigMaps, Secrets, resource requests and limits, ServiceAccounts, SecurityContexts, and how to define custom resources and operators at a basic level. This is where the most points live, so it gets the most attention in this plan.

Application Design and Build (20%)

Container images, defining and running pods, multi-container pod patterns (sidecar, ambassador, adapter), init containers, jobs, cronjobs, and persistent volume claims. Strong fundamentals here make everything else faster.

Application Deployment (20%)

Deployments, rolling updates and rollbacks, scaling, and using common templating tools such as Helm and Kustomize to deploy and manage workloads.

Services and Networking (20%)

ClusterIP, NodePort, and how to expose applications with Services. Network policies to restrict traffic, and Ingress basics for routing HTTP traffic to services.

Application Observability and Maintenance (15%)

Readiness, liveness and startup probes, container logging, monitoring application health, and debugging pods that will not start.

How to Pass the CKAD: The Six-Week Study Plan

This plan assumes one to two hours on weekdays and a longer practical session at the weekend. Every week ends with hands-on repetition, because the exam rewards speed and accuracy under time pressure, not theory.

Week 1: Environment Setup and kubectl Foundations

Get your tooling right before you learn anything else. The candidates who fail on time usually lose it fighting their own terminal.

• Install a local cluster with Minikube or Kind so you can practise for free.
• Set the alias alias k=kubectl and learn the imperative shortcuts: kubectl run, kubectl create, kubectl expose.
• Master --dry-run=client -o yaml to generate manifests instead of writing YAML by hand.
• Learn kubectl explain, for example kubectl explain pod.spec.containers.livenessProbe --recursive, so you can look up fields without leaving the terminal.

By the end of week one you should be able to create a pod, a deployment and a service imperatively in under a minute each.

Week 2: Application Design and Build

Work through the design domain until pod creation is automatic.

• Single and multi-container pods, and the sidecar, ambassador and adapter patterns.
• Init containers and why they run to completion before app containers start.
• Jobs and CronJobs, including completions, parallelism and schedules.
• PersistentVolumeClaims and mounting storage into pods.

Week 3: Configuration, Security and the Big Domain

This is the 25% domain, so give it a full week.

• ConfigMaps and Secrets, injected as environment variables and as mounted volumes.
• Resource requests and limits, and how the scheduler uses them.
• SecurityContext at pod and container level, including running as non-root.
• ServiceAccounts and basic role bindings.

Exam Tip: Practise mounting a Secret as a volume and as an environment variable until you can do both from memory. It is one of the most commonly tested tasks and easy points if you are quick.

Week 4: Deployment, Services and Networking

Combine two domains that naturally overlap in real tasks.

• Deployments, rolling updates, kubectl rollout status, kubectl rollout undo, and scaling with kubectl scale.
• Helm basics: install, upgrade and rollback a chart. Kustomize overlays.
• Services: ClusterIP, NodePort, and exposing a deployment with kubectl expose.
• NetworkPolicies to allow or deny traffic between pods, and Ingress routing fundamentals.

Week 5: Observability, Maintenance and Full Mock Runs

• Configure readiness, liveness and startup probes correctly, and know the difference.
• Read container logs with kubectl logs, including previous crashed containers.
• Debug a pod stuck in Pending, CrashLoopBackOff or ImagePullBackOff.
• Run your first full timed mock. Aim to complete a 15 to 20 task set in two hours.

Week 6: killer.sh, Speed and Exam Readiness

Use your two included killer.sh sessions this week, not earlier. They are harder than the real exam by design, so they are perfect for the final push.

• Take your first killer.sh session under strict exam conditions. Note every task that slowed you down.
• Review the full solutions, then redo the questions you struggled with until they are fast.
• Take your second session two or three days later. A score of 70% or higher here means you are ready.
• Rehearse your exam-day setup: alias, vim settings, and bookmarking the allowed documentation.

kubectl Speed: The Skill That Actually Passes CKAD

Almost everyone who fails CKAD fails on time, not knowledge. The fix is imperative-first working. For any simple task, generate the YAML rather than typing it.

k run nginx --image=nginx --dry-run=client -o yaml > pod.yaml
k create deployment web --image=nginx --replicas=3 --dry-run=client -o yaml > deploy.yaml
k expose deployment web --port=80 --target-port=8080 --dry-run=client -o yaml > svc.yaml

Then edit only what the task requires. Combine this with kubectl explain for field lookups and you rarely need to open the documentation at all. Every second you save on a simple task is a second you can spend on a hard one.

CKAD vs CKA vs CKS: Where CKAD Fits

CKAD is one of three CNCF Kubernetes certifications, and candidates often ask which to take first. Here is the short version.

CKAD is the natural starting point for developers, and it does not require any prerequisite. If you administer clusters rather than build apps on them, start with the CKA study plan instead. If you already hold CKA and want to specialise in security, the CKS study plan is your next step. Many engineers work through all three, and practising them together on CertCrush keeps the shared kubectl skills sharp across every exam.

Common CKAD Mistakes to Avoid

• Writing YAML from scratch. Generate it imperatively and edit. Typing full manifests by hand is the single biggest time sink.
• Ignoring the context switch. The exam uses multiple clusters. Read the kubectl config use-context line at the top of every task and run it, or you will solve the right problem in the wrong cluster.
• Leaving high-weight tasks for last. Skim all tasks first, do the quick high-value ones, and flag the rest.
• Skipping killer.sh. Two free, exam-realistic sessions come with your registration. Not using them is throwing away your best preparation.
• Neglecting the free retake. If the first attempt does not go your way, you have a free retake for 12 months. Book it, review your weak tasks, and go again.

Is CKAD Worth It in 2026?

Yes, for developers working in cloud-native environments. Kubernetes remains the default container orchestration platform, and CKAD is the credential that proves you can build and ship on it rather than just talk about it. Because it is performance-based, hiring managers trust it more than multiple-choice certs. It is a two-year certification, so plan to renew, but for developers deploying to Kubernetes daily, the practical skills you build studying for it pay off well beyond the exam.

Ready to Start Practising?

CKAD is passed in the terminal, not in a textbook, so the sooner you start doing tasks against a real cluster the better. A structured question bank that mirrors the exam format turns the six-week plan above into repeatable, measurable practice.

Create your free CertCrush account and start drilling Kubernetes tasks today. Work through realistic CKAD scenarios, track your weak domains, and build the kubectl speed that gets you across the 66% line first time. Explore the full range of Kubernetes and cloud certifications while you are there and map out your next credential.

Pass CKAD, then keep going. The CKA and CKS study plans are ready when you are.