This CKA practice question tests your understanding of workloads & 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.
You are tasked with ensuring that a critical application runs on a specific node that has dedicated hardware. The node is labeled with 'hw=special'. You want to guarantee that only pods from this application are scheduled on that node, and no other pods can use it. Which scheduling feature should you use?
Why wrong: Taints prevent other pods, but without node affinity the pod might not be forced to that node.
B
Use pod affinity with a requiredDuringSchedulingIgnoredDuringExecution rule
Why wrong: Pod affinity is for co-locating pods, not for forcing pods to specific nodes.
C
Use node affinity with a requiredDuringSchedulingIgnoredDuringExecution rule
Node affinity with a required rule forces the pod to nodes matching the label, and combined with taints/tolerations can achieve exclusivity. It is the primary feature for hard scheduling constraints.
D
Use a nodeSelector with a matchExpressions constraint
Why wrong: A nodeSelector alone does not prevent other pods from using the node.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use node affinity with a requiredDuringSchedulingIgnoredDuringExecution rule
Option C is correct because node affinity with a `requiredDuringSchedulingIgnoredDuringExecution` rule ensures that a pod is scheduled only on nodes matching the specified label (e.g., `hw=special`). This is the appropriate feature to guarantee that only pods from this application are scheduled on that specific node, as it restricts scheduling to that node while also preventing other pods from using it if combined with taints and tolerations. However, to fully prevent other pods from using the node, you must also taint the node; node affinity alone only ensures the pod goes to that node, but does not block other pods.
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.
✗
Use taints and tolerations
Why it's wrong here
Taints prevent other pods, but without node affinity the pod might not be forced to that node.
✗
Use pod affinity with a requiredDuringSchedulingIgnoredDuringExecution rule
Why it's wrong here
Pod affinity is for co-locating pods, not for forcing pods to specific nodes.
✓
Use node affinity with a requiredDuringSchedulingIgnoredDuringExecution rule
Why this is correct
Node affinity with a required rule forces the pod to nodes matching the label, and combined with taints/tolerations can achieve exclusivity. It is the primary feature for hard scheduling constraints.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a nodeSelector with a matchExpressions constraint
Why it's wrong here
A nodeSelector alone does not prevent other pods from using the node.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse node affinity with taints and tolerations, thinking that node affinity alone can prevent other pods from using the node, when in fact it only ensures the pod is placed on the node but does not repel other pods; taints and tolerations are needed for that exclusivity.
Detailed technical explanation
How to think about this question
Node affinity uses the `nodeAffinity` field in the pod spec under `spec.affinity`, with `requiredDuringSchedulingIgnoredDuringExecution` being a hard constraint that the scheduler must satisfy. Under the hood, the scheduler evaluates the `matchExpressions` against node labels during the filtering phase; if no node matches, the pod remains unscheduled. A real-world scenario is when you have GPU nodes labeled with `gpu=true` and you want to ensure only GPU workloads land there, but you must also taint the node with `gpu=true:NoSchedule` to prevent non-tolerating pods from being scheduled, as node affinity alone does not block other pods.
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 & Scheduling — This question tests Workloads & Scheduling — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use node affinity with a requiredDuringSchedulingIgnoredDuringExecution rule — Option C is correct because node affinity with a `requiredDuringSchedulingIgnoredDuringExecution` rule ensures that a pod is scheduled only on nodes matching the specified label (e.g., `hw=special`). This is the appropriate feature to guarantee that only pods from this application are scheduled on that specific node, as it restricts scheduling to that node while also preventing other pods from using it if combined with taints and tolerations. However, to fully prevent other pods from using the node, you must also taint the node; node affinity alone only ensures the pod goes to that node, but does not block other pods.
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.