KCNA Kubernetes Fundamentals Practice Question
Which kubectl command would you use to view detailed information about a specific pod, including events and container status?
⚠ Common exam trap
CNCF often tests the distinction between `kubectl get` (summary) and `kubectl describe` (detailed with events), expecting candidates to know that only `describe` surfaces the event stream and container state transitions 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 <pod-name>
`kubectl describe pod <pod-name>` provides a comprehensive view of a pod's metadata, spec, status, conditions, container resource usage, and a chronological list of events (e.g., scheduling, pulling images, container restarts). This command aggregates information from the Kubernetes API server, including the pod's current state and lifecycle events, which is essential for debugging pod failures or unexpected behavior.
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 explain pod
Why it's wrong here
kubectl explain documents resource field schemas from the API, not a live pod's events or container statuses. It is the right tool when authoring manifests and needing field definitions, but it never queries cluster state for a named pod.
- ✗
kubectl get pod <pod-name>
Why it's wrong here
`kubectl get pod <pod-name>` returns only summary fields — status phase, restarts, age — from the pod's spec and status, without the event stream or per-container state detail. It is tempting because it is the standard command for listing pods and confirming existence, and would be correct when you only need a quick inventory or health overview.
- ✗
kubectl logs pod <pod-name>
Why it's wrong here
kubectl logs retrieves stdout/stderr from a container, so it shows application output but not pod events, restart reasons or container statuses. It is correct when debugging application errors, not when inspecting pod-level scheduling or lifecycle events.
- ✓
kubectl describe pod <pod-name>
Why this is correct
kubectl describe pod queries the API server for the pod's full status plus associated Events, showing container states, restart counts and scheduling messages. Unlike kubectl get, it surfaces the event stream needed to diagnose why a container is pending or crash-looping.
Go deeper
Related to this question
About these practice questions
One of 930 original KCNA 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 KCNA 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 KCNA exam.