How Long to Study for Certified Kubernetes Application Developer (CKAD)
A complete week-by-week study plan for the Certified Kubernetes Application Developer (CKAD) (Hard difficulty, Not published pass rate).
12
Weeks
10
Hrs/Week
114
Total Hours
Not published
Pass Rate
8-10 this week
- Install a local cluster with kind or minikube running Kubernetes v1.35
- Add alias k=kubectl, source the kubectl completion script and export do='--dry-run=client -o yaml'
- Create Pods imperatively with kubectl run and inspect them with describe and get -o yaml
- Practise kubectl explain to find field paths without opening documentation
- Learn namespace switching with kubectl config set-context --current --namespace
8-10 this week
- Create Deployments, DaemonSets, Jobs and CronJobs from imperative commands
- Build an init container that waits on a Service before the main container starts
- Build a sidecar that tails a shared emptyDir volume written by the main container
- Set Job completions, parallelism and backoffLimit and watch the Pods finish
- Time yourself creating each workload type in under 90 seconds
9-11 this week
- Create ConfigMaps from literals, files and directories with kubectl create configmap
- Inject configuration three ways: single env var, envFrom, and a mounted volume
- Create generic and docker-registry Secrets and decode them with base64 -d
- Attach a ServiceAccount to a Pod and inspect the projected token volume
- Set a SecurityContext with runAsUser, fsGroup and dropped capabilities
8-10 this week
- Set requests and limits on containers and observe scheduling failures when they exceed node capacity
- Create a ResourceQuota and a LimitRange in a namespace and watch Pod creation get rejected
- Read the difference between Guaranteed, Burstable and BestEffort QoS classes
- Explore a CustomResourceDefinition and list its instances with kubectl get
- Review RBAC verbs and test permissions with kubectl auth can-i
8-10 this week
- Create a PersistentVolume and a matching PersistentVolumeClaim and bind them
- Mount a PVC into a Deployment and confirm data survives a Pod delete
- Compare emptyDir, configMap, secret and downwardAPI volume types side by side
- Practise accessModes and storageClassName mismatches so you recognise a Pending PVC
- Write a Pod manifest with two containers sharing one emptyDir
9-11 this week
- Run a rolling update, check kubectl rollout status, then roll back with rollout undo
- Tune maxSurge and maxUnavailable and observe the replica counts during the update
- Build a canary by running two Deployments behind a single Service selector
- Install, upgrade and uninstall a Helm chart and override values with --set
- Create a Kustomize base and overlay and apply it with kubectl apply -k
9-11 this week
- Expose Deployments with kubectl expose as ClusterIP, NodePort and LoadBalancer
- Break a Service on purpose by changing the selector, then diagnose it with kubectl get endpoints
- Write an Ingress with two host rules and two path rules and check pathType behaviour
- Resolve service DNS names from inside a Pod with nslookup and wget
- Practise reaching a Service by its fully qualified cluster DNS name across namespaces
9-11 this week
- Install a CNI that enforces NetworkPolicy, such as Calico, on your practice cluster
- Write a default-deny policy, then allow one Pod by label and verify with wget
- Add ingress and egress rules including a namespaceSelector and a port restriction
- Add liveness, readiness and startup probes to a Deployment and force each to fail
- Read logs with kubectl logs --previous after deliberately crashing a container
10-12 this week
- Fix a broken cluster scenario set covering ImagePullBackOff, CrashLoopBackOff and Pending Pods
- Use kubectl debug to attach an ephemeral container to a distroless Pod
- Practise kubectl get events --sort-by=.metadata.creationTimestamp as a first diagnostic step
- Run timed sets of 8 mixed tasks in 45 minutes and record which task types cost you time
- Rebuild your alias and vim setup from scratch in under 2 minutes
10-12 this week
- Take the first Killer.sh simulator attempt under full exam conditions with no pauses
- Score the attempt, then list every task you failed and the domain it belongs to
- Redo every failed task from a blank terminal without looking at the answer
- Re-read the CNCF curriculum PDF and tick off any bullet you cannot demonstrate
- Rehearse the documentation search path for your three slowest task types
8-10 this week
- Take the second Killer.sh simulator attempt and aim to finish with 15 minutes spare
- Do a full PSI system check on the exact machine and network you will use
- Clear your desk, test your webcam and confirm one monitor only
- Practise the copy and paste key combinations Ctrl+Shift+C and Ctrl+Shift+V
- Write a one-page cheat sheet from memory, then throw it away
6-8 this week
- Redo the 10 tasks you have failed most often across all practice sessions
- Confirm your government-issued photo ID is unexpired and matches your registered name
- Schedule the exam at least 24 hours in advance at a time you are alert
- Do one 60-minute half-length run to keep pace without exhausting yourself
- Stop new material 48 hours before the exam and review only your own notes
Duration: 18 weeks
Hours/week: 7 hours
Daily: ~1 hours on weeknights
Weekends: 3-4 hours Saturday + Sunday
Study during lunch breaks and commute time. Use weekends for deeper study sessions and practice tests.
Duration: 24 weeks
Hours/week: 5 hours
Saturday: 4-5 hours of focused study
Sunday: 3-4 hours of practice tests
Longer timeline but sustainable. Review flashcards on weeknights for 15-20 minutes to maintain retention.
How long does it take to study for the Certified Kubernetes Application Developer (CKAD)?
Plan for 12 weeks of dedicated study at 10 hours per week (114 total hours). If studying while working full-time, extend to 18 weeks.
Can I pass the Certified Kubernetes Application Developer (CKAD) in 2 weeks?
It's unlikely for most candidates. The Certified Kubernetes Application Developer (CKAD) is rated "Hard" difficulty and typically requires 12 weeks of preparation. Rushing increases your risk of failing and paying the exam fee again.
How many hours a day should I study for Certified Kubernetes Application Developer (CKAD)?
Aim for 2-3 hours per day on weekdays. Quality matters more than quantity, use active recall and practice tests rather than passive reading.
Is Certified Kubernetes Application Developer (CKAD) hard to pass?
The Certified Kubernetes Application Developer (CKAD) is rated "Hard" difficulty with a pass rate of Not published. Solid preparation over several months is recommended.
Ready to start your Certified Kubernetes Application Developer (CKAD) journey?
Get the complete exam guide with tips, resources, and practice questions.
View Certified Kubernetes Application Developer (CKAD) Guide