Failed Certified Kubernetes Application Developer (CKAD)? Here's Your Recovery Plan

Pro tip: The included retake must be scheduled and completed within 12 months of the original purchase date, the same window as the initial exam eligibility. If the window lapses, both the eligibility and the retake expire together.

• Writing every manifest by hand in vim from a blank file
  Generate the base YAML with kubectl create or kubectl run plus --dry-run=client -o yaml, redirect it to a file, then edit only the fields the task asks for. This routinely saves two to three minutes per task, which is one to two extra tasks over the full exam.
• Forgetting to set the namespace and creating objects in default
  Read the namespace line in every task first. Either pass -n to every command or run kubectl config set-context --current --namespace=<ns> at the start of the task. Objects created in the wrong namespace score zero even when the manifest is correct.
• Running out of time because one hard task consumed 20 minutes
  Set a personal ceiling of eight minutes per task. Flag the task in the exam interface, note it on the provided notepad, move on, and come back with whatever time is left. At 66% to pass you can afford to lose whole tasks, but you cannot afford to lose several easy ones you never reached.
• Practising on an old Kubernetes version and hitting removed API versions
  Check the current exam version on the Linux Foundation instructions page, which lists v1.35, and pin your kind or minikube cluster to it. Manifests using deprecated apiVersions from older tutorials will be rejected by the API server.
• Treating CKAD like CKA and studying control plane administration
  Skip etcd backups, kubeadm upgrades, certificate rotation and node cordon and drain. None of those appear in the CKAD curriculum. Spend the time instead on the 25% environment, configuration and security domain, which is the single largest scoring block.
• Losing the Service to Pod connection because of a label selector typo
  After creating any Service, run kubectl get endpoints <name>. An empty endpoints list means the selector does not match any Pod labels. This one check catches the most common silent failure in the services and networking domain.
• Opening an external search result during the exam
  Search only within kubernetes.io/docs using its own search box, and do not follow results that leave the allowed domains. Allowed sites are kubernetes.io/docs, kubernetes.io/blog, helm.sh/docs and the Quick Reference links. Leaving them is a policy breach that can void the attempt.
• Skipping the simulator until the night before
  Take the first of your two Killer.sh attempts about two weeks out, so the failures still leave time to fix them, and the second attempt about three days out as a dress rehearsal. Each attempt gives 36 hours of access, so you can review the solutions after the timed session ends.
• Not verifying the work after finishing a task
  Spend 20 seconds running kubectl get and kubectl describe on whatever you created. Grading reads cluster state, so a Pod stuck in Pending or CrashLoopBackOff scores nothing even though the YAML looked right when you applied it.
• Assuming the free retake can be used at any time
  The included retake must be taken within 12 months of the original purchase date. If you buy during a discount period and delay, the eligibility window and the retake expire together, and a further attempt means paying full price again.

• Score 66% or higher on 15-20 hands-on tasks in 2 hours
• Use the two included killer.sh simulator attempts, 17 questions each
• Set alias k=kubectl and export do='--dry-run=client -o yaml' first
• Only kubernetes.io/docs, kubernetes.io/blog and helm.sh/docs are allowed
• Flag and skip any task over 8 minutes, then return to it
• The exam environment runs Kubernetes v1.35, so practice on that version