The answer is a memory limit set too low in the pod spec, causing the container to be OOMKilled. This is correct because when a container exceeds its configured memory limit, the kubelet terminates it with an Out of Memory (OOM) error, triggering a restart. Since the application works fine locally—where no such limit exists—the repeated crash and restart cycle in Kubernetes produces the CrashLoopBackOff status, a classic cloud-environment constraint absent in development. On the CompTIA Cloud+ CV0-004 exam, this scenario tests your understanding of how resource quotas differ between local and cloud deployments; a common trap is assuming the issue is code-related rather than environmental. Remember the mnemonic “LOCAL works, CLOUD breaks—check the LIMITS” to quickly isolate memory versus application faults.
CV0-004 Operations and Support Practice Question
This CV0-004 practice question tests your understanding of operations and support. 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 company runs a containerized application on a Kubernetes cluster. The application logs indicate occasional 'CrashLoopBackOff' errors. The developer says the application works fine locally. What is the most likely cause in the cloud environment?
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 memory limit set in the pod spec is too low, causing the container to be OOMKilled.
The 'CrashLoopBackOff' error indicates that the container is repeatedly crashing after startup. Since the application works locally, the issue is likely environmental. A memory limit set too low in the pod spec causes the container to exceed its allowed memory, triggering an OOMKill (Out of Memory Kill) by the kubelet. The container restarts, fails again, and enters CrashLoopBackOff, which is a common cloud-specific resource constraint not present in local development.
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 readiness probe is misconfigured and returning false.
Why it's wrong here
Readiness probe does not cause container restart.
✓
The memory limit set in the pod spec is too low, causing the container to be OOMKilled.
Why this is correct
OOMKill causes container to restart, resulting in CrashLoopBackOff.
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 image is not being pulled correctly from the registry.
Why it's wrong here
Would prevent container from starting.
✗
The persistent volume claim is not bound to a storage class.
Why it's wrong here
Would cause application errors, not crash loop.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CompTIA often tests the distinction between pod statuses: candidates confuse 'CrashLoopBackOff' (container crashes after starting) with 'ImagePullBackOff' (image pull failure) or 'Pending' (resource unavailability), so they incorrectly attribute the error to image or volume issues rather than resource limits.
Detailed technical explanation
How to think about this question
Under the hood, when a container exceeds its memory limit (specified in the pod spec's resources.limits.memory), the Linux kernel's OOM killer terminates the container process. The kubelet then reports the exit code 137 (SIGKILL) and restarts the container based on the restartPolicy. If the memory limit is too low, this cycle repeats, leading to CrashLoopBackOff. A real-world scenario is a Java application with default heap settings that exceed the container's memory limit, causing repeated OOM kills in Kubernetes but running fine on a local machine with ample memory.
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 CV0-004 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.
Operations and Support — This question tests Operations and Support — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The memory limit set in the pod spec is too low, causing the container to be OOMKilled. — The 'CrashLoopBackOff' error indicates that the container is repeatedly crashing after startup. Since the application works locally, the issue is likely environmental. A memory limit set too low in the pod spec causes the container to exceed its allowed memory, triggering an OOMKill (Out of Memory Kill) by the kubelet. The container restarts, fails again, and enters CrashLoopBackOff, which is a common cloud-specific resource constraint not present in local development.
What should I do if I get this CV0-004 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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A cloud engineer deploys the Kubernetes manifest shown in the exhibit. After deployment, the frontend pods are in CrashLoopBackOff state. The engineer checks the logs and finds 'OOMKilled' errors. Which of the following changes would resolve the issue?
medium
✓ A.Increase the memory limit to 1Gi.
B.Increase the number of replicas to 5.
C.Reduce the CPU limit to 250m.
D.Change the service type to ClusterIP.
Why A: The 'OOMKilled' error indicates the container's memory usage exceeded its configured limit, causing the kernel's Out-Of-Memory (OOM) killer to terminate the process. Increasing the memory limit to 1Gi provides the container with more memory headroom, preventing the OOM kill and allowing the pod to run without crashing.
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 CV0-004 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 CV0-004 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.