This CKA practice question tests your understanding of troubleshooting. 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.
Which TWO of the following are valid methods to troubleshoot a pod that is stuck in 'Pending' state?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Run 'kubectl describe pod <pod-name>' and check the Events section.
A is correct because 'kubectl describe pod <pod-name>' displays the Events section, which includes detailed reasons for a pod being stuck in Pending state, such as insufficient CPU/memory, persistent volume claims not binding, or node selector mismatches. This is the primary diagnostic command for understanding scheduling failures.
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.
✓
Run 'kubectl describe pod <pod-name>' and check the Events section.
Why this is correct
Events show scheduling failures.
Related concept
Read the scenario before looking for a memorised answer.
✗
Run 'kubectl logs <pod-name>' to view application logs.
Why it's wrong here
Logs are for running pods, not pending.
✗
Run 'kubectl exec -it <pod-name> -- /bin/sh' to inspect the container.
Why it's wrong here
Exec requires a running container.
✗
Run 'kubectl top pod <pod-name>' to check resource usage.
Why it's wrong here
Top requires metrics-server and running pod.
✓
Run 'kubectl get events --sort-by=.metadata.creationTimestamp' to see recent cluster events.
Why this is correct
Events include pod scheduling failures.
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 misconception that 'kubectl logs' or 'kubectl exec' can be used on any pod regardless of its lifecycle phase, but these commands require a running container, which does not exist in a Pending pod.
Detailed technical explanation
How to think about this question
The Pending state indicates the pod has been accepted by the API server but not yet scheduled to a node, often due to resource constraints (e.g., insufficient CPU/memory), PersistentVolumeClaim binding failures, or node selector/taint mismatches. The scheduler writes events to the pod's status, visible via 'kubectl describe pod', which includes conditions like 'PodScheduled' set to False with a reason such as 'Unschedulable'. Checking cluster events with 'kubectl get events --sort-by=.metadata.creationTimestamp' (option E) provides a broader view of cluster-wide issues, such as node failures or quota limits, that may indirectly affect scheduling.
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 CKA 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 CKA question in full detail.
Troubleshooting — This question tests Troubleshooting — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Run 'kubectl describe pod <pod-name>' and check the Events section. — A is correct because 'kubectl describe pod <pod-name>' displays the Events section, which includes detailed reasons for a pod being stuck in Pending state, such as insufficient CPU/memory, persistent volume claims not binding, or node selector mismatches. This is the primary diagnostic command for understanding scheduling failures.
What should I do if I get this CKA 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 CKA 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 CKA 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.