SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
KCNA · Domain 1

Kubernetes Fundamentals practice questions

Kubernetes Fundamentals is worth 44% of the KCNA exam — the heaviest of the 4 domains. The Kubernetes object model, cluster administration, scheduling, and containerization. Official weighting 44%. 6 fully worked examples are further down this page, answers included.

Exam weight
44%
the heaviest of the 4 domains
Questions
162
across 4 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 4 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Kubernetes Fundamentals questions, fully explained

Questions from the KCNA bank mapped to domain 1, with the answer key and the reasoning behind every option. None of them repeat the examples on the main KCNA practice page.

Question 1Kubernetes Fundamentals

Which Kubernetes component is the only one that reads from and writes to etcd directly?

Choose one.

  • a
    kubelet

    The kubelet reports Pod and node status to the kube-apiserver over the API. It has no direct access to etcd.

  • b
    kube-controller-manager

    Controllers watch and update objects through the kube-apiserver. They never open a connection to etcd themselves.

  • c
    kube-proxy

    kube-proxy watches Service and endpoint information via the API server to program network rules. It does not talk to etcd.

  • d
    kube-apiserver Correct

    By design, the kube-apiserver is the only component with a direct connection to etcd. All other components read and write cluster state through the API server.

The concept

etcd is the cluster's source of truth, but access to it is deliberately funneled through a single component: the kube-apiserver.

Why that’s the answer

Centralizing etcd access in the API server means authentication, authorization, admission control, and validation happen in exactly one place before any state changes. The controller manager and kubelet are plausible distractors because they constantly read and update state, but they always do so via API requests - if they wrote to etcd directly, they would bypass every security and validation layer.

How to reason it out
  1. A component or user submits a change through the Kubernetes API.
  2. The kube-apiserver validates the request and authorizes the caller.
  3. The kube-apiserver alone persists the resulting object into etcd.

Exam tip: Only kube-apiserver talks to etcd - every other component goes through the API server.

Kubernetes Core Concepts: Architecture, Pods, Deployments, and Services — the lesson that teaches this.

Question 2Kubernetes Fundamentals

Which description matches the job etcd does in Kubernetes?

Choose one.

  • a
    Caches container images close to nodes so Pods start faster

    Images are pulled from a container registry by the container runtime on each node. etcd holds no images.

  • b
    Stores every API object as consistent key-value data Correct

    etcd is the consistent, distributed key-value store behind the API server. Every object you create - Pods, Deployments, Services, Secrets - is persisted there.

  • c
    Spreads Service traffic across the healthy backend Pods

    That is the Service data path, implemented by kube-proxy rules on each node. etcd is not in the traffic path.

  • d
    Picks the node on which each newly created Pod will run

    Node selection is the kube-scheduler's job. The scheduler records its decision through the API server, which stores it in etcd, but etcd makes no decisions.

The concept

etcd is the consistent, distributed key-value store that holds the whole cluster state. The API server is the only component that reads and writes it.

Why that’s the answer

etcd is the cluster's single source of truth: every API object is stored there as key-value data, which is why backing up etcd is how you back up a cluster. Placement (the scheduler), traffic distribution (kube-proxy) and image distribution (registries and the runtime) are other components' jobs; etcd only stores the records those jobs produce.

How to reason it out
  1. Recall that etcd is a datastore, not an active controller.
  2. Rule out options that make decisions or move traffic or images.
  3. Pick the option that describes persistent storage of API objects.

Exam tip: etcd stores the cluster state; it does not schedule, route or run anything.

Kubernetes Core Concepts: Architecture, Pods, Deployments, and Services — the lesson that teaches this.

Question 3Kubernetes Fundamentals

What does kube-scheduler do when a new Pod is created without a node assigned?

