This CKAD practice question tests your understanding of application observability and maintenance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You need to debug a Pod that is in CrashLoopBackOff. Which command should you run first?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Clue: "which command"
Why it matters: Tests specific CLI syntax. Recall the exact command and its required context — near-synonyms and partial matches are common distractors.
kubectl get events --sort-by=.lastTimestamp
Why wrong: Events may show restarts but not the crash reason.
kubectl logs <pod-name>
Logs often contain the error that caused the crash.
kubectl exec -it <pod-name> -- sh
Why wrong: Cannot exec into a crashing container.
kubectl describe pod <pod-name>
Why wrong: Useful but not the first command; logs give more direct crash info.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
kubectl logs <pod-name>
When a Pod is in CrashLoopBackOff, the immediate priority is to see why the container is failing. `kubectl logs <pod-name>` retrieves the container's stdout/stderr output, which typically contains the error message (e.g., missing config, runtime exception, or startup failure). This is the fastest way to get the root cause without modifying the Pod state.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
kubectl get events --sort-by=.lastTimestamp
Why it's wrong here
Events may show restarts but not the crash reason.
kubectl logs <pod-name>
Why this is correct
Logs often contain the error that caused the crash.
Clue confirmation
The clue words "first", "which command" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
kubectl exec -it <pod-name> -- sh
Why it's wrong here
Cannot exec into a crashing container.
kubectl describe pod <pod-name>
Why it's wrong here
Useful but not the first command; logs give more direct crash info.
Common exam traps
CNCF often tests the misconception that `kubectl describe pod` provides enough debugging information, but it only shows the exit code and a brief termination message, not the full application logs that reveal the actual error.
Trap categories for this question
Command / output trap
Events may show restarts but not the crash reason.
Detailed technical explanation
Under the hood, `kubectl logs` reads the container's log file from the node's filesystem (typically /var/log/pods/...), which captures all output written to stdout/stderr by the container's entrypoint. In a CrashLoopBackOff scenario, the container restarts repeatedly, and logs from the previous (failed) run are still available unless the Pod has been evicted or the logs have been rotated. A real-world nuance: if the container uses a logging framework that buffers output, the crash may occur before the buffer is flushed, so logs may be empty; in that case, you might need to add a delay or use `kubectl logs --previous` to see the last terminated container's logs.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A practitioner preparing for the CKAD exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Application Observability and Maintenance — study guide chapter
Learn the concepts, then practise the questions
Application Observability and Maintenance practice questions
Targeted practice on this topic area only
All CKAD questions
991 questions across all exam domains
Certified Kubernetes Application Developer CKAD study guide
Full concept coverage aligned to exam objectives
CKAD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CKAD questions linked to Application Design and Build.
Practise CKAD questions linked to Application Deployment.
Practise CKAD questions linked to Application Environment, Configuration and Security.
Practise CKAD questions linked to Application Observability and Maintenance.
Practise CKAD questions linked to Services and Networking.
Practise CKAD questions linked to CKAD fundamentals.
Practise CKAD questions linked to CKAD scenario.
Practise CKAD questions linked to CKAD troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Application Observability and Maintenance — This question tests Application Observability and Maintenance — Read the scenario before looking for a memorised answer..
The correct answer is: kubectl logs <pod-name> — When a Pod is in CrashLoopBackOff, the immediate priority is to see why the container is failing. `kubectl logs <pod-name>` retrieves the container's stdout/stderr output, which typically contains the error message (e.g., missing config, runtime exception, or startup failure). This is the fastest way to get the root cause without modifying the Pod state.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "first", "which command". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 30, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.