This KCNA practice question tests your understanding of kubernetes fundamentals. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A pod is stuck in Pending state. Which THREE of the following are possible causes?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The pod specifies a nodeSelector that does not match any node
A pod enters a Pending state when it cannot be scheduled onto a node. A `nodeSelector` constraint requires the node to have specific labels; if no node matches, the scheduler cannot place the pod, leaving it Pending. This is a common scheduling failure cause.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 specifies a nodeSelector that does not match any node
Why this is correct
If no nodes have the required labels, the pod cannot be scheduled.
Related concept
Read the scenario before looking for a memorised answer.
✗
The container image does not exist
Why it's wrong here
Image pull errors typically cause ImagePullBackOff, not Pending.
✓
No node has enough CPU or memory to satisfy the pod's resource requests
Why this is correct
If no node can meet the resource requests, the pod remains unscheduled.
Related concept
Read the scenario before looking for a memorised answer.
✗
The pod has a liveness probe that is failing
Why it's wrong here
Liveness probes are checked after the pod is running, not during scheduling.
✓
A PersistentVolumeClaim used by the pod is not bound
Why this is correct
If a PVC is not bound, the pod will remain Pending until the volume is available.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between scheduling failures (Pending) and runtime failures (CrashLoopBackOff, ImagePullBackOff), so candidates mistakenly attribute image or probe issues to the Pending state.
Detailed technical explanation
How to think about this question
The Kubernetes scheduler uses predicates like nodeSelector, resource requests, and volume binding to filter nodes. If a PersistentVolumeClaim is unbound, the scheduler cannot determine the node's topology constraints (e.g., zone), so it marks the pod as unschedulable. The `kubectl describe pod` command shows events like '0/1 nodes are available: 1 node(s) didn't match node selector' or '1 node(s) had volume node affinity conflict'.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the KCNA exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this KCNA question in full detail.
Kubernetes Fundamentals — This question tests Kubernetes Fundamentals — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The pod specifies a nodeSelector that does not match any node — A pod enters a Pending state when it cannot be scheduled onto a node. A `nodeSelector` constraint requires the node to have specific labels; if no node matches, the scheduler cannot place the pod, leaving it Pending. This is a common scheduling failure cause.
What should I do if I get this KCNA question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.