The answer is to add limits to the resources section of the container configuration. This is correct because the "container OOM killed" error occurs when the kernel’s Out-Of-Memory killer terminates a process that has exhausted the host’s available memory; by defining memory limits in the container’s resource constraints, you cap its maximum usage, preventing it from starving the node and triggering the OOM killer. On the CompTIA Linux+ XK0-005 exam, this scenario tests your understanding of container resource management and the `--memory` flag in tools like Docker or Podman, often appearing as a troubleshooting question where a container repeatedly crashes under load. A common trap is to assume the fix is increasing host RAM or restarting the container, but those don’t address the root cause of an unconstrained process. Memory tip: think "OOM = Out Of Memory, so add a memory limit to keep it in bounds."
XK0-005 Scripting, Containers and Automation Practice Question
This XK0-005 practice question tests your understanding of scripting, containers and automation. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
$ cat config.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:
- name: nginx
image: nginx
resources:
requests:
memory: "256Mi"
cpu: "250m"
$ kubectl apply -f config.yaml
Error: The Pod "nginx" is invalid: spec.containers[0].resources.limits: Required value: must specify limits for cpu and memory
The sysadmin receives the error shown in the exhibit. What is the most likely fix?
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.
$ cat config.yaml
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:
- name: nginx
image: nginx
resources:
requests:
memory: "256Mi"
cpu: "250m"
$ kubectl apply -f config.yaml
Error: The Pod "nginx" is invalid: spec.containers[0].resources.limits: Required value: must specify limits for cpu and memory
A
Add a readiness probe to the container.
Why wrong: A readiness probe is not related to resource limits.
B
Change the image tag to :latest.
Why wrong: The image tag is not related to the error.
C
Remove the requests section.
Why wrong: Removing requests does not add the required limits.
D
Add limits to the resources section.
The error explicitly requires limits to be specified.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Add limits to the resources section.
The error indicates the container was killed due to an Out Of Memory (OOM) condition. Adding limits to the resources section constrains the container's memory usage, preventing it from exceeding the node's capacity and being terminated by the kernel OOM killer.
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.
✗
Add a readiness probe to the container.
Why it's wrong here
A readiness probe is not related to resource limits.
✗
Change the image tag to :latest.
Why it's wrong here
The image tag is not related to the error.
✗
Remove the requests section.
Why it's wrong here
Removing requests does not add the required limits.
✓
Add limits to the resources section.
Why this is correct
The error explicitly requires limits to be specified.
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 confuse resource requests (which guarantee minimum resources) with limits (which cap usage), and mistakenly think removing requests or adding probes will fix an OOM error, when only a memory limit prevents the container from exhausting node memory.
Detailed technical explanation
How to think about this question
In Kubernetes, the OOM killer is triggered when a container exceeds its memory limit or the node runs out of memory; setting `resources.limits.memory` enforces a hard cap via cgroups. Without limits, containers can burst and starve other processes, leading to unpredictable evictions. Real-world scenarios often involve memory leaks in applications where limits act as a safety valve, and monitoring OOMKilled pod status is key to diagnosing such issues.
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: Add limits to the resources section. — The error indicates the container was killed due to an Out Of Memory (OOM) condition. Adding limits to the resources section constrains the container's memory usage, preventing it from exceeding the node's capacity and being terminated by the kernel OOM killer.
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.