Choose one.

  • a
    Tells the container runtime on a node to start the Pod's containers

    Starting containers is the kubelet's job: it sees the Pod bound to its node and instructs the container runtime.

  • b
    Records the new Pod object in the cluster's key-value datastore

    The kube-apiserver persists the Pod to etcd when it is created, before the scheduler ever sees it.

  • c
    Chooses a feasible node for the Pod and binds the Pod to that node Correct

    The scheduler filters out nodes that cannot run the Pod, scores the rest, and binds the Pod to the best node through the API server. That is all it does.

  • d
    Restarts the Pod's containers on its node whenever they crash

    Container restarts follow the Pod's restartPolicy and are carried out by the kubelet on the node, not the scheduler.

The concept

The kube-scheduler watches for Pods with no node assigned, filters and scores nodes, and binds each Pod to one. It only makes the placement decision.

Why that’s the answer

The scheduler's output is a binding of Pod to node, written through the API server. The tempting distractor is starting the containers, but that happens afterwards: the kubelet on the chosen node notices the bound Pod and asks the container runtime to run it. Persisting the Pod is the API server's job, and restarting crashed containers is the kubelet's.

How to reason it out
  1. Separate deciding from doing: the scheduler decides where.
  2. The kubelet on the chosen node does the starting and restarting.
  3. The API server stores the object; the scheduler only adds the node binding.

Exam tip: kube-scheduler picks the node; the kubelet runs the Pod there.

Kubernetes Core Concepts: Architecture, Pods, Deployments, and Services — the lesson that teaches this.

Question 4Kubernetes Fundamentals

Which component runs on every node and makes sure the containers described in each Pod assigned to that node are actually running, by instructing the container runtime?

Choose one.

  • a
    kube-controller-manager

    The controller manager runs cluster-level control loops on the control plane. It does not run on every node or talk to the container runtime.

  • b
    kube-proxy

    kube-proxy also runs on every node, but it manages network rules for Services. It never starts or manages containers.

  • c
    etcd

    etcd is the control plane's datastore. It stores Pod definitions but plays no part in running containers on nodes.

  • d
    kubelet Correct

    The kubelet is the node agent. It watches for Pods assigned to its node and drives the container runtime to start, monitor, and restart their containers.

The concept

The kubelet is the primary node agent in Kubernetes: it turns Pod specifications into running containers by working with a container runtime (via the Container Runtime Interface).

Why that’s the answer

Once the scheduler assigns a Pod to a node, that node's kubelet takes over - pulling images, starting containers through the runtime, running health probes, and reporting status back to the API server. kube-proxy is the classic distractor since it also runs on every node, but its domain is Service networking, not container lifecycle.

How to reason it out
  1. The kubelet sees (via the API server) that a Pod has been assigned to its node.
  2. It instructs the container runtime to pull images and start the Pod's containers.
  3. It continuously monitors the containers and reports Pod status back to the API server.

Exam tip: kubelet is the per-node agent that makes Pods real by driving the container runtime.

Kubernetes Core Concepts: Architecture, Pods, Deployments, and Services — the lesson that teaches this.

Question 5Kubernetes Fundamentals

What is the primary job of kube-proxy on each node?

Choose one.

  • a
    Relaying kubectl requests from users to the cluster's API server

    kubectl talks to the kube-apiserver directly over HTTPS; kube-proxy has nothing to do with client requests to the control plane.

  • b
    Assigning each new Pod an IP address from the node's Pod range

    Pod IP addresses are allocated by the network (CNI) plugin when the Pod sandbox is created, not by kube-proxy.

  • c
    Programming node rules that send Service traffic to backend Pods Correct

    kube-proxy watches Services and their EndpointSlices and programs iptables or IPVS rules on its node, so traffic to a Service's virtual IP reaches one of its backend Pods.

  • d
    Terminating external HTTP traffic and routing it by host and path

    Host- and path-based HTTP routing is done by an Ingress controller or a Gateway API implementation in front of Services, not by kube-proxy.

The concept

kube-proxy runs on every node and implements the Service abstraction: it programs forwarding rules (typically iptables or IPVS) so traffic to a Service's virtual IP is sent to a backend Pod.

