
Certified Kubernetes Administrator (CKA)
Domain 3Objective 5
Configure Pod Admission and Scheduling (limits, Node Affinity, Etc.) CKA Practice Questions (Page 5)
Part of the Workloads and Scheduling domain, which accounts for 15% of the CKA exam. Linux Foundation does not publish an official question count, but from its 120-minute exam (~50–80 total, ~8–12 in this domain), expect 2–2 from this objective — we provide 29 practice questions to prepare you well beyond it. (estimate)
29questions here
6free pages
10concepts
15%of the exam
Questions 21–25
- 21
A cluster has dedicated nodes for a critical database. These nodes are tainted with `db=critical:NoSchedule`. A database Pod is deployed with a toleration for this taint. However, the Pod is not being scheduled; it remains Pending. The scheduler logs show that the Pod is being rejected due to insufficient resources on the tainted nodes. What is the most likely cause?
Select an answer first - 22
Which component is responsible for selecting a node for a Pod in Kubernetes?
Select an answer first - 23
A workload must run on nodes that are part of a specific availability zone, `zone-a`. The nodes are labeled `topology.kubernetes.io/zone=zone-a`. The administrator wants to ensure the Pod is scheduled only on those nodes. Which configuration should be used?
Select an answer first - 24
A namespace has a LimitRange that sets a default CPU request of 250m and a default CPU limit of 500m. A developer creates a Pod with a container that specifies only `resources.limits.cpu: 1`. What will be the effective CPU request and limit for the container?
Select an answer first - 25
A namespace has a LimitRange that sets `max.cpu: 2` and `default.cpu: 500m`. A developer creates a Pod with a container that specifies `resources.limits.cpu: 3`. What happens when the Pod is created?
Select an answer first
Finished these 5 questions?
Review the revealed explanations, or continue through the curriculum.
Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Linux Foundation. “CKA” is a trademark of its owner, used for identification only.