The answer is that the application inside the container is crashing repeatedly. This is the most likely cause of a Kubernetes CrashLoopBackOff because the status specifically indicates that a container starts, runs briefly, then exits with a non-zero exit code, triggering Kubernetes to restart it in a loop. When the application crashes faster than Kubernetes can stabilize it, the pod enters this backoff state, incrementally delaying restarts. On the CompTIA Linux+ XK0-005 exam, this question tests your ability to interpret pod statuses and distinguish between infrastructure issues (like resource limits) and application-level failures. A common trap is assuming a misconfigured liveness probe is the root cause, but the probe itself only detects a crash—the underlying application bug or misconfiguration is the true culprit. Memory tip: think of CrashLoopBackOff as the pod saying “I keep trying, but my app keeps dying”—always check the container logs first for the real error.
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.
Exhibit
Refer to the exhibit.
# kubectl get pods -l app=web
NAME READY STATUS RESTARTS AGE
web-0 1/1 Running 0 10m
web-1 1/1 Running 0 10m
web-2 0/1 CrashLoopBackOff 3 5m
# kubectl describe pod web-2
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulled 5m kubelet Container image "web-app:1.0" already present on machine
Normal Created 5m kubelet Created container web
Normal Started 5m kubelet Started container web
Warning BackOff 2m kubelet Back-off restarting failed container
Warning CrashLoopBackOff 1m kubelet CrashLoopBackOff
A pod in the Kubernetes cluster is in CrashLoopBackOff. Based on the exhibit, 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.
Refer to the exhibit.
# kubectl get pods -l app=web
NAME READY STATUS RESTARTS AGE
web-0 1/1 Running 0 10m
web-1 1/1 Running 0 10m
web-2 0/1 CrashLoopBackOff 3 5m
# kubectl describe pod web-2
...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulled 5m kubelet Container image "web-app:1.0" already present on machine
Normal Created 5m kubelet Created container web
Normal Started 5m kubelet Started container web
Warning BackOff 2m kubelet Back-off restarting failed container
Warning CrashLoopBackOff 1m kubelet CrashLoopBackOff
A
The application inside the container is crashing repeatedly.
The CrashLoopBackOff status and BackOff event indicate the application is crashing right after start.
B
The container failed to start because of a missing configuration file.
Why wrong: The container started successfully but then crashed, so it's not a startup failure.
C
The image pull failed due to authentication issues.
Why wrong: There is no ImagePullBackOff event; the image was successfully pulled previously.
D
The container image is not available in the registry.
Why wrong: The event shows the image was already present on the machine, so it's not a pull issue.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The application inside the container is crashing repeatedly.
The CrashLoopBackOff status indicates that a container in a pod is repeatedly crashing after starting. Kubernetes attempts to restart the container, but the application inside exits with a non-zero exit code, causing the restart loop. This is most commonly caused by the application itself crashing due to a bug, misconfiguration, or resource issue.
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 application inside the container is crashing repeatedly.
Why this is correct
The CrashLoopBackOff status and BackOff event indicate the application is crashing right after start.
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 failed to start because of a missing configuration file.
Why it's wrong here
The container started successfully but then crashed, so it's not a startup failure.
✗
The image pull failed due to authentication issues.
Why it's wrong here
There is no ImagePullBackOff event; the image was successfully pulled previously.
✗
The container image is not available in the registry.
Why it's wrong here
The event shows the image was already present on the machine, so it's not a pull issue.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the distinction between container startup failures (ImagePullBackOff, ErrImagePull) and runtime crashes (CrashLoopBackOff), so candidates must remember that CrashLoopBackOff implies the container started at least once before crashing.
Trap categories for this question
Command / output trap
The event shows the image was already present on the machine, so it's not a pull issue.
Detailed technical explanation
How to think about this question
CrashLoopBackOff is a Kubernetes pod status that occurs when a container exits repeatedly (exit code non-zero) and the kubelet's restart policy (e.g., Always) triggers exponential backoff delays between restarts. The backoff delay starts at 10 seconds and doubles up to 5 minutes, resetting after a successful run of at least 10 seconds. This mechanism prevents resource exhaustion from rapid restart loops.
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 practitioner preparing for the XK0-005 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.
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 application inside the container is crashing repeatedly. — The CrashLoopBackOff status indicates that a container in a pod is repeatedly crashing after starting. Kubernetes attempts to restart the container, but the application inside exits with a non-zero exit code, causing the restart loop. This is most commonly caused by the application itself crashing due to a bug, misconfiguration, or resource issue.
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.