How hard is the KCNA exam? +
KCNA is an entry-level exam, but it is not purely conceptual. Kubernetes Fundamentals is 44% of the blueprint, and questions test specific component responsibilities, scheduling behavior, and object relationships. The rest spans container orchestration, cloud native architecture, observability, and application delivery, which can feel overwhelming because it is hard to know how deep to go.
What is the KCNA exam format? +
KCNA is 90 minutes of multiple-choice questions, about 60 in total, delivered online with remote proctoring through the Linux Foundation. Unlike the CKA and CKAD, there is no hands-on command-line component. You need a quiet private room and a system that passes the proctoring check.
What is the KCNA passing score? +
You need 75% to pass. That is a higher bar than the 66% required for the hands-on CKA and CKAD, which surprises some candidates. Because Kubernetes Fundamentals carries 44%, weakness there makes 75% very hard to reach. Results are reported as pass or fail along with your score, typically within 24 hours of finishing the exam.
How much does KCNA cost and how long is it valid? +
KCNA costs 250 USD and includes one free retake within the eligibility window. The certification is valid for two years. There are no prerequisites. The Linux Foundation regularly runs discounts and bundles, so check its training site before paying full price. Your exam must be scheduled and taken within the eligibility window after purchase.
Should I take KCNA before CKA or CKAD? +
KCNA is a sensible first step if you are new to Kubernetes or come from a non-engineering role, since it builds the vocabulary and architecture knowledge the hands-on exams assume. If you already work with Kubernetes daily, many candidates skip KCNA and go straight to CKA or CKAD, which carry more weight with employers.
How long should I prepare for KCNA? +
Candidates new to Kubernetes typically need 4 to 6 weeks. Those with some hands-on experience may need 2 to 3 weeks. Prioritize core objects and architecture, then cover observability, GitOps, service mesh, and CNCF community and governance - the governance topics are easy points technical candidates often skip.