CKAD Application Observability and Maintenance Practice Question
What is the purpose of the 'kubectl describe pod' command?
⚠ Common exam trap
CNCF often tests the distinction between 'describe' (detailed metadata + events) and 'get' (summary or YAML output), so the trap here is confusing 'kubectl describe' with 'kubectl logs' or 'kubectl exec', especially when a pod is failing and candidates instinctively reach for logs instead of first checking events for scheduling or image-related errors.
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
✓
Display detailed information about a pod, including recent events
The 'kubectl describe pod' command retrieves detailed metadata about a specific pod, including its current state, labels, annotations, container specifications, volumes, and a chronological list of recent events (e.g., image pull failures, container restarts, scheduling decisions). This aggregated information is essential for debugging pod lifecycle issues because it surfaces both static configuration and dynamic cluster-level events that are not shown in the pod's YAML manifest or logs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Display detailed information about a pod, including recent events
Why this is correct
kubectl describe pod outputs a detailed, human-readable summary of a pod's current state, including its metadata, spec, status, conditions, container states, restart counts, and, notably, a tail of recent events from the Kubernetes event stream. This event history is essential for debugging because it reveals scheduler decisions, image pull outcomes, and liveness/readiness probe failures that are not visible in the pod's YAML or its logs.
- ✗
Execute a command inside a pod
Why it's wrong here
Running a command inside a pod is the purpose of kubectl exec, not kubectl describe. kubectl exec attaches to a running container to execute a process with its stdin/stdout/stderr forwarded, while kubectl describe merely reads and formats the pod object and its events from the API server without spawning any process or interacting with the container runtime.
- ✗
Display resource usage of a pod
Why it's wrong here
kubectl describe pod does not display live resource usage; that is the job of kubectl top pod, which queries the Metrics API (typically via metrics-server) to report current CPU and memory consumption. While describe does show the pod's resource requests and limits from its spec, it never reports actual usage over time, so it cannot answer 'how much is this pod using right now?'.
- ✗
Show the logs of a pod
Why it's wrong here
Showing the logs of a pod is performed by kubectl logs, which retrieves the output captured by the kubelet from the container's stdout/stderr or configured log files. kubectl describe only shows the pod's declarative configuration and status metadata, such as the node, IP addresses, and conditions, but it never includes any application output or error messages written by the processes inside the pod.
Go deeper
Related to this question
About these practice questions
This CKAD question is part of Courseiva's 826-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 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.