CKAD Practice Question: Application Environment, Configuration and Security
A pod is in Pending state. 'kubectl describe pod' shows '0/1 nodes are available: 1 Insufficient cpu'. Which action would resolve this?
⚠ Common exam trap
The CKAD exam often tests the distinction between CPU requests and limits, where candidates mistakenly think increasing limits or deleting/recreating the pod will fix scheduling issues, but only adjusting the request (or adding more nodes) resolves 'Insufficient cpu' errors.
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
✓
Reduce the CPU request in the container's resource spec
The pod is in Pending state because no node has enough allocatable CPU to satisfy the container's CPU request. Reducing the CPU request in the container's resource spec lowers the amount of guaranteed CPU the scheduler requires, making it possible to schedule the pod on a node with insufficient CPU capacity. This directly resolves the 'Insufficient cpu' condition shown in 'kubectl describe pod'.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Reduce the CPU request in the container's resource spec
Why this is correct
Scheduling decisions in Kubernetes are based on resource requests, not limits. Your pod remains Pending because no node in the cluster has enough unallocated CPU to satisfy the container's requested amount. Reducing the CPU request lowers the pod's scheduling footprint, allowing the scheduler to fit it onto a node whose remaining allocatable CPU is smaller, resolving the Pending state.
- ✗
Increase the CPU limit of the container
Why it's wrong here
Raising the CPU limit does not help because limits are ignored during the pod placement process—only the request is compared against node allocatable capacity. Since your request is unchanged, the pod will still fail the node fit check and stay Pending. If your limit and request are not set separately, increasing the limit can inadvertently increase the request, making the shortage worse.
- ✗
Delete and recreate the pod
Why it's wrong here
The Pending state is not a transient failure; it reflects a deterministic insufficiency of node CPU resources. Deleting and recreating the pod without altering its resource requests produces a new pod with the identical request, so the scheduler will again be unable to find a node with enough free CPU. Recreation only helps if the offending issue was a taint or a transient quota, neither of which applies here.
- ✗
Add more environment variables
Why it's wrong here
Environment variables are runtime input passed into the container process and have no connection to the scheduler's resource model. They neither increase node capacity nor reduce the CPU request that governs admission, so the pod remains Pending for the same reason. Pod scheduling is determined solely by resource requests, node selectors, affinity rules, and similar placement constraints.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every CKAD question from scratch — 826 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 CKAD 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 CKAD exam.