Question 208 of 510
Scripting, Containers and AutomationhardMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the application inside the container is repeatedly crashing. This is the most likely cause of a CrashLoopBackOff state, which appears in `kubectl get pods` output as a high restart count—typically five or more restarts—combined with a status of CrashLoopBackOff. The kubelet detects that the container’s entrypoint process exits with a non-zero code, restarts it, and then exponentially increases the back-off delay between attempts. On the CompTIA Linux+ XK0-005 exam, this scenario tests your ability to differentiate between application-level failures and infrastructure issues like node resource pressure or network misconfiguration. A common trap is assuming a resource limit is the cause, but CrashLoopBackOff specifically points to the container process failing to stay alive. Remember the mnemonic: “Crash equals code exit, not capacity.”

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
NAME                        READY   STATUS    RESTARTS   AGE
webapp-6b9f5b7c8d-2x7ht    1/1     Running   0          10m
webapp-6b9f5b7c8d-3y8iu    1/1     Running   0          10m
db-7d4f6c8e9f-1a2b3        0/1     CrashLoopBackOff  5   15m

A sysadmin runs the command and sees the exhibit output. What is the most likely cause of the db pod's status?

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.

Question 1hardmultiple choice
Full question →

Exhibit

Refer to the exhibit.

$ kubectl get pods
NAME                        READY   STATUS    RESTARTS   AGE
webapp-6b9f5b7c8d-2x7ht    1/1     Running   0          10m
webapp-6b9f5b7c8d-3y8iu    1/1     Running   0          10m
db-7d4f6c8e9f-1a2b3        0/1     CrashLoopBackOff  5   15m

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 repeatedly crashing.

The pod's status shows a high restart count (e.g., 5+ restarts) in the output of `kubectl get pods`, which is the classic indicator of a CrashLoopBackOff state. This occurs when the container's entrypoint process exits repeatedly, causing the container to crash and be restarted by the kubelet, until the back-off delay increases. The most likely cause is that the application inside the container is repeatedly crashing, not a resource or node 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 container is out of memory.

    Why it's wrong here

    An out-of-memory condition would result in OOMKilled status, not CrashLoopBackOff.

  • The node running the pod is unreachable.

    Why it's wrong here

    Node unreachable would show NodeLost or Unknown status.

  • The pod does not have enough CPU resources.

    Why it's wrong here

    CPU issues typically cause performance degradation, not a crash loop.

  • The application inside the container is repeatedly crashing.

    Why this is correct

    CrashLoopBackOff means the container exits with an error and is being restarted repeatedly.

    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.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse a high restart count with a resource exhaustion issue (OOM or CPU), but the key differentiator is the specific exit code and status message shown in `kubectl describe pod` or `kubectl logs`.

Trap categories for this question

  • Command / output trap

    Node unreachable would show NodeLost or Unknown status.

Detailed technical explanation

How to think about this question

The CrashLoopBackOff state is managed by the kubelet's restart policy (default: Always), which uses an exponential back-off delay (starting at 10s, doubling up to 5 minutes) to prevent rapid restarts from overwhelming the node. The `kubectl describe pod` command reveals the last exit code and reason (e.g., Exit Code 0 for intentional stop, 1 for general error, 137 for SIGKILL), helping distinguish between application crashes and resource kills. In real-world scenarios, a misconfigured health check (liveness probe) can also cause restarts even if the app is healthy, but the high restart count without probe failure logs points to an application crash.

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.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related XK0-005 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free XK0-005 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this XK0-005 question test?

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 repeatedly crashing. — The pod's status shows a high restart count (e.g., 5+ restarts) in the output of `kubectl get pods`, which is the classic indicator of a CrashLoopBackOff state. This occurs when the container's entrypoint process exits repeatedly, causing the container to crash and be restarted by the kubelet, until the back-off delay increases. The most likely cause is that the application inside the container is repeatedly crashing, not a resource or node 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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 25, 2026

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.

Loading comments…

Sign in to join the discussion.

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.