mediumMultiple ChoiceObjective-mapped
XK0-006 Practice Question: A pod in the Kubernetes cluster is in…
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?
⚠ Common exam trap
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.
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
✓
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.
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.
- ✗
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.
Go deeper
Related to this question
About these practice questions
Courseiva writes every XK0-006 question from scratch — 979 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 XK0-006 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-006 exam.