CKA Troubleshooting Practice Question
You have a pod that is in 'Pending' state. Which command would you run to get more information about why the pod cannot be scheduled?
⚠ Common exam trap
Many exam-takers confuse `kubectl logs` (which only works for running containers) with troubleshooting a pending pod, or they assume `kubectl get events` is the best tool, but the most targeted and efficient command for a single pod's scheduling issue is `kubectl describe pod`.
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
✓
kubectl describe pod <pod-name>
`kubectl describe pod <pod-name>` provides detailed information about the pod, including events, conditions, and scheduler-related messages. For a pod stuck in 'Pending', the 'Conditions' and 'Events' sections will reveal scheduling failures such as insufficient resources, node selector mismatches, or taint toleration issues, which are not visible in logs or basic status output.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
kubectl logs <pod-name>
Why it's wrong here
Since a pending pod has not yet been scheduled or started its containers, no container logs exist to retrieve. Running this command will result in an error indicating that the container is not in a running or completed state, making it useless for diagnosing scheduling bottlenecks.
- ✗
kubectl get events
Why it's wrong here
While this command retrieves cluster-wide events, it outputs a noisy, unfiltered stream of events from all namespaces and resources. Locating the specific scheduling failure for your target pod in a busy cluster is highly inefficient compared to targeted resource inspection.
- ✗
kubectl get pod <pod-name> -o wide
Why it's wrong here
The -o wide output format merely appends columns for the assigned node name, node IP, and readyness gates to the standard pod list. Because a pending pod has not yet been assigned to a node, these fields will remain blank or incomplete, offering no diagnostic clues about why scheduling failed.
- ✓
kubectl describe pod <pod-name>
Why this is correct
This command queries the Kubernetes API server for the complete state of the pod and appends a dedicated Events section at the bottom. This section explicitly details scheduler decisions, such as insufficient CPU/memory, taints and tolerations mismatches, or node selector conflicts that are keeping the pod in a pending state.
Go deeper
Related to this question
About these practice questions
This CKA question is part of Courseiva's 726-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.