Why that’s the answer

Despite its name, kube-proxy does not proxy kubectl traffic and usually does not even pass packets through itself; it configures the node's kernel to forward Service traffic. Pod IP assignment belongs to the CNI plugin, and HTTP host/path routing belongs to an Ingress controller or Gateway, which are the layers candidates commonly mix up with it.

How to reason it out
  1. Recall that a Service has a virtual IP but no process of its own.
  2. Something on every node must translate that virtual IP to Pod IPs.
  3. That is kube-proxy, programming iptables/IPVS rules.

Exam tip: kube-proxy makes Service virtual IPs work on each node; CNI gives Pods IPs; Ingress routes HTTP.

Kubernetes Core Concepts: Architecture, Pods, Deployments, and Services — the lesson that teaches this.

Question 6Kubernetes Fundamentals

Which description fits kube-controller-manager?

Choose one.

  • a
    Runs the etcd members and manages their cluster membership

    etcd members are their own processes (often static Pods). The controller-manager never talks to etcd; it works through the API server.

  • b
    Runs the loops that move each object's observed state toward its spec Correct

    The controller-manager runs the built-in controllers (ReplicaSet, Deployment, node, Job and more) in one process. Each loop compares desired and observed state and acts through the API server.

  • c
    Runs the scheduling logic that assigns each new Pod to a node

    Pod placement is done by the separate kube-scheduler component.

  • d
    Runs on each worker node and starts the containers listed in Pods

    That is the kubelet, the node agent. The controller-manager is a control plane component.

The concept

kube-controller-manager is the control plane process that runs Kubernetes' built-in controllers, each a loop that reconciles observed state toward desired state.

Why that’s the answer

Controllers such as the ReplicaSet, Deployment, node and Job controllers are compiled into one binary, the kube-controller-manager. Each watches objects through the API server and creates, updates or deletes objects to close the gap. Scheduling is a separate component (kube-scheduler), starting containers is the kubelet's job on each node, and etcd is managed outside it.

How to reason it out
  1. Recall the four control plane components: API server, etcd, scheduler, controller-manager.
  2. Match each distractor to its real owner.
  3. The remaining description - reconciliation loops - is the controller-manager.

Exam tip: kube-controller-manager = the built-in reconciliation loops in one process.

Kubernetes Core Concepts: Architecture, Pods, Deployments, and Services — the lesson that teaches this.

What KCNA domain 1 tests, topic by topic

The official exam guide breaks Kubernetes Fundamentals into 4 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published KCNA practice questions per topic in Kubernetes Fundamentals
TopicWhat it coversQuestions
Kubernetes Core ConceptsOfficial KCNA competency (Kubernetes Fundamentals). The Kubernetes architecture and object model: control plane vs worker nodes, the API server and etcd, controllers and desired-state reconciliation, and the core resources (Pods, ReplicaSets, Deployments, Services, namespaces) with declarative configuration.41
AdministrationOfficial KCNA competency. Managing a Kubernetes cluster: kubectl and the API, the cluster components (kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy), role-based access control (RBAC) basics, namespaces, and resource quotas.41
SchedulingOfficial KCNA competency. How the scheduler places Pods onto nodes: resource requests and limits, node selectors, affinity and anti-affinity, taints and tolerations, and scheduling constraints.41
ContainerizationOfficial KCNA competency. Container fundamentals underpinning Kubernetes: images and registries, container runtimes and the Container Runtime Interface (CRI), Open Container Initiative (OCI) standards, and building and running containers.39
Total162

Revise Kubernetes Fundamentals before you drill it

Other KCNA domains

Kubernetes Fundamentals: your questions

Kubernetes Fundamentals is domain 1 of the KCNA exam guide and carries 44% of the scored content — the heaviest of the 4 domains. On a 60-question paper that works out to roughly 26 questions, though CNCF does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official KCNA exam guide.