CKA Practice Question: Cluster Architecture, Installation and Configuration
Which component is responsible for running containers on a node and reporting their status to the control plane?
⚠ Common exam trap
Many exam-takers confuse the container runtime with the kubelet, because both are involved in running containers, but the kubelet is the agent that reports status to the control plane, while the runtime only executes containers locally.
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 every node in a Kubernetes cluster. It is responsible for ensuring that containers are running in a Pod as expected, by interacting with the container runtime (e.g., containerd) to start, stop, and monitor containers. The kubelet then reports the status of the node and its Pods back to the control plane via the Kubernetes API server, using heartbeats (NodeStatus updates) and Pod status updates.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
kubelet
Why this is correct
As the primary node agent, the kubelet is responsible for ensuring that containers described in PodSpecs are running and healthy on its node. It acts as the bridge between the control plane and the container runtime, translating declarative pod specifications into runtime commands via the Container Runtime Interface (CRI).
- ✗
container runtime (e.g., containerd)
Why it's wrong here
While the container runtime is the low-level engine that actually executes container processes, it does not act as the Kubernetes node agent. It operates under the direct instruction of the kubelet via the Container Runtime Interface (CRI) and does not communicate directly with the Kubernetes API server to manage pod lifecycles.
- ✗
kube-proxy
Why it's wrong here
This component is a network daemon running on each node that maintains network rules to allow communication to your Pods from network sessions inside or outside of your cluster. It does not manage container lifecycles, pull images, or interface with container runtimes to run workloads.
- ✗
kube-scheduler
Why it's wrong here
Operating strictly as a control plane component, this daemon assigns newly created Pods to specific nodes based on resource availability and constraints. It has no presence on individual worker nodes and does not participate in the actual execution or monitoring of containers on those nodes.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
Key term
Container Runtime
A container runtime is software that runs containers by using the host operating system's kernel to isolate processes, manage filesystem layers, and handle networking.
Key term
Network Policies
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
About these practice questions
One of 726 original CKA 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA 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 CKA exam.