KCNA Kubernetes Fundamentals Practice Question
A platform engineer runs `kubectl get pods -n web` and sees a pod stuck in the `Pending` phase. The pod's `nodeName` field is empty, and no events about image pulling appear. Which Kubernetes component is most directly responsible for assigning this pod to a node?
⚠ Common exam trap
The trap here is assuming the kube-controller-manager places pods on nodes because it manages replica counts, when node binding is exclusively the kube-scheduler's responsibility.
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
✓
kube-scheduler
A pod enters the Pending phase when it has been accepted by the API server but not yet bound to a node. The kube-scheduler continuously watches for such pods and selects a node that satisfies resource requests, affinity, taints, and tolerations. Once it binds the pod, the kubelet on that node takes over and starts the containers, moving the pod toward Running.
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 it's wrong here
The kubelet is the node agent that receives PodSpecs and ensures containers described in them are running and healthy. It only acts on pods already assigned to its node. A pod with an empty nodeName has not been bound yet, so no kubelet has been instructed to run it, and the kubelet cannot itself assign the pod to a node.
- ✓
kube-scheduler
Why this is correct
The kube-scheduler watches for newly created pods that have no node assigned, then selects a suitable node based on resource requests, affinity rules, taints, and other constraints. Because the pod has an empty nodeName and is not yet running, the scheduler is the component that must bind it to a node before the kubelet on that node can start it.
- ✗
kube-controller-manager
Why it's wrong here
The kube-controller-manager runs control loops such as the Deployment, ReplicaSet, and Node controllers. It ensures the desired number of pod replicas exists and reacts to node failures, but it does not choose which node a pod runs on. Node selection is the scheduler's job, so this component does not resolve a pod stuck without a node assignment.
- ✗
kube-proxy
Why it's wrong here
kube-proxy maintains network rules on nodes to implement Service abstraction, forwarding traffic to the correct backend pods. It operates after pods are scheduled and running, and it has no role in placing pods on nodes. A Pending pod with no node assignment is not affected by kube-proxy's networking rules, so it is not the responsible component.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
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.