This CKA practice question tests your understanding of workloads and scheduling. 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 with a resource request of 500m CPU and a limit of 1 CPU is scheduled. The node has a CPU capacity of 2 cores. What does the '500m' represent?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
500 millicores (0.5 CPU core)
In Kubernetes, CPU resources are measured in millicores, where 1000m equals 1 full CPU core (vCPU or hyperthread). The '500m' in a resource request means the pod is guaranteed at least 500 millicores, or 0.5 CPU core, from the node's 2-core capacity. This is a standard unit used by the kubelet for CPU scheduling and the Completely Fair Scheduler (CFS) quota enforcement.
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.
✓
500 millicores (0.5 CPU core)
Why this is correct
CPU requests and limits are defined in millicores; 1000m = 1 core.
Related concept
Read the scenario before looking for a memorised answer.
✗
500 megabytes of memory
Why it's wrong here
The 'm' suffix here stands for millicores, not megabytes. Memory is expressed in Mi or Gi.
✗
50% of the node's CPU capacity
Why it's wrong here
It is an absolute value, not a percentage. However, 500m on a 2-core node would be 25% of the node's CPU.
✗
A limit of 500,000 CPU seconds per day
Why it's wrong here
This is incorrect. Kubernetes does not measure CPU in seconds per day.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the 'm' suffix with megabytes or a percentage, when in Kubernetes it specifically denotes millicores (1/1000th of a CPU core).
Detailed technical explanation
How to think about this question
Under the hood, the kubelet converts CPU requests and limits into CFS quota and period values in the cgroup. For a limit of 1 CPU (1000m), the kernel sets cpu.cfs_quota_us to 100000 and cpu.cfs_period_us to 100000, meaning the pod can use up to 100ms of CPU time per 100ms period. The '500m' request ensures the pod is scheduled with a weight that guarantees at least 50ms per period under contention. In real-world scenarios, setting requests too low can cause CPU throttling even if the node has idle cores, because the CFS quota is strictly enforced.
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 CKA 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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this CKA question in full detail.
Workloads and Scheduling — This question tests Workloads and Scheduling — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: 500 millicores (0.5 CPU core) — In Kubernetes, CPU resources are measured in millicores, where 1000m equals 1 full CPU core (vCPU or hyperthread). The '500m' in a resource request means the pod is guaranteed at least 500 millicores, or 0.5 CPU core, from the node's 2-core capacity. This is a standard unit used by the kubelet for CPU scheduling and the Completely Fair Scheduler (CFS) quota enforcement.
What should I do if I get this CKA 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 CKA 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 CKA 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.