The answer is to use `kubectl logs --previous` because the current container instance in a CrashLoopBackOff state has not yet written any output to stdout before failing. When a pod enters CrashLoopBackOff, the container restarts repeatedly, and running `kubectl logs pod-name` without flags only shows logs from the currently running (or most recent) container—which, having just started and crashed, often produces no output. The previous terminated container, however, may have written critical error messages to stdout before it exited, and those logs are preserved and retrievable with the `--previous` flag. On the CompTIA Linux+ XK0-005 exam, this scenario tests your understanding of Kubernetes log retrieval and container lifecycle states; a common trap is assuming no logs means no errors occurred, when in fact the logs exist but are tied to the terminated instance. Memory tip: think “previous crash, previous logs”—if the current container is silent, look back to the one that actually failed.
XK0-005 Scripting, Containers and Automation Practice Question
This XK0-005 practice question tests your understanding of scripting, containers and automation. 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.
A Kubernetes pod has a container that fails with CrashLoopBackOff. The administrator runs 'kubectl logs pod-name' but sees no output. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The container exited before writing to stdout, and logs need to be retrieved with 'kubectl logs --previous'.
When a container enters CrashLoopBackOff, it restarts repeatedly. If 'kubectl logs pod-name' shows no output, it means the current (restarted) container has not written anything to stdout yet. The previous instance of the container may have written logs before crashing, and those logs are accessible using 'kubectl logs --previous' to retrieve the output from the terminated container.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The container exited before writing to stdout, and logs need to be retrieved with 'kubectl logs --previous'.
Why this is correct
Correct: use --previous to see previous container logs.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The container has no logging driver configured.
Why it's wrong here
Kubernetes uses Docker's logging; it logs by default.
✗
The log file is rotated and deleted.
Why it's wrong here
Log rotation does not cause empty logs on first fetch.
✗
The pod is not scheduled on any node.
Why it's wrong here
Would show Pending status, not CrashLoopBackOff.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume 'no output' means logs are missing or misconfigured, when in fact the current container simply hasn't written anything yet, and the previous container's logs are still available via --previous.
Trap categories for this question
Command / output trap
Would show Pending status, not CrashLoopBackOff.
Detailed technical explanation
How to think about this question
Kubernetes stores container logs in JSON files under /var/log/pods/ on the node, and 'kubectl logs' reads from the current container's stdout stream. The --previous flag retrieves logs from the last terminated container instance, which is critical for debugging crash loops where the container exits before writing to stdout. This behavior is defined by the kubelet's log management and the container runtime interface (CRI), which preserves logs for terminated containers until they are garbage collected.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this XK0-005 question in full detail.
Scripting, Containers and Automation — This question tests Scripting, Containers and Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The container exited before writing to stdout, and logs need to be retrieved with 'kubectl logs --previous'. — When a container enters CrashLoopBackOff, it restarts repeatedly. If 'kubectl logs pod-name' shows no output, it means the current (restarted) container has not written anything to stdout yet. The previous instance of the container may have written logs before crashing, and those logs are accessible using 'kubectl logs --previous' to retrieve the output from the terminated container.
What should I do if I get this XK0-005 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
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 →
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.
This XK0-005 practice question is part of Courseiva's free CompTIA 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 XK0-005 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.