CKA Workloads and Scheduling Practice Question
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?
⚠ Common exam trap
Watch out — candidates often confuse the 'm' suffix with megabytes or a percentage, when in Kubernetes it specifically denotes millicores (1/1000th of a CPU core).
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
✓
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.
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
In Kubernetes, CPU resources are specified in millicores, where 'm' is the unit suffix. A value of 500m precisely denotes 500 millicores, which is equivalent to 0.5 of a full CPU core. This is the standard, absolute measure for CPU requests and limits, ensuring consistent resource allocation across nodes.
- ✗
500 megabytes of memory
Why it's wrong here
The 'm' suffix in the context of CPU resource requests, such as '500m', specifically refers to millicores, not megabytes. Memory resources in Kubernetes are designated using distinct suffixes like 'Mi' for mebibytes or 'Gi' for gibibytes. Confusing these units is a common pitfall, as the same letter can have different meanings depending on the resource type being defined.
- ✗
50% of the node's CPU capacity
Why it's wrong here
Kubernetes CPU requests, like '500m', represent an absolute quantity of CPU time, not a percentage relative to the node's total capacity. This value guarantees the pod access to 0.5 CPU core, irrespective of whether the node has 2, 4, or 8 cores available. While 500m might constitute a certain percentage of a specific node's CPU, the request itself is a fixed, portable resource allocation.
- ✗
A limit of 500,000 CPU seconds per day
Why it's wrong here
Kubernetes does not measure CPU resource allocation in terms of CPU seconds per day. Instead, CPU requests and limits define a share of CPU time within a short scheduling period, typically 100 milliseconds, using the Completely Fair Scheduler (CFS) quotas. This unit of measurement, 500,000 CPU seconds per day, is entirely inconsistent with how Kubernetes manages and throttles CPU resources.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
Key term
Network Policies
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
Key term
Ingress Resources
Ingress Resources are Kubernetes API objects that manage external access to services inside a cluster, typically HTTP and HTTPS traffic, by defining rules for routing requests based on hostnames and paths.
About these practice questions
One of 302 original CKA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.