- A
spec.containers[].resources.requests.memory only
Why wrong: Requests guarantee a minimum but do not cap; the pod could use more and affect others.
- B
spec.containers[].resources.limits.memory and requests.cpu
Why wrong: requests.cpu is for CPU, not memory; this does not address memory requirements.
- C
spec.containers[].resources.limits.memory only
Why wrong: Limits alone cap usage but do not guarantee a minimum; the pod could be starved if nodes are under pressure.
- D
spec.containers[].resources.requests.memory and limits.memory
Requests guarantee the minimum; limits cap the maximum. If memory exceeds limits, the pod is OOMKilled and restarted.
KCNA Kubernetes Fundamentals Practice Question
This KCNA practice question tests your understanding of kubernetes fundamentals. 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.
A pod is experiencing high memory usage. The administrator wants to enforce that the pod is terminated if it exceeds a memory limit and restarted automatically, but also wants to guarantee a minimum amount of memory for the pod. Which resource specification should be used in the container definition?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"minimum / minimize"Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
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
spec.containers[].resources.requests.memory and limits.memory
Option D is correct because setting both `requests.memory` and `limits.memory` guarantees a minimum memory allocation (the request) while enforcing a hard cap (the limit). If the pod exceeds the memory limit, it is terminated (OOMKilled) and, if part of a Deployment or StatefulSet, the controller automatically restarts it. This satisfies the requirement for both guaranteed minimum and enforced maximum with automatic restart.
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.
- ✗
spec.containers[].resources.requests.memory only
Why it's wrong here
Requests guarantee a minimum but do not cap; the pod could use more and affect others.
- ✗
spec.containers[].resources.limits.memory and requests.cpu
Why it's wrong here
requests.cpu is for CPU, not memory; this does not address memory requirements.
- ✗
spec.containers[].resources.limits.memory only
Why it's wrong here
Limits alone cap usage but do not guarantee a minimum; the pod could be starved if nodes are under pressure.
- ✓
spec.containers[].resources.requests.memory and limits.memory
Why this is correct
Requests guarantee the minimum; limits cap the maximum. If memory exceeds limits, the pod is OOMKilled and restarted.
Clue confirmation
The clue word "minimum / minimize" 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
CNCF often tests the misconception that setting only `limits.memory` is sufficient for both guarantee and enforcement, but without `requests.memory` the pod has no guaranteed minimum and may be evicted under node pressure, failing the 'guarantee a minimum' requirement.
Detailed technical explanation
How to think about this question
Under the hood, when both `requests.memory` and `limits.memory` are set and equal, the pod is placed in the Guaranteed QoS class, which gives it the highest priority for memory and prevents eviction under resource pressure unless it exceeds the limit. If the limit is higher than the request, the pod is in the Burstable class. The OOM killer terminates the process when memory usage exceeds the limit, and the pod's restart policy (default Always) ensures automatic restart by the controller. This is defined in the Kubernetes Resource QoS specification.
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.
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.
- →
Kubernetes Fundamentals — study guide chapter
Learn the concepts, then practise the questions
- →
Kubernetes Fundamentals practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA 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 KCNA question test?
Kubernetes Fundamentals — This question tests Kubernetes Fundamentals — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: spec.containers[].resources.requests.memory and limits.memory — Option D is correct because setting both `requests.memory` and `limits.memory` guarantees a minimum memory allocation (the request) while enforcing a hard cap (the limit). If the pod exceeds the memory limit, it is terminated (OOMKilled) and, if part of a Deployment or StatefulSet, the controller automatically restarts it. This satisfies the requirement for both guaranteed minimum and enforced maximum with automatic restart.
What should I do if I get this KCNA 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: "minimum / minimize". Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
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 →
Last reviewed: Jun 30, 2026
This KCNA practice question is part of Courseiva's free CNCF 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 KCNA 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.