CKA Troubleshooting Practice Question
A pod is in ImagePullBackOff state. Which command can you run to get more details about the underlying error?
⚠ Common exam trap
Many candidates confuse `kubectl logs` (which shows application output) with `kubectl describe` (which shows pod lifecycle events and container runtime errors), leading them to choose A when the container never started to produce logs.
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
The `kubectl describe pod` command provides detailed information about the pod, including its status, conditions, events, and container states. For an `ImagePullBackOff` error, the output will include the exact error message from the container runtime (e.g., 'Failed to pull image', 'manifest not found', or 'unauthorized'), which is essential for diagnosing the root cause.
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 pod
Why it's wrong here
kubectl logs reads stdout from a container that has started; an ImagePullBackOff pod never pulled its image, so no container exists to produce logs. It is tempting because logs are the usual first diagnostic, but they would be correct for a CrashLoopBackOff pod whose container starts then exits.
- ✗
kubectl get events --field-selector involvedObject.name=pod
Why it's wrong here
kubectl get events lists cluster events, but the field selector involvedObject.name matches only the object name, not its namespace, so it can return events for same-named pods elsewhere. It is tempting because events do record pull failures; kubectl describe pod is the correct choice, showing the pod's own events and image error.
- ✓
kubectl describe pod
Why this is correct
The kubectl describe pod command retrieves the pod's events and status conditions, which include the specific image pull failure reason and message. This satisfies the stem's need for underlying error detail that kubectl get pod alone does not expose.
- ✗
kubectl top pod
Why it's wrong here
kubectl top pod reports CPU and memory consumption from the metrics API, which requires a running pod; an ImagePullBackOff pod has no container consuming resources. It is tempting as a diagnostic command, but it would be the right choice for investigating resource usage or performance, not image pull failures.
Go deeper
Related to this question
Key term
Container Runtime
A container runtime is software that runs containers by using the host operating system's kernel to isolate processes, manage filesystem layers, and handle networking.
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
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.