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.
An administrator wants to update the image of a Deployment named 'my-app' from 'nginx:1.19' to 'nginx:1.20' with a rolling update strategy. They want to ensure that during the update, the number of unavailable pods never exceeds 1. Which field should they set in the Deployment spec?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "never"
Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
Why wrong: replicas sets the desired number of pods, not the update surge/unavailable count.
B
spec.minReadySeconds
Why wrong: minReadySeconds is the minimum time a pod must be ready to be considered available; it does not control the number of unavailable pods during update.
C
spec.strategy.rollingUpdate.maxSurge
Why wrong: maxSurge controls how many extra pods can be created above the desired count, not the unavailable count.
D
spec.strategy.rollingUpdate.maxUnavailable
maxUnavailable sets the maximum number of pods that can be unavailable during a rolling update. Setting to 1 ensures at most one pod is down at a time.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
spec.strategy.rollingUpdate.maxUnavailable
Option D is correct because `spec.strategy.rollingUpdate.maxUnavailable` controls the maximum number of Pods that can be unavailable during a rolling update. Setting this to 1 ensures that at most one Pod is unavailable at any time, meeting the administrator's requirement. This field is part of the Deployment's rolling update strategy and directly governs the availability guarantee during the update process.
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.
✗
spec.replicas
Why it's wrong here
replicas sets the desired number of pods, not the update surge/unavailable count.
✗
spec.minReadySeconds
Why it's wrong here
minReadySeconds is the minimum time a pod must be ready to be considered available; it does not control the number of unavailable pods during update.
✗
spec.strategy.rollingUpdate.maxSurge
Why it's wrong here
maxSurge controls how many extra pods can be created above the desired count, not the unavailable count.
✓
spec.strategy.rollingUpdate.maxUnavailable
Why this is correct
maxUnavailable sets the maximum number of pods that can be unavailable during a rolling update. Setting to 1 ensures at most one pod is down at a time.
Clue confirmation
The clue word "never" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse `maxSurge` with `maxUnavailable`, mistakenly thinking that controlling how many extra Pods are created (surge) also limits unavailable Pods, but `maxSurge` only caps the number of Pods above the desired count, not the number that can be unavailable.
Detailed technical explanation
How to think about this question
Under the hood, the Kubernetes Deployment controller uses `maxUnavailable` and `maxSurge` together to orchestrate a rolling update. `maxUnavailable` can be specified as an absolute number (e.g., 1) or a percentage of the desired replicas; it defines how many Pods can be in a non-ready state at any point. This ensures that the update proceeds safely by terminating old Pods and creating new ones in a controlled manner, preventing service disruption beyond the configured threshold.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this KCNA question in full detail.
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: spec.strategy.rollingUpdate.maxUnavailable — Option D is correct because `spec.strategy.rollingUpdate.maxUnavailable` controls the maximum number of Pods that can be unavailable during a rolling update. Setting this to 1 ensures that at most one Pod is unavailable at any time, meeting the administrator's requirement. This field is part of the Deployment's rolling update strategy and directly governs the availability guarantee during the update process.
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: "never". Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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 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.