KCNA Kubernetes Fundamentals Practice Question
A pod is in 'Pending' state for a long time. What is the most likely cause?
⚠ Common exam trap
CNCF often tests the distinction between scheduling failures (Pending) and runtime failures (CrashLoopBackOff, ImagePullBackOff), so the trap here is confusing a pod that cannot be placed on a node with a pod that fails after it starts running.
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 satisfies the pod's resource requests or constraints
A pod remains in 'Pending' state when it has been accepted by the API server but cannot be scheduled onto a node. The most common cause is that the scheduler cannot find a node that meets the pod's resource requests (CPU/memory) or constraints (node selectors, affinity rules, taints/tolerations). Until a suitable node is found, the pod stays in Pending, waiting for scheduling.
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 produces CrashLoopBackOff or Error, since the pod must first be scheduled and started. CrashLoopBackOff is the correct diagnosis when containers repeatedly fail after starting, whereas Pending means the scheduler cannot place the pod on any node.
- ✗
The pod's service endpoint is misconfigured
Why it's wrong here
A misconfigured service endpoint breaks connectivity for an already running pod, producing connection failures rather than Pending. Endpoint troubleshooting applies when traffic cannot reach healthy pods, but Pending indicates the scheduler has not yet bound the pod to a node.
- ✓
The scheduler cannot find a node that satisfies the pod's resource requests or constraints
Why this is correct
The scheduler places pods onto nodes; when no node satisfies resource requests, affinity rules or taints, it leaves the pod unscheduled. That unsatisfied scheduling constraint is the most likely cause of a prolonged Pending state.
- ✗
The container image is invalid
Why it's wrong here
An invalid image causes ImagePullBackOff or ErrImagePull after scheduling succeeds. That is the right diagnosis when the kubelet cannot fetch the image, but Pending occurs earlier, when the scheduler finds no node satisfying resource requests, affinity rules or taints.
About these practice questions
Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.