An application has two components: `frontend` and `backend`. For low latency, frontend Pods should be on the same node as backend Pods, but if that's not possible, they should be on the same rack. The cluster has nodes labeled with `rack` and `kubernetes.io/hostname`. The backend Pods are labeled `app=backend`. Which podAffinity configuration best meets this requirement?

One preferred podAffinity term with topologyKey `kubernetes.io/hostname` matching `app=backend`.

Two preferred podAffinity terms: one with topologyKey `kubernetes.io/hostname` and one with topologyKey `rack`, both matching `app=backend`.

Two required podAffinity terms: one with topologyKey `kubernetes.io/hostname` and one with topologyKey `rack`, both matching `app=backend`.

One required podAffinity term with topologyKey `kubernetes.io/hostname` matching `app=backend`.

What is the function of the nodeSelector field in a Pod spec?

It specifies which nodes the Pod can tolerate taints from.

It constrains the Pod to be scheduled only on nodes that have all the specified label key-value pairs.

It defines the order in which nodes are considered for scheduling.

It sets the priority of the Pod relative to other Pods.

A cluster administrator wants to ensure that all Pods created in a specific namespace have a CPU limit set, even if the developer forgets to specify one. They also want to reject any Pod that requests more than 4 CPUs. Which admission controller configuration should they use?

Enable the LimitRanger admission controller and create a LimitRange with default and max values.

Enable the ResourceQuota admission controller and create a ResourceQuota with limits.cpu: 4.

Enable the MutatingAdmissionWebhook and create a webhook that injects a CPU limit of 4.

Enable the PodSecurity admission controller and set a policy that requires CPU limits.

A namespace is shared by multiple teams. The platform team wants to prevent any single team from consuming more than 8 CPU cores and 16Gi of memory in total across all Pods in the namespace. They also want to ensure that each Pod requests at least 100m CPU. Which objects should they create?

A LimitRange with `max.cpu: 8`, `max.memory: 16Gi`, and a ResourceQuota with `min.cpu: 100m`.

A ResourceQuota with `requests.cpu: 8`, `requests.memory: 16Gi`, and a LimitRange with `min.cpu: 100m`.

A ResourceQuota with `limits.cpu: 8`, `limits.memory: 16Gi`, and a LimitRange with `default.cpu: 100m`.

Two ResourceQuotas: one with `requests.cpu: 8` and another with `requests.memory: 16Gi`, and a LimitRange with `min.cpu: 100m`.

Certified Kubernetes Administrator (CKA)

Domain 3Objective 5

Configure Pod Admission and Scheduling (limits, Node Affinity, Etc.) CKA Practice Questions (Page 1)

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 1–5

1expert · medium
An application has two components: `frontend` and `backend`. For low latency, frontend Pods should be on the same node as backend Pods, but if that's not possible, they should be on the same rack. The cluster has nodes labeled with `rack` and `kubernetes.io/hostname`. The backend Pods are labeled `app=backend`. Which podAffinity configuration best meets this requirement?
Select an answer first
2foundation · easy
What is the function of the nodeSelector field in a Pod spec?
Select an answer first
3application · medium
A cluster administrator wants to ensure that all Pods created in a specific namespace have a CPU limit set, even if the developer forgets to specify one. They also want to reject any Pod that requests more than 4 CPUs. Which admission controller configuration should they use?
Select an answer first
4application · medium
A namespace is shared by multiple teams. The platform team wants to prevent any single team from consuming more than 8 CPU cores and 16Gi of memory in total across all Pods in the namespace. They also want to ensure that each Pod requests at least 100m CPU. Which objects should they create?
Select an answer first
5foundation · easy
Which field in a Pod spec is used to define node affinity rules?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CKA

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.

Configure Pod Admission and Scheduling (limits, Node Affinity, Etc.) CKA Practice Questions (Page 1)

Questions 1–5

What is the function of the nodeSelector field in a Pod spec?

A cluster administrator wants to ensure that all Pods created in a specific namespace have a CPU limit set, even if the developer forgets to specify one. They also want to reject any Pod that requests more than 4 CPUs. Which admission controller configuration should they use?

A namespace is shared by multiple teams. The platform team wants to prevent any single team from consuming more than 8 CPU cores and 16Gi of memory in total across all Pods in the namespace. They also want to ensure that each Pod requests at least 100m CPU. Which objects should they create?

Which field in a Pod spec is used to define node affinity rules?

Keep studying — Workloads and Scheduling