You failed. The score report says 672 and passing is 720. Here’s exactly what that means and what you do next.
What Your Score Actually Means
You scored 672 out of 900. Passing is 720. You’re 48 points away. That’s about 5%.
The CKAD exam uses scaled scoring, not raw percentages. Your 672 doesn’t mean you got 75% of questions right. It means the exam’s statistical algorithm determined your competency level fell short of the passing bar. That’s a critical distinction because it changes how you study for your retake.
The exam has roughly 17 questions across 2 hours and 59 minutes. Each question is weighted differently depending on difficulty and cognitive load. A single imperative deployment question might be worth more than a simple ConfigMap creation. Your 672 tells you that you got some questions right, but missed too many in the weighted categories.
Here’s what this likely means in practical terms: you probably nailed basic YAML syntax and simple object creation. You probably struggled with multi-step scenarios like “deploy this application, expose it via a service, configure resource limits, and verify logs across three namespaces.” Those complex, real-world questions carry more weight.
You need 48 more points. That’s achievable. People retake and pass all the time. But not by studying harder at the same thing.
The Real Reason You Failed Certified Kubernetes Application Developer (CKAD)
You studied topics. You didn’t practice exam scenarios.
The CKAD isn’t a knowledge test. It’s a performance test. You sit at a live terminal. You deploy applications. You fix broken configurations. You work under time pressure.
Most failing candidates make one of three mistakes:
Mistake 1: Watching videos instead of typing. You watched someone deploy a Pod and felt like you learned it. You didn’t. Your hands never touched kubectl. Your muscle memory is zero. When exam day comes and you’re under pressure, your fingers freeze.
Mistake 2: Taking practice tests but not reviewing the why you failed. You run through a practice test, see your score, move on. You never diagnose which question type destroyed you. Was it imperative vs. declarative? Was it networking? Was it time management? Without this data, you retake and fail the same way.
Mistake 3: Memorizing kubectl commands instead of understanding what they do. You know kubectl create deployment nginx --image=nginx works. But when the exam asks you to create a deployment, modify its resource requests, add a sidecar container, and expose it through a service—you’re lost. You don’t understand the relationships between objects.
The CKAD tests these specific things:
- Creating and modifying Pods, Deployments, StatefulSets, DaemonSets
- Configuring Services, networking, and ingress rules
- Managing ConfigMaps and Secrets
- Debugging running applications
- Understanding resource limits, requests, and Pod disruption budgets
- Working with storage and persistent volumes
If your score report showed you struggled in any of these areas, that’s where 48 points are waiting.
What To Do In The Next 48 Hours
Stop studying new material. You know enough to pass.
Step 1: Get your hands on a live Kubernetes cluster (today). Use Minikube, kind, or KinD. It takes 20 minutes to set up. It’s free. If you don’t have one yet, every hour you delay is an hour you’re not fixing the real problem.
Step 2: Recreate three scenarios from your failed exam (tomorrow). Don’t memorize them. You won’t see the exact same questions. Instead, find three multi-step scenarios that stressed you out. Could be deployment-plus-service-plus-debugging. Could be StatefulSet with persistent volume. Could be ConfigMap mounting and container environment variables.
Work through each one without looking at documentation. Time yourself. Stop when you finish or when 15 minutes pass. Then check the answer. Document what you did wrong. Don’t move on.
Step 3: Stop taking practice tests for 48 hours. Tests measure where you are. They don’t improve where you’re going. Right now, targeted practice beats test-taking.
Your Retake Plan
You have a waiting period. Depending on your test provider, it’s usually 24 hours before you can retake. Some vendors allow immediate retake. Check your confirmation email or contact the testing center.
The cost to retake is $395 (the same as the initial attempt). That’s the price of your next attempt. Don’t hesitate on cost. You’re 48 points away. You can close that gap in two weeks.
Week 1: Hands-on drilling (5 hours per day, focused)
- Monday & Tuesday: Deploy and expose applications. Create a Deployment with three replicas. Expose it via ClusterIP, then NodePort, then LoadBalancer. Verify the service works. Delete and recreate it. Do this five times. Your hands need to know the motions.
- Wednesday & Thursday: Debugging scenarios. Break something intentionally. A Pod won’t start. An image doesn’t exist. A resource request is too high. Use
kubectl describe,kubectl logs,kubectl exec. Find and fix the problem. Do this eight times. - Friday: ConfigMaps and Secrets. Create them. Mount them as files. Mount them as environment variables. Update them and see how Pods react. Run six scenarios.
Week 2: Scenario-based practice (4 hours per day)
- Monday-Thursday: Run four practice exam simulations. These are timed, multi-question scenarios that mimic the real exam. Use KodeKloud, Linux Academy, or Killer.sh. These platforms give you real exam-style environments.
- Friday: Review mistakes. Don’t run another full test. Pull apart your three weakest scenarios. Redo them. Understand why you failed.
- Weekend: Light review. 30 minutes of kubectl command reference. Rest.
Retake day: Three things.
- Read the exam instructions twice. Seriously. Read them.
- Start with the easiest question. Build confidence.
- Flag hard questions and return if time allows.
One Thing To Do Right Now
Open your terminal. Run minikube start or kind create cluster. While that’s spinning up, download one practice scenario from KodeKloud’s free tier or Killer.sh’s CKAD simulator.
In the next 30 minutes, deploy a simple Nginx application without looking at documentation. Use kubectl run or write the YAML from memory. See what sticks. See what doesn’t.
That’s your baseline for the next two weeks. Your score will move because your hands will move first.
You’re 48 points away. You’re not starting over. You’re finishing what you started.