- A
Node affinity with requiredDuringSchedulingIgnoredDuringExecution
Why wrong: Node affinity selects nodes based on node labels, not pod relationships.
- B
Pod affinity with a preferredDuringSchedulingIgnoredDuringExecution
Why wrong: Pod affinity attracts pods to nodes with other pods; requiredDuringScheduling forces it.
- C
Pod anti-affinity with requiredDuringSchedulingIgnoredDuringExecution and topologyKey: kubernetes.io/hostname
This ensures the scheduler does not place two pods from the same deployment on the same node.
- D
Taints and tolerations
Why wrong: Taints and tolerations prevent pods from being scheduled on nodes with taints, but do not enforce pod-to-pod separation.
Question 652 of 997
Kubernetes Pod Anti-Affinity — Prevent Same-Node Scheduling | CKNA Explained
This KCNA practice question tests your understanding of container orchestration. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
An application requires that a pod must not be scheduled on the same node as another pod from the same Deployment. Which configuration should be used?
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
✓
Pod anti-affinity with requiredDuringSchedulingIgnoredDuringExecution and topologyKey: kubernetes.io/hostname
Option C is correct because pod anti-affinity with `requiredDuringSchedulingIgnoredDuringExecution` enforces a hard constraint that prevents two pods from the same Deployment from being scheduled on the same node. The `topologyKey: kubernetes.io/hostname` specifies that the anti-affinity rule applies at the node level, ensuring each pod is placed on a distinct host. This directly meets the requirement that a pod must not be scheduled on the same node as another pod from the same Deployment.
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.
- ✗
Node affinity with requiredDuringSchedulingIgnoredDuringExecution
Why it's wrong here
Node affinity selects nodes based on node labels, not pod relationships.
- ✗
Pod affinity with a preferredDuringSchedulingIgnoredDuringExecution
Why it's wrong here
Pod affinity attracts pods to nodes with other pods; requiredDuringScheduling forces it.
- ✓
Pod anti-affinity with requiredDuringSchedulingIgnoredDuringExecution and topologyKey: kubernetes.io/hostname
Why this is correct
This ensures the scheduler does not place two pods from the same deployment on the same node.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Taints and tolerations
Why it's wrong here
Taints and tolerations prevent pods from being scheduled on nodes with taints, but do not enforce pod-to-pod separation.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common pitfall in Kubernetes exams is confusing pod affinity (which attracts pods to the same node) with pod anti-affinity (which repels them). Option B uses `preferredDuringSchedulingIgnoredDuringExecution` which is a soft preference, not a hard requirement, and it uses affinity instead of anti-affinity, so it would actually encourage pods to be together, not apart.
Detailed technical explanation
How to think about this question
Under the hood, pod anti-affinity uses the `topologyKey` to define the failure domain (e.g., `kubernetes.io/hostname` for nodes, or `topology.kubernetes.io/zone` for availability zones). The `requiredDuringSchedulingIgnoredDuringExecution` policy is enforced at scheduling time by the kube-scheduler, which checks the `podAntiAffinity` field against existing pods in the same namespace (or across namespaces if `namespaceSelector` is used). A subtle behavior is that this rule only applies to pods that are already running; if a node becomes empty later, the anti-affinity does not force rescheduling—hence the 'IgnoredDuringExecution' suffix.
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 KCNA 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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Container Orchestration — study guide chapter
Learn the concepts, then practise the questions
- →
Container Orchestration practice questions
Targeted practice on this topic area only
- →
All KCNA questions
997 questions across all exam domains
- →
Kubernetes and Cloud Native Associate KCNA study guide
Full concept coverage aligned to exam objectives
- →
KCNA practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related KCNA practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Kubernetes Fundamentals practice questions
Practise KCNA questions linked to Kubernetes Fundamentals.
Container Orchestration practice questions
Practise KCNA questions linked to Container Orchestration.
Cloud Native Architecture practice questions
Practise KCNA questions linked to Cloud Native Architecture.
Cloud Native Observability practice questions
Practise KCNA questions linked to Cloud Native Observability.
Cloud Native Application Delivery practice questions
Practise KCNA questions linked to Cloud Native Application Delivery.
KCNA fundamentals practice questions
Practise KCNA questions linked to KCNA fundamentals.
KCNA scenario practice questions
Practise KCNA questions linked to KCNA scenario.
KCNA troubleshooting practice questions
Practise KCNA questions linked to KCNA troubleshooting.
Practice this exam
Start a free KCNA practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this KCNA question test?
Container Orchestration — This question tests Container Orchestration — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Pod anti-affinity with requiredDuringSchedulingIgnoredDuringExecution and topologyKey: kubernetes.io/hostname — Option C is correct because pod anti-affinity with `requiredDuringSchedulingIgnoredDuringExecution` enforces a hard constraint that prevents two pods from the same Deployment from being scheduled on the same node. The `topologyKey: kubernetes.io/hostname` specifies that the anti-affinity rule applies at the node level, ensuring each pod is placed on a distinct host. This directly meets the requirement that a pod must not be scheduled on the same node as another pod from the same Deployment.
What should I do if I get this KCNA 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 →
Keep practising
More KCNA practice questions
- Which CNCF project provides a graduated service mesh implementation that includes features like traffic management, secu…
- A pod in the 'production' namespace is in a CrashLoopBackOff state. The pod has been running successfully for several da…
- You need to ensure that a pod runs on a node with SSD storage. How can you achieve this?
- Match each Kubernetes resource to its primary purpose.
- Match each Kubernetes security concept to its definition.
- Which three of the following are valid methods to create or update resources in Kubernetes? (Choose three.)
Last reviewed: Jul 4, 2026
This KCNA 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 KCNA 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.