- A
The cluster does not have enough resources (CPU/memory) to schedule the additional pods
If nodes lack sufficient resources, new pods remain Pending until resources become available or are released.
- B
The Deployment's YAML has a syntax error
Why wrong: A syntax error would cause the 'kubectl apply' to fail; it would not result in a partially created Deployment.
- C
The container image is not available on the worker nodes
Why wrong: An unavailable image would cause ImagePullBackOff or ErrImagePull, not Pending.
- D
The kubelet on the node is not running
Why wrong: If kubelet were down, the pod would show as Unknown or NodeLost, not Pending.
KCNA Kubernetes Fundamentals Practice Question
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 developer creates a Deployment with 3 replicas. The developer runs 'kubectl get pods' immediately after creation and sees that only 1 pod is in Running state, and the other 2 are Pending. What is the most likely reason for this?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Clue:
"immediately / without restart"Why it matters: Time or reboot constraint — the correct answer must take effect right away without requiring a reboot or reload.
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 cluster does not have enough resources (CPU/memory) to schedule the additional pods
When a Pod remains in Pending state, it indicates that the scheduler cannot find a suitable node to place it. The most common cause is insufficient cluster resources (CPU or memory) to accommodate the additional Pods, as the scheduler checks node allocatable resources against Pod resource requests. With 2 out of 3 Pods pending, the cluster likely has enough resources for only one replica, leaving the others unscheduled.
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 cluster does not have enough resources (CPU/memory) to schedule the additional pods
Why this is correct
If nodes lack sufficient resources, new pods remain Pending until resources become available or are released.
Clue confirmation
The clue words "most likely", "immediately / without restart" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The Deployment's YAML has a syntax error
Why it's wrong here
A syntax error would cause the 'kubectl apply' to fail; it would not result in a partially created Deployment.
- ✗
The container image is not available on the worker nodes
Why it's wrong here
An unavailable image would cause ImagePullBackOff or ErrImagePull, not Pending.
- ✗
The kubelet on the node is not running
Why it's wrong here
If kubelet were down, the pod would show as Unknown or NodeLost, not Pending.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between Pod lifecycle phases — Pending means scheduling failure, not image or runtime issues — so candidates mistakenly associate Pending with image pull errors or node problems rather than resource insufficiency.
Trap categories for this question
Command / output trap
If kubelet were down, the pod would show as Unknown or NodeLost, not Pending.
Detailed technical explanation
How to think about this question
The Kubernetes scheduler uses predicates and priorities to assign Pods to nodes. When a Pod is Pending, it means the scheduler has evaluated all nodes and found none satisfying the Pod's resource requests (spec.containers[].resources.requests) or other constraints like nodeSelector or taints. The scheduler logs events like '0/3 nodes are available: 3 Insufficient cpu' which can be viewed with 'kubectl describe pod <pod-name>'. In real-world scenarios, this often happens during burst scaling when cluster autoscaler hasn't provisioned new nodes yet.
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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Kubernetes Fundamentals — study guide chapter
Learn the concepts, then practise the questions
- →
Kubernetes Fundamentals practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this KCNA question test?
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 cluster does not have enough resources (CPU/memory) to schedule the additional pods — When a Pod remains in Pending state, it indicates that the scheduler cannot find a suitable node to place it. The most common cause is insufficient cluster resources (CPU or memory) to accommodate the additional Pods, as the scheduler checks node allocatable resources against Pod resource requests. With 2 out of 3 Pods pending, the cluster likely has enough resources for only one replica, leaving the others unscheduled.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely", "immediately / without restart". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Last reviewed: Jun 30, 2026
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.