Five exams, one title: the Kubestronaut roadmap

The five exams, in the order I took them

The two multiple-choice exams first, to learn the vocabulary, then the three hands-on exams. The CKS needs the CKA first, so it comes last.

1. 1

   KCNA: Kubernetes and Cloud Native Associate

   Passed Feb 2025

   Cloud native basics: containers, the Kubernetes architecture, kubectl, scheduling, observability and application delivery. It builds the vocabulary everything else uses.

   Multiple choice90 minutesValid for two years

   My notesOfficial exam page

2. 2

   KCSA: Kubernetes and Cloud Native Security Associate

   Passed May 2025

   Security fundamentals: the four Cs of cloud native security, hardening each cluster component, the Kubernetes threat model, platform security, and compliance and security frameworks.

   Multiple choice90 minutesValid for two years

   My notesOfficial exam page

3. 3

   CKAD: Certified Kubernetes Application Developer

   Passed Sep 2025

   Building and running applications on Kubernetes: pods, deployments, services, configuration, probes, volumes and networking, solved at the command line.

   Hands-on, at the command line2 hoursValid for two years

   My notesOfficial exam page

4. 4

   CKA: Certified Kubernetes Administrator

   Passed Oct 2025

   Running clusters: architecture and installation, workloads and scheduling, services and networking, storage, and troubleshooting. The prerequisite for the CKS.

   Hands-on, at the command line2 hoursValid for two years

   My notesOfficial exam page

5. 5

   CKS: Certified Kubernetes Security Specialist

   Passed Oct 2025

   Securing clusters and workloads: cluster setup and hardening, system hardening, microservice vulnerabilities, supply chain security, and monitoring, logging and runtime security.

   Hands-on, at the command line2 hoursValid for two yearsNeeds the CKA first

   My notesOfficial exam page

How to prepare, from the notes

The advice the notes open with, in short:

1. Memorise the basic commands and syntax, so you are not looking everything up in the documentation during the exam. That costs time.
2. Know the official documentation well enough to know where to find what you need. It is allowed in the hands-on exams, and most of the YAML you need is on a docs page.
3. Memorise the flow of a few long tasks, such as upgrading a node, so you are not working them out under the clock.
4. Back up a config before you change it. A fix that goes wrong can do more damage to the cluster than the task itself.
5. Read the question twice, then keep the solution simple.
6. Use Ctrl+F on the docs page to jump to the snippet you need, and learn a few Vim moves for indenting and deleting blocks. Both save minutes.
7. Before a hands-on exam, take a day or two for the scenario questions at the end of the notes, and use the two Killer Shell sessions that come with the exam.

Back to the DevOps path