Kubernetes and Cloud Native Associate

KCNA is conceptual, not hands-on. You will not run kubectl in this exam - the questions test that you understand what kubectl, the API server, the scheduler, and the various objects do. Studying for KCNA the way you would study for CKA (drilling kubectl on a live cluster) is overkill and misallocates time. Read the docs and the curriculum bullets thoroughly instead.

Kubernetes Fundamentals is 44% of the exam - by far the largest domain. If your background is non-Kubernetes (e.g. you came from VMs or PaaS), spend the bulk of your study time here: pods, deployments, services, configmaps, secrets, namespaces, the controller pattern, the role of etcd. Everything else builds on these primitives.

Cloud Native Architecture (12%) is the surprise domain. It tests recognition of the CNCF landscape - which projects are graduated, what each one is for, and the broader cloud-native principles (12-factor, immutable infra, GitOps). Most candidates underprepare here because it sounds vague. Skim the CNCF Landscape (landscape.cncf.io) and read the graduated-project list at least once.

Multiple-choice format means distractors matter. Many questions list four similar-sounding answer choices (e.g. four different Service types, four different probe types). The trap is moving fast and clicking the first plausible option. Read every choice before answering - the test writers are good at making the second-best answer look right.

Networking is consistently the hardest 28%-domain topic for first-timers. Memorize the four Service types and what each one creates: ClusterIP (cluster-internal virtual IP), NodePort (opens a port on every node), LoadBalancer (provisions a cloud LB), ExternalName (DNS CNAME, no proxying). Know that kube-proxy is what makes ClusterIP work, and that NetworkPolicy is enforced by the CNI plugin (not by the API server).

Storage questions hinge on two things: access modes and provisioning. Access modes - ReadWriteOnce / ReadOnlyMany / ReadWriteMany / ReadWriteOncePod - and which storage backends support which (block storage = RWO, file storage like NFS = RWX). Provisioning - static (admin pre-creates PV) vs dynamic (StorageClass triggers creation when a PVC binds).

Observability questions love the four golden signals (latency, traffic, errors, saturation) and the three pillars (metrics, logs, traces). Know which CNCF project owns which pillar: Prometheus (metrics), Fluentd / Fluent Bit (logs), Jaeger / OpenTelemetry (traces). OpenTelemetry is increasingly the unified API for all three - this is the modern shape of the answer.

GitOps comes up under Application Delivery. Argo CD and Flux are the two big graduated tools - know that GitOps means 'the desired cluster state lives in git and a controller continuously reconciles toward it', not just 'we use git to store YAML'. The reconciliation loop is the load-bearing concept.

Manage the clock loosely. 90 minutes for a multiple-choice exam (estimated 60 questions based on community reports) is roughly 90 seconds per question - generous. Don't agonize over single questions; flag and come back. If a question is asking about a CNCF project you've never heard of, the answer is usually the one that names a well-known project (Prometheus, Envoy, Linkerd, Helm) over a niche one.

The free retake is a real safety net - use it as one. If you fail by a small margin on attempt 1, treat the gap analysis as the study plan for attempt 2. CNCF deliberately offers the retake because KCNA is positioned as a learning credential, not a gatekeeping one.