You have 7 days until your CKA exam. The decisions you make this week matter more than the previous month of preparation. Most candidates lose points not from gaps in knowledge, but from peaking too early, drilling the wrong topics, or burning out 48 hours before the exam.
This 7-day plan is built for candidates who already know the material. It focuses on speed, recall, and the high-yield troubleshooting and cluster admin scenarios that make up most of the score. By Day 7, you’ll be sharp, calibrated, and confident — not exhausted.
Who This Plan Is For
You should already have:
- Spent at least 4-6 weeks on CKA preparation
- Built and broken kubeadm clusters
- Hit at least one practice exam in the 60-70% range
- Comfortable with kubectl and basic YAML
If you’re below those benchmarks, 7 days isn’t enough — see our 30-day CKA study plan instead.
The Core Principle: Peak on Day 7, Not Day 4
The biggest mistake at this stage is over-studying. Your brain consolidates skills during sleep and rest. The candidate who drills 12 hours/day for a week walks into the exam exhausted and slow. The candidate who balances 3-4 focused hours/day with sleep, exercise, and short breaks walks in sharp.
Daily structure: 3-4 hours of focused work, broken into two sessions. Stop when the timer hits. Trust the process.
Day 1: Diagnostic Mock + Weakness Identification
Today is about knowing where you stand.
Morning (90 minutes)
Take a full-length, scored, timed mock exam. Don’t pause. Don’t Google outside the official Kubernetes docs. Treat it like the real thing.
When you finish, score yourself honestly:
- 75%+ → You’re in great shape. The week is for sharpening, not learning.
- 60-74% → Solidly pass-able with focused work. Stick to the plan.
- 50-59% → Possible but tight. You’ll need to push on weak domains.
- Below 50% → Consider rescheduling. The CKA is hands-on; gaps don’t close in 7 days.
Afternoon (60 minutes)
Categorize every missed question by domain:
- Cluster Architecture, Installation & Configuration (25%)
- Workloads & Scheduling (15%)
- Services & Networking (20%)
- Storage (10%)
- Troubleshooting (30%)
Identify the 1-2 domains where you lost the most points. These are this week’s targets.
Evening
Review your weakest domain in the official Kubernetes documentation. Don’t take a second mock today — let the diagnostic settle.
Day 2: Troubleshooting Drills (the 30% Domain)
Troubleshooting is the largest domain and the highest-leverage practice area. Today is troubleshooting only.
Morning (90 minutes)
Pick five “broken cluster” scenarios and time yourself solving each in under 6 minutes:
- A pod is
Pending(cause: nodeSelector or taint). - A pod is
CrashLoopBackOff(cause: wrong command or OOMKilled). - A service has no endpoints (cause: selector mismatch).
- A node is
NotReady(cause: kubelet stopped or wrong runtime). - The API server is unreachable (cause: bad static pod manifest).
If you don’t have a lab, our CKA troubleshooting guide has the full diagnostic playbook with kubectl recipes.
Afternoon (60 minutes)
Drill kubectl describe, kubectl logs --previous, and crictl logs on real running clusters. The goal: when a pod misbehaves, your fingers reach for the right command without thinking.
Evening
Review one tricky topic from your morning drills. Don’t add new material.
Day 3: Cluster Admin (etcd, Upgrade, RBAC)
These three together are 25% of the exam plus heavy partial overlap with troubleshooting. Today is procedural drills.
Morning (90 minutes)
Drill 1: Full etcd backup and restore on a kubeadm cluster. Goal: under 6 minutes including manifest edit. See our CKA etcd backup and restore guide.
Drill 2: Cluster upgrade from one minor version to the next. Goal: under 12 minutes for a single control plane + single worker. See our CKA cluster upgrade with kubeadm guide.
Afternoon (60 minutes)
Drill 3: Five RBAC scenarios from our CKA RBAC hands-on guide:
- Create a SA with read-only permissions on pods.
- Bind a built-in ClusterRole to a user in a specific namespace.
- Lock down a role to a specific resource name.
- Diagnose a “forbidden” error.
- Create a ClusterRoleBinding for a group.
Time each one and aim for under 5 minutes total per scenario.
Evening
No drills. Review the kubeadm upgrade flag order in your head before bed.
Day 4: Networking and NetworkPolicy
20% of the score, often the domain where YAML mistakes silently cost points.
Morning (90 minutes)
Run through these scenarios on a kind or kubeadm cluster:
- Expose a Deployment as ClusterIP, NodePort, and LoadBalancer.
- Create an Ingress with two paths routing to two services.
- Write a default-deny ingress NetworkPolicy.
- Add an allow-from-namespace NetworkPolicy.
- Add an egress NetworkPolicy that permits DNS only.
- Test each policy from a busybox pod with
wget --timeout=3.
For YAML templates and verification recipes, see our CKA networking deep dive.
Afternoon (60 minutes)
Take a 30-minute timed practice block (around 8 questions) focused on services and networking. Score yourself.
Evening
Quick review of kubectl auth can-i syntax — it’s the single most-used verification command on the exam.
Day 5: Workloads, Scheduling, Storage (the Smaller Domains)
15% workloads + 10% storage = 25% of the exam, but these are the easiest points if you’ve drilled the imperative commands.
Morning (90 minutes)
Imperative drill — generate YAML with --dry-run=client -o yaml for each:
- Deployment with 3 replicas, resource requests, and a readiness probe.
- StatefulSet (you’ll need YAML for this; no clean imperative shortcut).
- Multi-container Pod with init containers and a sidecar.
- Pod with nodeSelector or affinity.
- DaemonSet (also YAML — practice the template).
Afternoon (60 minutes)
Storage drill:
- Create a StorageClass.
- Create a PVC that binds to a static PV.
- Create a Pod that mounts the PVC.
- Resize the PVC (if the SC supports it).
- Delete the PVC and observe reclaim policy behavior.
Evening
Take 30 minutes of timed practice questions. Score honestly. If you’re consistently above 70%, you’re on track.
Day 6: Full-Length Mock Exam (The Final Calibration)
Today is the most important day of the week.
Morning
Take a full-length, scored, timed mock under exam conditions:
- Clean desk, no distractions.
- 2-hour timer, no pauses.
- Only the official Kubernetes documentation as reference.
- Don’t peek at solutions until the timer ends.
If you score 75%+, you’re ready. The exam will feel similar.
If you score 65-74%, you’re still on track — review the missed questions in the afternoon.
If you score below 65%, don’t panic. Identify the 1-2 question categories that cost the most points and drill those tomorrow morning. Consider rescheduling if you have the option.
Afternoon
Review every missed question. For each, write down:
- The exact wrong answer you gave.
- The correct approach.
- Why you missed it (knowledge gap, time pressure, careless reading).
Most missed questions on Day 6 are speed and accuracy issues, not knowledge gaps. The fix isn’t more learning — it’s more careful execution.
Evening
Stop studying. Pack your exam-day setup:
- Government-issued photo ID
- Quiet, private space confirmed
- Webcam, microphone, stable internet tested
- Computer meets Linux Foundation requirements
Sleep early.
Day 7: Light Touch + Exam-Day Readiness
The day before the exam is for confidence, not learning.
Morning (45 minutes max)
Light review only:
- Skim your kubectl cheat sheet (see our CKA kubectl cheat sheet).
- Walk through the etcd backup/restore steps in your head.
- Walk through the cluster upgrade order in your head.
- Skim NetworkPolicy templates.
Don’t do a mock exam. Don’t drill. You’re in calibration mode.
Afternoon
Rest. Take a walk, exercise lightly, do something unrelated to Kubernetes. The brain consolidates during downtime.
Evening
- Eat a normal dinner.
- Set your alarm.
- Lay out your ID and a glass of water.
- Sleep.
Exam Day: The Plan
Before You Start
- Eat a light meal 1-2 hours before the exam.
- Test your network and webcam 30 minutes before.
- Have your ID, water, and a clean desk ready.
- Close all other apps.
- Use the bathroom right before login.
During the First 5 Minutes
Don’t dive into the first question. Spend the first 5 minutes:
- Configure your shell (alias
k, completion,$do,$nowexports). - Skim every question. Note each one’s point value.
- Plan your order: highest-point quick wins first, slow procedural questions (upgrade, etcd) last.
During the Exam
- Switch context first. Every question. The #1 silent point loss is applying YAML to the wrong cluster.
- Verify every answer before moving on (
kubectl get,kubectl auth can-i,wget --timeout=3). - Flag and skip anything that takes more than 5 minutes. Come back at the end.
- Don’t over-engineer. The grader wants the minimum correct answer, not the production-grade one.
Last 15 Minutes
Return to flagged questions. Bank partial credit by writing a --dry-run YAML even if you can’t complete the apply.
What Not to Do This Week
- Don’t learn new tools. It’s too late for Helm or Kustomize unless you’re already fluent.
- Don’t switch your editor. If you’ve practiced with vim, don’t try nano on Day 4.
- Don’t change your kubectl aliases. Muscle memory is fragile this close to the exam.
- Don’t take 3 mocks in 3 days. Diminishing returns; you’ll burn out.
- Don’t read forum stories of failed attempts. Anxiety doesn’t help.
A Realistic Pep Talk
The CKA isn’t a knowledge test — it’s a reflex test. By now, you either have the reflexes or you don’t, and 7 days of cramming won’t change that. What 7 days can do is make sure you arrive sharp, well-rested, and free of avoidable mistakes.
Most candidates who fail aren’t unprepared. They’re tired, panicked, or rushed. Stay calm, trust your preparation, and treat exam day as another mock with higher stakes.
The Single Most Important Tool This Week
If you take only one piece of advice: take at least two full-length, scored mock exams under exam conditions in the last 7 days. The number on the result page calibrates everything — your speed, your weak domains, and your confidence.
Our CKA Mock Exam Bundle includes multiple full-length simulators with the same UI, certificates layout, and scoring rubric as the real exam. The candidates who go in confident are the ones who’ve already passed a scored simulator. Be one of them.
Frequently Asked Questions
Q: I’m scoring 50% on mocks with 7 days to go. Should I reschedule? A: Probably yes. The CKA is a hands-on exam — gaps don’t close in a week. Rescheduling is free for first-time candidates within 24 hours of the original time.
Q: How many hours per day should I study this week? A: 3-4 hours of focused work, no more. Quality over quantity. Burning out is worse than skipping a session.
Q: Should I take a mock on Day 7? A: No. Day 7 is for rest and light review. The last mock should be Day 6.
Q: What if I’ve never used kubectl bash completion? A: Practice it tomorrow morning for 10 minutes. It’s the single biggest speed gain on the exam.
Q: Should I memorize NetworkPolicy YAML? A: Memorize the four templates: default-deny ingress, default-deny egress, allow-from-namespace, and allow-from-pod. Most NetworkPolicy questions are variants of those.
Q: I’m anxious. What should I do? A: Anxiety is normal. Two things help: (1) take one well-executed mock (success builds confidence faster than reading), and (2) sleep. Cognitive performance drops sharply with poor sleep — protect it.
Q: Should I take the exam in the morning or evening? A: Whatever matches your peak alertness. For most people that’s mid-morning. Avoid late-night exam slots — proctoring tech glitches are more common, and you’ll be tired.
Ready to peak at the right moment? Run a final scored simulator with our CKA Mock Exam Bundle and walk into your exam knowing you’ll pass.