CNCF certifications

Most certification exams ask the candidate to pick the right answer out of four. The CKA seats the candidate at a terminal in front of several running clusters, sets fifteen to twenty tasks whose result either works or does not, allows two hours, and permits the project's own documentation to stay open throughout. The pass mark is 66 per cent. Open documentation narrows what is being tested rather than easing it: the exact field inside a network policy, the flag on a kubeadm command and the shape of a manifest are all a search away, so the marks go to knowing which page holds the answer, reaching it fast and turning it into a working object before the timer runs out. Preparation has to match that shape. Standing up disposable clusters, breaking them deliberately, repairing them against a stopwatch and rehearsing the kubectl shortcuts that write a manifest is the work; reading about Kubernetes prepares nobody for it. In return the certificate proves something narrow and specific: under a proctor and a clock, the holder operated real infrastructure and fixed what was wrong with it.

• Administrators and platform engineers who touch kubectl weekly are the intended candidates, and they often find the format easier than a multiple-choice paper.
• Anyone the Linux command line still slows down should wait. The exam sets no formal entry condition but assumes a confident shell, kubectl, YAML and container basics, and the Linux Foundation grades it as intermediate.
• Developers who deploy onto clusters somebody else maintains are aiming at the wrong exam. CKAD is written for that seat, and the two syllabuses share enough ground that a second credential later needs far less preparation.
• Holders of a cloud platform badge do not have this one. Managed Kubernetes services wrap the same engine in provider machinery the CKA ignores; passing says the holder can run a cluster, not that they can run one on a given cloud's terms.
• Career changers should learn containers before orchestration; an afternoon of searching under exam conditions is a hard way to discover the gap.

Two years, then the exam again

Many vendors keep a credential open in exchange for logged training hours. CNCF does not. The certificate stands for two years and then lapses unless the holder books the exam and passes it again at the keyboard; no continuing-education route exists. The fee includes a retake and two runs of the exam simulator, and eligibility runs for twelve months from purchase. Kubernetes will have moved several releases on by the time of the second sitting, and the task environment tracks the current release, so the exam re-sat is not the exam first taken. Two years is a cycle, not a purchase; the holder who keeps enough cluster work in the role makes the second attempt routine, and the holder who has moved on lets the credential lapse. The current fee and the Kubernetes version of the exam carry their read date on the CKA page.