CKA Troubleshooting Practice Question
You have a pod that is in 'Pending' state. Which command would you use to view detailed information about the pod's status, including events that may indicate why it is not running?
⚠ Common exam trap
Many candidates assume `kubectl logs` can show startup errors even when the pod has never run, or they confuse `kubectl get` with `kubectl describe`, not realizing that `get` only shows a high-level status without the event history needed for troubleshooting.
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
C is correct because `kubectl describe pod` provides detailed information about the pod's current state, including status conditions, container statuses, and a chronological list of events associated with the pod. These events often contain error messages (e.g., 'FailedScheduling', 'ImagePullBackOff', 'CrashLoopBackOff') that directly explain why the pod is stuck in 'Pending' state, such as insufficient resources or persistent volume claim issues.
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 get endpoints
Why it's wrong here
This command retrieves Endpoint resources, which map Services to the IP addresses of healthy backend Pods. It provides no visibility into the scheduling state, resource requests, or lifecycle events of an unassigned Pod. Because a pending Pod has not been assigned an IP address or associated with an active Endpoint, querying endpoints is completely irrelevant for troubleshooting scheduling failures.
- ✗
kubectl logs pod
Why it's wrong here
This command attempts to fetch the stdout and stderr streams from running containers within a Pod. However, when a Pod is in a Pending state, its containers have not yet been created or started by the kubelet. Attempting to run this command on a Pending Pod will result in an error indicating that the API server cannot fetch logs for unstarted containers.
- ✓
kubectl describe pod
Why this is correct
This is the correct command because it queries the Kubernetes API server for the detailed state, conditions, and event history of the specified Pod. The "Events" section at the bottom of the output will explicitly reveal why the Pod is pending, such as insufficient CPU/memory on nodes, taints and tolerations mismatches, or unbound PersistentVolumeClaims.
- ✗
kubectl get pod
Why it's wrong here
While this command is useful for a quick high-level status check to confirm that the Pod is indeed in a "Pending" state, it only outputs basic metadata like status, restarts, and age. It lacks the diagnostic depth required to troubleshoot the root cause, as it does not display the scheduler's decision-making events or node-matching failures.
Go deeper
Related to this question
Learn chapter
Troubleshooting Cluster and Node Issues
Key term
Pod Failure Troubleshooting
Pod failure troubleshooting is the process of identifying and resolving issues that cause Kubernetes pods to crash, restart, or become unavailable.
Key term
kubectl Command Reference
kubectl is the command-line tool used to interact with and manage Kubernetes clusters by sending commands to the Kubernetes API.
About these practice questions
One of 726 original CKA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.