- A
replicas: 3
Why wrong: This sets the count but does not spread across nodes.
- B
template.spec.affinity.podAntiAffinity
PodAntiAffinity can prevent scheduling multiple pods on the same node.
- C
strategy.type: Recreate
Why wrong: Recreate strategy does not affect node distribution.
- D
template.spec.nodeName
Why wrong: nodeName directly assigns a specific node, not suitable for dynamic scheduling.
Question 565 of 997
Using Pod Anti-Affinity for Fault Tolerance
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 administrator wants to ensure that a Deployment named 'webapp' always has exactly 3 replicas running across distinct nodes to improve fault tolerance. Which field in the Deployment spec should they configure?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"always"Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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
✓
template.spec.affinity.podAntiAffinity
Option B is correct because `podAntiAffinity` in the `template.spec.affinity` field allows you to enforce scheduling rules that prevent multiple pods from the same Deployment from running on the same node. By configuring a `requiredDuringSchedulingIgnoredDuringExecution` pod anti-affinity rule with a topology key of `kubernetes.io/hostname`, the scheduler ensures that each of the 3 replicas is placed on a distinct node, thereby improving fault tolerance against node failures.
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.
- ✗
replicas: 3
Why it's wrong here
This sets the count but does not spread across nodes.
- ✓
template.spec.affinity.podAntiAffinity
Why this is correct
PodAntiAffinity can prevent scheduling multiple pods on the same node.
Clue confirmation
The clue word "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
strategy.type: Recreate
Why it's wrong here
Recreate strategy does not affect node distribution.
- ✗
template.spec.nodeName
Why it's wrong here
nodeName directly assigns a specific node, not suitable for dynamic scheduling.
Common exam traps
Common exam trap: answer the scenario, not the keyword
CNCF often tests the distinction between ensuring a desired number of replicas (via `replicas`) and controlling pod placement (via affinity/anti-affinity), trapping candidates who assume that setting `replicas` alone guarantees distribution across nodes.
Detailed technical explanation
How to think about this question
Under the hood, pod anti-affinity is implemented using the Kubernetes scheduler's predicates, which evaluate `requiredDuringSchedulingIgnoredDuringExecution` rules during pod placement. The `topologyKey` (e.g., `kubernetes.io/hostname`) defines the domain over which anti-affinity is enforced; using `kubernetes.io/hostname` ensures that no two pods with the same label selector run on the same node. In a real-world scenario, if a node fails, the ReplicaSet controller will create a replacement pod, and the anti-affinity rule will prevent it from being scheduled on any node already hosting a pod from the same set, maintaining the distribution across remaining healthy nodes.
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: template.spec.affinity.podAntiAffinity — Option B is correct because `podAntiAffinity` in the `template.spec.affinity` field allows you to enforce scheduling rules that prevent multiple pods from the same Deployment from running on the same node. By configuring a `requiredDuringSchedulingIgnoredDuringExecution` pod anti-affinity rule with a topology key of `kubernetes.io/hostname`, the scheduler ensures that each of the 3 replicas is placed on a distinct node, thereby improving fault tolerance against node failures.
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.
Are there clue words in this question I should notice?
Yes — watch for: "always". Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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.