This KCNA practice question tests your understanding of container orchestration. 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 has resource requests of 512Mi memory and 500m CPU, and limits of 1Gi memory and 1 CPU. The node has 4Gi memory and 2 CPU cores. If the pod tries to use 700m CPU, what will happen?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The pod will be allowed to use 700m CPU
The pod's CPU request is 500m, and its CPU limit is 1 CPU (1000m). When the pod attempts to use 700m CPU, it is below the limit of 1000m, so it is allowed to burst up to that amount. Kubernetes uses the CPU request for scheduling and the limit for throttling; since 700m is within the limit, no throttling occurs. The pod is not evicted or terminated because it has not exceeded its memory limit or violated any resource constraints.
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 pod will be throttled to 500m CPU
Why it's wrong here
Throttling occurs only above the limit, not the request.
✓
The pod will be allowed to use 700m CPU
Why this is correct
The pod can use up to the CPU limit (1000m) if the node has capacity.
Related concept
Read the scenario before looking for a memorised answer.
✗
The pod will be evicted from the node
Why it's wrong here
Eviction occurs due to memory pressure or disk pressure, not CPU usage.
✗
The pod will be terminated for exceeding the limit
Why it's wrong here
CPU is compressible; exceeding CPU limit causes throttling, not termination.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse CPU requests with limits, thinking that exceeding the request triggers throttling or eviction, when in fact throttling only occurs at the limit and eviction is tied to memory or node pressure, not CPU usage below the limit.
Detailed technical explanation
How to think about this question
In Kubernetes, CPU is a compressible resource, meaning the kernel uses Completely Fair Scheduler (CFS) quotas to throttle a pod when it exceeds its limit, but the pod is not killed. The CPU request (500m) guarantees that amount, and the limit (1000m) caps the maximum; the pod can burst between request and limit if the node has spare CPU capacity. A real-world scenario is a web server that normally uses 500m CPU but spikes to 700m during traffic bursts—it will run fine as long as the node has available CPU and the limit is not breached.
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 KCNA question in full detail.
Container Orchestration — This question tests Container Orchestration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The pod will be allowed to use 700m CPU — The pod's CPU request is 500m, and its CPU limit is 1 CPU (1000m). When the pod attempts to use 700m CPU, it is below the limit of 1000m, so it is allowed to burst up to that amount. Kubernetes uses the CPU request for scheduling and the limit for throttling; since 700m is within the limit, no throttling occurs. The pod is not evicted or terminated because it has not exceeded its memory limit or violated any resource constraints.
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.
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 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.