KCNA Container Orchestration Practice Question
A pod is stuck in 'Pending' state. You run 'kubectl describe pod mypod' and see the event '0/4 nodes are available: 4 Insufficient cpu'. What is the most likely cause?
⚠ Common exam trap
A common pitfall is confusing resource 'requests' (used for scheduling) with 'limits' (used for throttling/eviction). Candidates may mistakenly think 'Insufficient cpu' refers to CPU limits being exceeded, rather than the scheduler failing to find a node with enough free CPU to meet the request.
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
✓
None of the nodes have enough CPU resources to satisfy the pod's request
The '0/4 nodes are available: 4 Insufficient cpu' event directly indicates that the Kubernetes scheduler attempted to place the pod on each of the four nodes but found that none had enough allocatable CPU capacity to satisfy the pod's CPU request (specified in the container's `resources.requests.cpu`). This causes the pod to remain in 'Pending' state because the scheduler cannot find a feasible node.
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 has exceeded its memory limit
Why it's wrong here
Exceeding a memory limit triggers OOMKilled and container restarts, visible as Running with restarts or CrashLoopBackOff. The Pending state with 'Insufficient cpu' indicates the scheduler could not place the pod because no node had enough allocatable CPU.
- ✗
The pod's image pull is failing
Why it's wrong here
The event names insufficient CPU across all four nodes, so the scheduler cannot bind the pod; image pull failures surface as ErrImagePull or ImagePullBackOff after scheduling, not as Pending with a CPU event. Image pull troubleshooting applies when a pod is scheduled but its container cannot start.
- ✓
None of the nodes have enough CPU resources to satisfy the pod's request
Why this is correct
The scheduler cannot bind the pod because every node's allocatable CPU is below the pod's requested `resources.requests.cpu`. The event "4 Insufficient cpu" confirms all four nodes failed the CPU predicate during filtering, leaving no feasible node. This directly satisfies the stem's constraint: insufficient CPU capacity across the cluster.
- ✗
The pod's liveness probe is failing
Why it's wrong here
A failing liveness probe causes container restarts and a Running pod with CrashLoopBackOff or restarts, not Pending. The scheduler event names insufficient CPU on all four nodes, so no node satisfies the pod's CPU request. Liveness probes are relevant when diagnosing restart loops.
Go deeper
Related to this question
About these practice questions
One of 930 original KCNA 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 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.