This KCNA practice question tests your understanding of container orchestration. 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 command is most helpful to diagnose the issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "which command"
Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
kubectl logs my-pod
Why wrong: 'kubectl logs' shows container logs, but the Pod may not have started yet.
kubectl get events
Why wrong: This shows cluster-wide events, but is less focused on the specific Pod.
kubectl describe pod my-pod
This shows events and status conditions that indicate why the Pod is pending (e.g., insufficient resources).
kubectl top pod my-pod
Why wrong: This shows resource usage, but the Pod may not be running.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
kubectl describe pod my-pod
Option C is correct because 'kubectl describe pod my-pod' provides detailed information about the pod's current state, including events, conditions, and resource constraints. When a pod is stuck in 'Pending', it typically means the scheduler cannot place it on a node due to issues like insufficient CPU/memory, persistent volume claims not being bound, or node selector mismatches. The 'describe' command surfaces these specific reasons in the 'Events' section and 'Conditions' field, making it the most direct diagnostic tool.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
kubectl logs my-pod
Why it's wrong here
'kubectl logs' shows container logs, but the Pod may not have started yet.
kubectl get events
Why it's wrong here
This shows cluster-wide events, but is less focused on the specific Pod.
kubectl describe pod my-pod
Why this is correct
This shows events and status conditions that indicate why the Pod is pending (e.g., insufficient resources).
Clue confirmation
The clue word "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
kubectl top pod my-pod
Why it's wrong here
This shows resource usage, but the Pod may not be running.
Common exam traps
CNCF often tests the misconception that 'kubectl logs' is the universal debugging command, but for pending pods, logs are unavailable because containers haven't started, making 'kubectl describe' the correct choice for pre-run failures.
Trap categories for this question
Command / output trap
'kubectl logs' shows container logs, but the Pod may not have started yet.
Detailed technical explanation
Under the hood, the Kubernetes scheduler (kube-scheduler) evaluates predicates and priorities for each pod; when a pod is pending, the scheduler logs a 'FailedScheduling' event with reasons like '0/3 nodes are available: 1 Insufficient cpu, 2 node(s) didn't match node selector'. The 'kubectl describe pod' command retrieves this event from the pod's status and the associated object's metadata, including the 'Conditions' array where 'PodScheduled' is 'False' with a 'Reason' field. In real-world scenarios, a common subtlety is that a pod may be pending due to a PersistentVolumeClaim that is stuck in 'Pending' itself, which 'describe' reveals in the pod's 'Volumes' section.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Container Orchestration — study guide chapter
Learn the concepts, then practise the questions
Container Orchestration 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise KCNA questions linked to Kubernetes Fundamentals.
Practise KCNA questions linked to Container Orchestration.
Practise KCNA questions linked to Cloud Native Architecture.
Practise KCNA questions linked to Cloud Native Observability.
Practise KCNA questions linked to Cloud Native Application Delivery.
Practise KCNA questions linked to KCNA fundamentals.
Practise KCNA questions linked to KCNA scenario.
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Container Orchestration — This question tests Container Orchestration — Read the scenario before looking for a memorised answer..
The correct answer is: kubectl describe pod my-pod — Option C is correct because 'kubectl describe pod my-pod' provides detailed information about the pod's current state, including events, conditions, and resource constraints. When a pod is stuck in 'Pending', it typically means the scheduler cannot place it on a node due to issues like insufficient CPU/memory, persistent volume claims not being bound, or node selector mismatches. The 'describe' command surfaces these specific reasons in the 'Events' section and 'Conditions' field, making it the most direct diagnostic tool.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "which command". Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
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.