KCNA Kubernetes Fundamentals Practice Question
You have a Pod that is in 'Pending' state. What is the most likely cause?
⚠ Common exam trap
CNCF often tests the distinction between Pod lifecycle states, and the trap here is confusing 'Pending' (pre-scheduling) with post-scheduling failures like image pull errors or container crashes, which have distinct states (e.g., ImagePullBackOff, CrashLoopBackOff).
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 node is out of CPU or memory resources.
A Pod in 'Pending' state indicates that the scheduler has not yet assigned it to a node. The most common reason is insufficient resources (CPU or memory) on any available node, causing the scheduler to fail to find a suitable node that meets the Pod's resource requests. This is a core scheduling failure in Kubernetes.
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 node is out of CPU or memory resources.
Why this is correct
The scheduler cannot place a pod when no node has sufficient allocatable CPU or memory. Unschedulable pods remain Pending rather than being assigned to a node, making resource exhaustion the most common cause of this state.
- ✗
The application inside the container crashed.
Why it's wrong here
A crashed container process produces CrashLoopBackOff or Error, not Pending, because the kubelet has already scheduled the Pod and started the container. Pending means the scheduler cannot place the Pod, typically from insufficient CPU or memory, an unsatisfied node selector, or an unbound PersistentVolumeClaim.
- ✗
The container image is missing.
Why it's wrong here
A missing image surfaces as ImagePullBackOff or ErrImagePull once the Pod is scheduled to a node, not as Pending. Image availability is tempting because it blocks container start, but Pending means no node has yet accepted the Pod, typically from insufficient resources or unsatisfied affinity.
- ✗
The Service does not have any endpoints.
Why it's wrong here
A Service without endpoints reflects missing or unready backing Pods, not a cause of Pending; the scheduler places Pods independently of Service endpoint population. Endpoint troubleshooting is tempting because Services and Pods are linked, but it diagnoses connectivity failures rather than scheduling.
Go deeper
Related to this question
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.