CKAD Application Observability and Maintenance Practice Question
Which kubectl command shows detailed information about a pod, including events, labels, and container state?
⚠ Common exam trap
A common mix-up: candidates confuse `kubectl get pod -o yaml` with `kubectl describe pod`, not realizing that `describe` includes the event history and a human-readable state summary that `get -o yaml` omits.
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 my-pod
B is correct because `kubectl describe pod my-pod` provides a comprehensive summary of the pod, including its current state, labels, annotations, conditions, container states (waiting/running/terminated with reasons), and a chronological list of recent events (e.g., pulls, starts, restarts). This makes it the standard command for detailed troubleshooting of a pod's lifecycle and configuration.
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 my-pod
Why it's wrong here
kubectl logs my-pod retrieves only the container's standard output and error streams, which are runtime logs, not pod configuration, status, or scheduling metadata. It lacks any information about the pod's IP address, node, conditions, or events, so it cannot serve as a detailed inspection tool.
- ✓
kubectl describe pod my-pod
Why this is correct
kubectl describe pod my-pod is the correct command because it produces a human-readable, aggregated summary of the pod's configuration, current status, and lifecycle conditions. Crucially, it also displays recent events (e.g., pulls, scheduling, errors) at the bottom, which are essential for diagnosing why a pod is not running as expected.
- ✗
kubectl get pod my-pod -o yaml
Why it's wrong here
kubectl get pod my-pod -o yaml outputs the pod's complete Kubernetes object manifest as YAML, showing the desired spec and current status fields, but it omits cluster-side events because those are stored in separate Event objects. While this is useful for extracting machine-readable details, it is not a concise, human-oriented summary and does not surface event history.
- ✗
kubectl top pod my-pod
Why it's wrong here
kubectl top pod my-pod reports real-time CPU and memory usage metrics for the pod, relying on the metrics server. It focuses solely on resource consumption and performance, providing none of the descriptive details such as labels, annotations, containers, volumes, or event history that would help understand the pod's overall state.
Go deeper
Related to this question
About these practice questions
One of 826 original CKAD 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 CKAD 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 CKAD exam.