KCNA Kubernetes Fundamentals Practice Question
Which component on a worker node is responsible for enforcing the desired state of pods as defined in the pod specification?
⚠ Common exam trap
Many candidates confuse the kubelet's role with the container runtime or kube-scheduler, assuming that running containers automatically enforces the desired state, when in fact the kubelet is the only component that actively reconciles the actual state with the PodSpec.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
kubelet
The kubelet is the primary node agent that runs on each worker node and is responsible for ensuring that containers are running in a pod as specified by the pod's manifest (PodSpec). It continuously monitors pod status and takes corrective actions, such as restarting containers or re-creating pods, to match the desired state defined in the Kubernetes API.
Go deeper
Related to this question
About these practice questions
One of 833 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
8 more ways this is tested on KCNA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which component runs on each worker node and ensures that containers are running as specified in the Pod spec?
easy- ✓ A.kubelet
- B.kube-proxy
- C.kube-scheduler
- D.kube-controller-manager
Why A: The kubelet is the primary node agent that runs on every worker node in a Kubernetes cluster. It receives PodSpec definitions (via the API server or a file) and ensures that the containers described in those PodSpecs are running and healthy. It does this by interacting with the container runtime (e.g., containerd or CRI-O) to start, stop, and monitor containers, and it reports the node and pod status back to the control plane.
Variation 2. Which component on each worker node is responsible for ensuring that containers are running as specified in the Pod manifest?
medium- A.kube-scheduler
- B.container runtime
- ✓ C.kubelet
- D.kube-proxy
Why C: The kubelet is the primary node agent that runs on each worker node. It receives Pod manifests (via the API server or a file) and ensures the containers described in those manifests are running and healthy. It interacts with the container runtime (e.g., containerd) to create, start, and stop containers as needed, continuously reconciling the actual state with the desired state defined in the Pod spec.
Variation 3. Which component runs on every Kubernetes node and ensures that the containers in a pod are running?
medium- A.kube-proxy
- B.kube-scheduler
- ✓ C.kubelet
- D.container runtime
Why C: The kubelet is the primary node agent that runs on every Kubernetes node. It receives PodSpec definitions from the API server and ensures that the containers described in those PodSpecs are running and healthy. It continuously monitors container status and takes corrective actions, such as restarting containers that have failed, making it the correct answer.
Variation 4. Which component runs on every worker node and ensures that containers are running in a Pod as specified in the Pod manifest?
medium- A.kube-controller-manager
- B.container runtime
- ✓ C.kubelet
- D.kube-proxy
Why C: The kubelet is the primary node agent that runs on every worker node in a Kubernetes cluster. It receives Pod specifications (Pod manifests) from the API server, either directly or via the kube-apiserver, and ensures that the containers described in those manifests are running and healthy. It does this by interacting with the container runtime (e.g., containerd or CRI-O) to start, stop, and monitor containers as needed.
Variation 5. Which component runs on every node and is responsible for ensuring that containers are running as specified in Pod manifests?
easy- ✓ A.kubelet
- B.kube-proxy
- C.container runtime
- D.kube-controller-manager
Why A: The kubelet is the primary node agent that runs on every node in a Kubernetes cluster. It is responsible for ensuring that containers described in Pod manifests (typically provided via the API server) are running and healthy. The kubelet does not manage containers directly; instead, it interacts with the container runtime (e.g., containerd, CRI-O) to create, start, and stop containers as specified.
Variation 6. Which component runs on every worker node and is responsible for ensuring that containers are running in a pod as specified in the PodSpec?
easy- A.container runtime
- B.kube-proxy
- ✓ C.kubelet
- D.kube-scheduler
Why C: The kubelet is the primary node agent that runs on every worker node in a Kubernetes cluster. It is responsible for ensuring that containers described in a PodSpec are running and healthy, by interacting with the container runtime (e.g., containerd, CRI-O) to create, start, and monitor pods. The kubelet does not manage containers that were not created by Kubernetes.
Variation 7. Which component runs on every worker node and is responsible for ensuring that containers are running in a pod according to the pod specification?
easy- A.kube-scheduler
- ✓ B.kubelet
- C.container runtime
- D.kube-proxy
Why B: The kubelet is the primary node agent that runs on every worker node in a Kubernetes cluster. It registers the node with the API server, watches for PodSpecs assigned to its node, and ensures the containers described in those PodSpecs are running and healthy. It does this by interacting with the container runtime to create, start, and stop containers as needed, and it reports the node and pod status back to the control plane.
Variation 8. Which of the following is a worker node component responsible for ensuring that containers are running in a pod as specified in the pod's spec?
easy- A.kube-scheduler
- B.kube-proxy
- ✓ C.kubelet
- D.etcd
Why C: The kubelet is the primary node agent that runs on each worker node. It receives PodSpecs (via the API server or a file) and ensures that the containers described in those PodSpecs are running and healthy. It does this by interacting with the container runtime (e.g., containerd or CRI-O) to start, stop, and monitor containers as required.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This KCNA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the KCNA exam.