- A
Use nodeSelector with a label that matches nodes having SSDs
Why wrong: nodeSelector is a simpler version of node affinity but is still valid; however, the question asks for a more flexible method. Actually, nodeSelector is correct but less flexible. For hard constraint, nodeSelector works. But node affinity is more expressive. Since nodeSelector is also valid, but the question expects node affinity because it's more commonly used for complex requirements. However, both could be correct. However, nodeSelector does not support multiple conditions. The best answer is node affinity because it supports multiple operators.
- B
Use a taint on nodes without SSDs and a toleration on the pod
Why wrong: Taints and tolerations are used to repel pods from nodes, not to attract them to specific nodes.
- C
Use pod anti-affinity to avoid nodes without SSDs
Why wrong: Pod anti-affinity is used to spread pods across nodes, not to select nodes based on hardware.
- D
Use node affinity with requiredDuringSchedulingIgnoredDuringExecution
Node affinity allows you to specify hard or soft constraints. Using requiredDuringSchedulingIgnoredDuringExecution ensures the pod is only scheduled on nodes with the specified label.
Node Affinity: Ensuring Pods Run on SSD Nodes
This KCNA practice question tests your understanding of kubernetes fundamentals. 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 need to ensure that a pod runs on a node with SSD storage. How can you achieve this?
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
Use node affinity with requiredDuringSchedulingIgnoredDuringExecution
Node affinity with `requiredDuringSchedulingIgnoredDuringExecution` is the correct approach because it allows you to specify a hard constraint that the pod must be scheduled on a node with a specific label (e.g., `disk=ssd`). This ensures the pod runs only on nodes that have SSD storage, as the scheduler enforces this rule during pod placement.
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 nodeSelector with a label that matches nodes having SSDs
Why it's wrong here
nodeSelector is a simpler version of node affinity but is still valid; however, the question asks for a more flexible method. Actually, nodeSelector is correct but less flexible. For hard constraint, nodeSelector works. But node affinity is more expressive. Since nodeSelector is also valid, but the question expects node affinity because it's more commonly used for complex requirements. However, both could be correct. However, nodeSelector does not support multiple conditions. The best answer is node affinity because it supports multiple operators.
- ✗
Use a taint on nodes without SSDs and a toleration on the pod
Why it's wrong here
Taints and tolerations are used to repel pods from nodes, not to attract them to specific nodes.
- ✗
Use pod anti-affinity to avoid nodes without SSDs
Why it's wrong here
Pod anti-affinity is used to spread pods across nodes, not to select nodes based on hardware.
- ✓
Use node affinity with requiredDuringSchedulingIgnoredDuringExecution
Why this is correct
Node affinity allows you to specify hard or soft constraints. Using requiredDuringSchedulingIgnoredDuringExecution ensures the pod is only scheduled on nodes with the specified label.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Kubernetes often tests the distinction between node affinity (which attracts pods to nodes with specific labels) and taints/tolerations (which repel pods from nodes), leading candidates to incorrectly choose taints/tolerations when the goal is to ensure a pod runs on a node with a specific feature.
Detailed technical explanation
How to think about this question
Node affinity uses the `nodeSelectorTerms` field with `matchExpressions` to define rules, and `requiredDuringSchedulingIgnoredDuringExecution` is a hard constraint enforced at scheduling time (the scheduler will not place the pod on a non-matching node). Under the hood, the kube-scheduler evaluates these expressions against node labels during the filtering phase, and if no node matches, the pod remains unscheduled. A real-world scenario is when you have a mixed cluster with SSD and HDD nodes, and you need to guarantee that a database pod only runs on SSD nodes for performance; node affinity with `requiredDuringSchedulingIgnoredDuringExecution` is the standard way to enforce this.
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.
- →
Kubernetes Fundamentals — study guide chapter
Learn the concepts, then practise the questions
- →
Kubernetes Fundamentals 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?
Kubernetes Fundamentals — This question tests Kubernetes Fundamentals — 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 requiredDuringSchedulingIgnoredDuringExecution — Node affinity with `requiredDuringSchedulingIgnoredDuringExecution` is the correct approach because it allows you to specify a hard constraint that the pod must be scheduled on a node with a specific label (e.g., `disk=ssd`). This ensures the pod runs only on nodes that have SSD storage, as the scheduler enforces this rule during pod placement.
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…
- 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.)
- Which TWO of the following are valid Prometheus metric types? (Select two.)
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.