- A
Setting the 'nodeName' field in the pod spec
Directly assigns the pod to a node.
- B
Using 'affinity' with 'nodeAffinity' rules
Provides advanced node selection.
- C
Using 'nodeSelector' with label matching
Selects nodes with matching labels.
- D
Using a ServiceAccount
Why wrong: ServiceAccounts provide identity for pods, not node assignment.
- E
Setting the 'clusterName' field
Why wrong: clusterName is not used for node assignment.
Question 623 of 997
Three Valid Ways to Assign a Pod to a Specific Node: nodeName, nodeSelector, and nodeAffinity
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.
Which THREE of the following are valid ways to assign a pod to a specific node? (Choose three.)
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
✓
Setting the 'nodeName' field in the pod spec
Setting the 'nodeName' field in the pod spec directly assigns the pod to a specific node by name. This bypasses the scheduler entirely, as the kubelet on that node will see the pod and attempt to run it. It is a valid, though inflexible, method for node assignment.
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.
- ✓
Setting the 'nodeName' field in the pod spec
Why this is correct
Directly assigns the pod to a node.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Using 'affinity' with 'nodeAffinity' rules
Why this is correct
Provides advanced node selection.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Using 'nodeSelector' with label matching
Why this is correct
Selects nodes with matching labels.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Using a ServiceAccount
Why it's wrong here
ServiceAccounts provide identity for pods, not node assignment.
- ✗
Setting the 'clusterName' field
Why it's wrong here
clusterName is not used for node assignment.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Candidates often confuse direct node assignment (nodeName) with scheduling constraints (nodeSelector, nodeAffinity). ServiceAccount and clusterName do not affect node placement.
Detailed technical explanation
How to think about this question
Under the hood, 'nodeName' is checked by the kubelet during pod admission, and if it matches the node's hostname, the kubelet will run the pod regardless of scheduler decisions. 'nodeAffinity' and 'nodeSelector' are evaluated by the scheduler, which uses label matching to filter nodes; 'nodeAffinity' supports both required (hard) and preferred (soft) rules, offering more flexibility than 'nodeSelector'. In real-world scenarios, 'nodeName' is useful for debugging or system pods that must run on a specific control-plane node, while affinity rules are better for dynamic scheduling based on node labels like GPU availability.
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: Setting the 'nodeName' field in the pod spec — Setting the 'nodeName' field in the pod spec directly assigns the pod to a specific node by name. This bypasses the scheduler entirely, as the kubelet on that node will see the pod and attempt to run it. It is a valid, though inflexible, method for node assignment.
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 →
Same concept, more angles
2 more ways this is tested on KCNA
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO of the following are valid ways to assign a pod to a specific node?
medium- ✓ A.nodeSelector
- B.affinity: nodeAntiAffinity
- C.tolerations
- ✓ D.nodeName
- E.podSelector
Why A: Option A is correct because `nodeSelector` is a simple, built-in field in the Pod spec that matches the pod to nodes with specific labels. When you add a `nodeSelector` with a key-value pair, the scheduler only places the pod on nodes that have that exact label. This is the most straightforward way to constrain a pod to a subset of nodes.
Variation 2. Which Kubernetes resource can be used to assign a pod to a specific node?
hard- ✓ A.Node affinity rules in the pod spec
- B.A NetworkPolicy
- C.A Service account
- D.A ConfigMap
Why A: Node affinity rules in the pod spec are a set of constraints that define which nodes a pod can be scheduled on, based on node labels. This is a native Kubernetes scheduling feature that allows you to attract pods to specific nodes using required or preferred matching rules, such as `requiredDuringSchedulingIgnoredDuringExecution`. This directly answers the question of assigning a pod to a specific node.
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.