KCNA is the CNCF's entry certification, and its subject is the cloud native landscape rather than Kubernetes alone. Kubernetes fundamentals and container orchestration sit alongside cloud native architecture, observability and application delivery, and a substantial part of the exam falls outside core Kubernetes altogether.
The exam expects you to read a Kubernetes manifest and explain what it does, and also to know where the surrounding CNCF tooling fits rather than treating it as one undifferentiated stack. Those ecosystem questions are the part a Kubernetes-only study plan leaves out, and they suit engineers moving toward container platform work who have so far met the orchestrator but not much around it.
The pass mark is set higher than any AWS associate exam and higher than the Azure fundamentals, so on a five-domain paper the margin for one weak area disappears quickly. The exam fee is also high for an entry-level certification, which makes a resit worth going out of your way to avoid.
The 5 KCNA domains
Kubernetes Fundamentals
Container Orchestration
Cloud Native Architecture
Cloud Native Observability
Cloud Native Application Delivery
Kubernetes Fundamentals
12 questions
Question 1 of 25
What is the difference between 'kubectl exec' and 'kubectl attach'?
A.The two commands are functionally identical and can always be used interchangeably
B.kubectl exec is only usable in combination with the --dry-run flag on a live cluster
C.kubectl attach can only be used against Job-managed Pods, never Deployment-managed ones
D.kubectl exec starts a new process inside a running container; kubectl attach connects to the existing main process's consoleCorrect
Answer: D
kubectl exec runs a new command/process inside a container (commonly an interactive shell), while kubectl attach connects your terminal to the stdin/stdout of the container's already-running main process.
Question 2 of 25
By default, before any NetworkPolicy is applied, how do Pods in a cluster communicate?
A.All Pods can communicate with all other Pods, with no restrictionCorrect
B.Only Pods that happen to share the same Namespace are able to communicate
C.No Pods are able to communicate with any other Pod whatsoever
D.Only Pods that share an identical set of labels are able to communicate
Answer: A
Kubernetes networking is non-isolated by default - all Pods can reach all other Pods unless a NetworkPolicy explicitly restricts that traffic.
Question 3 of 25
What is the Kubernetes API server's role in the cluster?
A.It is a component that only handles direct Node-to-Node networking traffic
B.It is a component used exclusively for handling user authentication
C.It is the front end for the control plane, exposing the Kubernetes APICorrect
D.It stores all of the cluster's data directly to disk, without relying on etcd
Answer: C
The kube-apiserver exposes the Kubernetes API and acts as the central point through which all cluster components and users interact.
Question 4 of 25
In a Kubernetes resource request like 'cpu: 500m', what does the 'm' suffix represent?
A.A measurement of milliseconds of delay added to the scheduling process
B.Millicpu - 500m equals half of one CPU coreCorrect
C.A measurement of megabytes allocated specifically to the CPU's own cache
D.A measurement of megahertz describing the CPU's underlying clock speed
Answer: B
CPU resources are measured in cores, with 'm' denoting millicpu (thousandths of a core) - 500m equals 0.5 of a full CPU core.
Question 5 of 25
What does 'kubectl auth can-i --list' show?
A.A list of every RBAC Role defined cluster-wide
B.A list of all Namespaces the cluster currently has
C.A list of all actions the current user is permitted to performCorrect
D.A list of every user who has ever accessed the cluster
Answer: C
kubectl auth can-i --list summarizes the full set of actions/resources the current user is authorized for, useful for auditing what an identity can actually do without testing each permission individually.
Question 6 of 25
What is a headless Service (a Service with 'clusterIP: None')?
A.A Service that has been created without any label selector defined at all
B.A Service whose configuration prevents it from routing any traffic whatsoever
C.A Service that returns the individual Pod IPs directly via DNS instead of a single virtual IPCorrect
D.A Service type that Kubernetes deprecated and no longer supports in current versions
Answer: C
A headless Service skips load-balancing and cluster-IP allocation, instead returning the IPs of individual backing Pods via DNS - commonly used with StatefulSets.
Question 7 of 25
What does setting 'immutable: true' on a ConfigMap or Secret do?
A.Makes the object's data readable by Pods running in every Namespace in the cluster
B.Prevents further updates to its data, protecting against accidental changes and improving API server performanceCorrect
C.Prevents the object from ever being deleted, even by a cluster administrator with full access
D.Encrypts the ConfigMap or Secret's data automatically using the cluster's default KMS provider
Answer: B
Marking a ConfigMap or Secret immutable rejects further updates to its data, which protects against accidental modification and reduces load on the API server from watching it for changes.
Question 8 of 25
Which kubectl command marks a Node as unschedulable ahead of maintenance, without evicting existing Pods?
A.kubectl drain
B.kubectl cordonCorrect
C.kubectl delete node
D.kubectl taint
Answer: B
kubectl cordon marks a Node unschedulable so no new Pods land on it, but leaves already-running Pods in place. kubectl drain goes further and evicts them.
Question 9 of 25
Besides CPU and memory totals, what else can a ResourceQuota limit in a Namespace?
A.How many total days a given Namespace is permitted to continue existing
B.Which specific container images are permitted to be used in that Namespace
C.The count of objects, such as the number of Pods, Services, or PVCs allowedCorrect
D.The maximum number of characters permitted in an object's name field
Answer: C
ResourceQuotas support object-count limits (e.g., pods: 50, services: 10), preventing a Namespace from accumulating unbounded numbers of objects - not just capping compute totals.
Question 10 of 25
What is the purpose of the 'imagePullSecrets' field on a Pod spec?
A.Providing credentials needed to pull container images from a private registryCorrect
B.Restricting which Namespace is permitted to pull a given container image
C.Encrypting a container's image after it has already been pulled onto the Node
D.Explicitly setting the image pull policy that should be applied to a container
Answer: A
imagePullSecrets references a Secret containing registry credentials, allowing kubelet to authenticate when pulling images from a private container registry.
Question 11 of 25
What does setting 'nodeName' directly in a Pod spec do?
A.Assigns the Pod to that specific Node, bypassing the scheduler entirelyCorrect
B.Renames the target Node itself to match the value given in the field
C.Creates only a soft preference the scheduler is still free to disregard
D.Simply adds a descriptive label to the named Node, with no scheduling effect
Answer: A
nodeName is direct node assignment - the scheduler is skipped and kubelet on that Node just runs the Pod. Unlike nodeSelector/affinity, there's no scheduling logic involved at all.
Question 12 of 25
What is the effect of a 'NoExecute' taint on a Node, unlike 'NoSchedule'?
A.It evicts existing Pods that don't tolerate the taint, in addition to blocking new ones from schedulingCorrect
B.It only blocks new Pods from scheduling, behaving identically to a NoSchedule taint
C.It applies exclusively to Pods managed by a DaemonSet, ignoring all other Pods
D.It permanently prevents the tainted Node from ever rejoining the cluster again
Answer: A
NoExecute not only prevents new Pods without a matching toleration from scheduling, it also evicts existing Pods on the Node that don't tolerate it. NoSchedule only blocks new scheduling.
Container Orchestration
4 questions
Question 13 of 25
What advantage does KEDA add over the standard Horizontal Pod Autoscaler using only CPU/memory metrics?
A.It completely removes the need to run a Kubernetes cluster in the first place
B.It is a mechanism that functions only when applied to StatefulSet workloads
C.It can scale based on external event-driven metrics, such as queue length, and can scale a workload down to zeroCorrect
D.It removes any need to define resource requests and limits on a container
Answer: C
Standard HPA scaling on CPU/memory doesn't capture workload demand well for event-driven systems; KEDA lets you scale based on the actual event source (like a queue depth) and can scale replicas down to zero when there's no work.
Question 14 of 25
What does a Deployment's 'revisionHistoryLimit' control?
A.The maximum number of times a given Pod is permitted to restart
B.How many old ReplicaSets are retained to allow rollbackCorrect
C.The maximum total number of Pods that are permitted to run at once
D.The maximum amount of time a rollout is permitted to take before timing out
Answer: B
revisionHistoryLimit sets how many old, scaled-down ReplicaSets are kept around for potential rollback via kubectl rollout undo.
Question 15 of 25
In a manual canary pattern using plain Kubernetes objects, how is traffic split between the stable and canary versions?
A.The scheduler decides how to route traffic based purely on each Node's relative age
B.A special field named 'canary: true' is set directly on the Service object itself
C.Two Deployments share a common label matched by one Service, so traffic distributes roughly by replica ratioCorrect
D.It's only possible after the stable Deployment has been deleted from the cluster
Answer: C
The classic DIY canary: stable (e.g., 9 replicas) and canary (1 replica) Deployments both carry the label the Service selects, giving an approximate 90/10 traffic split by replica count - no mesh required, though meshes make the split precise.
Question 16 of 25
What does minReadySeconds on a Deployment or StatefulSet control?
A.The minimum time a readiness probe itself is allowed to take
B.The minimum time a Pod must exist before it can be deleted
C.The minimum time the scheduler waits before placing a new Pod
D.The minimum time a new Pod must be ready before it's considered available, affecting rollout progressCorrect
Answer: D
minReadySeconds requires a Pod to stay ready for at least that long before it counts toward availableReplicas, preventing a rollout from treating a briefly-ready-then-crashing Pod as successfully rolled out.
Cloud Native Architecture
4 questions
Question 17 of 25
What do SPIFFE and SPIRE provide in cloud native environments?
A.A web-based dashboard for visualizing and managing Kubernetes RBAC role bindings
B.A build system that compiles container images directly from source without a Dockerfile
C.A standard and implementation for issuing cryptographic identities to workloads, enabling secure service-to-service authenticationCorrect
D.A centralized log aggregation pipeline optimized for high-cardinality structured event data
Answer: C
SPIFFE defines a standard for workload identity (SVIDs), and SPIRE is its production implementation - giving each workload a verifiable cryptographic identity instead of relying on network location or shared secrets.
Question 18 of 25
What is 'platform engineering' in a cloud native organization?
A.Building internal platforms and golden paths that let product teams deploy and operate services with less frictionCorrect
B.The engineering discipline focused on designing and manufacturing physical server hardware
C.Writing native mobile applications that target both iOS and Android from one codebase
D.Managing an organization's presence and posting schedule across social media platforms
Answer: A
Platform engineering teams build and maintain internal developer platforms - curated tooling, templates, and self-service infrastructure - so product teams don't each reinvent deployment and operations.
Question 19 of 25
What is an API gateway's typical role in a microservices architecture?
A.A build tool that compiles multiple microservices into a single deployable container image
B.A single entry point that routes, and may handle cross-cutting concerns like auth, for client requests to backend servicesCorrect
C.A Kubernetes-specific component responsible for scheduling Pods onto appropriate Nodes
D.A database connection proxy used exclusively to pool queries between microservices and their datastores
Answer: B
An API gateway sits in front of a set of microservices, providing a unified entry point and often handling routing, authentication, and rate limiting.
Question 20 of 25
What is Helm, in the context of the CNCF landscape?
A.A monitoring system used for collecting and visualizing cluster metrics
B.A general-purpose service mesh used to manage service-to-service traffic
C.A package manager for Kubernetes applicationsCorrect
D.A container runtime responsible for actually creating and running containers
Answer: C
Helm is a package manager for Kubernetes, using Charts to define, install, and upgrade complex Kubernetes applications.
Cloud Native Observability
3 questions
Question 21 of 25
In distributed tracing terminology, what is a 'span'?
A.A single unit of work or operation within a trace, with a start and end timeCorrect
B.A distinct Kubernetes object type used specifically to represent tracing data
C.The total, end-to-end duration of an entire distributed trace from start to finish
D.A metric type native to Prometheus used for recording distributed request counts
Answer: A
A span represents a single operation within a trace, capturing timing and metadata; a trace is composed of one or more related spans.
Question 22 of 25
What problem does Thanos solve for Prometheus deployments?
A.Collecting structured log data instead of the numeric metrics Prometheus normally handles
B.Rendering visual dashboards, a role otherwise handled separately by tools like Grafana
C.Replacing PromQL entirely with a different, incompatible query language
D.Long-term metric storage and a global query view across multiple Prometheus serversCorrect
Answer: D
Prometheus stores data locally with limited retention; Thanos adds durable long-term storage (object storage backed), high availability, and a single query layer spanning many Prometheus instances.
Question 23 of 25
What are commonly referred to as the 'four golden signals' in monitoring, per Google's SRE practices?
A.CPU, memory, disk, and network
B.Latency, traffic, errors, and saturationCorrect
C.Uptime, downtime, MTTR, and MTBF
D.Logs, metrics, traces, and profiles
Answer: B
The four golden signals - latency, traffic, errors, and saturation - are widely cited as the key metrics to monitor for a user-facing system's health.
Cloud Native Application Delivery
2 questions
Question 24 of 25
What is a container image digest, and why pin deployments to one?
A.A cryptographic signature that is only available when pulling from a private registry
B.A brief summary of an image's documentation, automatically generated at build time
C.A content-based sha256 identifier that uniquely and immutably references exact image contents, unlike tags which can be movedCorrect
D.A number representing the image's total file size, measured in bytes, after compression
Answer: C
A digest (e.g., @sha256:...) is derived from the image's actual content - it can never point to different bytes, whereas a tag like :v1.2 can be re-pushed. Digest pinning guarantees you deploy exactly what you tested.
Question 25 of 25
Why are unit tests typically run in the earliest stages of a CI pipeline?
A.They're the only category of test that any CI platform is technically capable of automating
B.They're fast and cheap, so failures are caught before spending time on slower stages like integration tests or buildsCorrect
C.Unit tests require direct production access that earlier pipeline stages don't have
D.Later pipeline stages are architecturally incapable of reporting a test failure back to the developer
Answer: B
Ordering pipeline stages fast-to-slow means the cheapest checks (unit tests, linting) fail first, giving quick feedback and avoiding wasted time on expensive downstream stages for broken changes.
20 more free after signup, then the full 500-question bank for $12.