KCNA Kubernetes Fundamentals Practice Question
You run 'kubectl get pods' and see a pod with status 'Pending'. Which is the most likely cause?
⚠ Common exam trap
The CNCF's KCNA exam often tests the distinction between pod lifecycle phases (Pending, Running, Succeeded, Failed, Unknown) and common error states (CrashLoopBackOff, ImagePullBackOff), so candidates mistakenly associate 'Pending' with image or runtime issues rather than scheduling failures.
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
✓
The scheduler cannot find a node that meets the pod's resource requirements
A pod with status 'Pending' indicates that the pod has been accepted by the cluster but is not yet running. The most common cause is that the Kubernetes scheduler cannot find a node that satisfies the pod's resource requests (CPU, memory) or other constraints (node selector, taints/tolerations, affinity rules). The scheduler continuously evaluates nodes and if none match, the pod remains in Pending state until a suitable node becomes available.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The pod's container has crashed
Why it's wrong here
A crashed container yields CrashLoopBackOff or Error, because the pod was already scheduled to a node. Pending means the scheduler cannot place the pod, typically from insufficient resources or unsatisfied node selectors; container crashes are diagnosed after scheduling succeeds.
- ✓
The scheduler cannot find a node that meets the pod's resource requirements
Why this is correct
A Pending status means the pod has been accepted by the API server but no node has been bound to it. The kube-scheduler assigns pods to nodes, and when no node satisfies the pod's CPU, memory, or affinity constraints, it remains unscheduled and reports Pending.
- ✗
The container image is not found
Why it's wrong here
A missing image produces ErrImagePull or ImagePullBackOff, since the kubelet only pulls images after the pod is bound to a node. Pending indicates the scheduler has not assigned a node, so image availability is irrelevant until scheduling completes.
- ✗
The pod has been deleted by a controller
Why it's wrong here
Deletion removes the pod object entirely, so it no longer appears in kubectl get pods output. Pending reflects a pod that exists but awaits scheduling; controller-driven deletion is relevant when investigating disappearing pods, not ones stuck without a node assignment.
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 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.