CKA Troubleshooting Practice Question
Which TWO commands show cluster events that can help in troubleshooting?
⚠ Common exam trap
Many exam-takers confuse `kubectl logs` (which shows container output) with event viewing, or assume `kubectl cluster-info` provides troubleshooting events, when in fact only `kubectl describe` and `kubectl get events` surface the cluster's event history.
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>
Option E, `kubectl get events`, is correct because it directly lists the cluster's event stream (backed by the Events API), showing scheduling failures, image pull errors, probe failures, and other warnings tied to specific resources. Option D, `kubectl describe pod <pod-name>`, is correct because its output includes an Events section at the bottom that surfaces the same per-pod events with timestamps, reasons, and messages, which is essential for troubleshooting a specific pod. Option A, `kubectl cluster-info`, only prints the addresses of the control plane and core add-ons, providing no event data. Option B, `kubectl logs <pod-name>`, shows application/container stdout and stderr, not Kubernetes cluster events. Option C, `kubectl top pods`, reports CPU and memory usage metrics from the metrics server, which is resource data rather than events.
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 cluster-info
Why it's wrong here
kubectl cluster-info displays the URL of the Kubernetes API server and the dashboard (if present), along with component statuses via the /healthz endpoint. It does not retrieve or present Event objects, which are ephemeral records of cluster changes. Therefore, this command cannot help you identify recent pod failures, evictions, or other problem-indicating events.
- ✗
kubectl logs <pod-name>
Why it's wrong here
kubectl logs <pod-name> streams the stdout/stderr output written by the main container(s) within the specified pod. Logs show application-level messages, but Kubernetes Events are a separate API resource recorded by the control plane (e.g., kubelet, scheduler) about state transitions. A container may crash without writing any log output, yet an event would still be generated for the crash loop; thus logs do not expose the troubleshooting event information the question asks about.
- ✗
kubectl top pods
Why it's wrong here
kubectl top pods reports real-time CPU and memory usage metrics for the pods in a namespace, using the metrics pipeline (metrics-server or similar). It is useful for capacity analysis or detecting resource saturation, but it does not list Event objects or describe pod lifecycle transitions. Since events like node pressure, image pull failures, or backoff restarts are not usage metrics, top pods cannot show the cluster events needed for troubleshooting.
- ✓
kubectl describe pod <pod-name>
Why this is correct
kubectl describe pod <pod-name> outputs a comprehensive summary of the pod's configuration and status, culminating in an Events section that chronologically lists recent events for that specific pod (e.g., successful pull, failed schedule, container started). These events often contain the direct cause of a pod problem, making this command one of the two candidates that actually surface events. However, it only shows events for the named pod, so its scope is limited to that Pod object.
- ✓
kubectl get events
Why this is correct
kubectl get events retrieves raw Event API objects from the cluster (or namespace if -n is used) and lists them in a table with fields such as REASON and MESSAGE. This provides a global or namespace-wide view of recent cluster activities, including node, deployment, and pod events. Since it directly queries the event store, it is a reliable way to see cluster events that help in troubleshooting; unlike describe, it does not filter to a single resource.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
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.
Key term
Network Policies
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
About these practice questions
Courseiva writes every CKA question from scratch — 726 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.