Question 463 of 997

Kubernetes Fundamentals →mediumMultiple ChoiceObjective-mapped

Pod Pending State — Causes and Troubleshooting

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.

You notice that a pod is in 'Pending' state for a long time. Which of the following is the most likely cause?

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.

A
The pod's liveness probe is failing.
Why wrong: Liveness probe failures cause restarts, not Pending.
B
No node has enough CPU or memory to meet the pod's requests.
Insufficient resources prevent scheduling, leaving the pod Pending.
C
The pod's readiness probe is not configured.
Why wrong: Readiness probe status affects service endpoints, not scheduling.
D
The container image does not exist.
Why wrong: Missing image typically results in ImagePullBackOff, not Pending.

Full breakdown with real-world context →

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

✓

No node has enough CPU or memory to meet the pod's requests.

A pod remains in 'Pending' state when the scheduler cannot find a node that satisfies its resource requests. The most common reason is insufficient CPU or memory capacity across all available nodes, preventing the pod from being bound to a node. Unlike probe failures or missing images, which cause 'Running' or 'ImagePullBackOff' states, resource constraints block scheduling entirely.

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's liveness probe is failing.
Why it's wrong here
Liveness probe failures cause restarts, not Pending.
✓
No node has enough CPU or memory to meet the pod's requests.
Why this is correct
Insufficient resources prevent scheduling, leaving the pod Pending.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The pod's readiness probe is not configured.
Why it's wrong here
Readiness probe status affects service endpoints, not scheduling.
✗
The container image does not exist.
Why it's wrong here
Missing image typically results in ImagePullBackOff, not Pending.

Common exam traps

Common exam trap: answer the scenario, not the keyword

A common exam trap is confusing scheduling failures (Pending) with runtime failures (CrashLoopBackOff, ImagePullBackOff). Candidates often mistake probe or image issues as causes of the Pending state, but these occur after the pod is scheduled.

Detailed technical explanation

How to think about this question

The Kubernetes scheduler uses predicates (e.g., PodFitsResources) to filter nodes that meet the pod's CPU and memory requests defined in the container spec. If no node passes these filters, the pod remains unscheduled and stuck in 'Pending' indefinitely until resources free up or new nodes are added. This can be diagnosed with `kubectl describe pod` to see events like '0/3 nodes are available: 3 Insufficient cpu'.

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.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

KCNA practice-test guide →Study guide →Browse all practice tests

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: No node has enough CPU or memory to meet the pod's requests. — A pod remains in 'Pending' state when the scheduler cannot find a node that satisfies its resource requests. The most common reason is insufficient CPU or memory capacity across all available nodes, preventing the pod from being bound to a node. Unlike probe failures or missing images, which cause 'Running' or 'ImagePullBackOff' states, resource constraints block scheduling entirely.

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". 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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on KCNA

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You run 'kubectl get pods' and see a pod with status 'Pending'. Which is the most likely cause?

medium

A.The pod's container has crashed
✓ B.The scheduler cannot find a node that meets the pod's resource requirements
C.The container image is not found
D.The pod has been deleted by a controller

Why B: A pod with status 'Pending' indicates that the pod has been accepted by the cluster but is not yet running. The most common cause is that the Kubernetes scheduler cannot find a node that satisfies the pod's resource requests (CPU, memory) or other constraints (node selector, taints/tolerations, affinity rules). The scheduler continuously evaluates nodes and if none match, the pod remains in Pending state until a suitable node becomes available.

Keep practising

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.

Loading comments…

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.