The answer is to configure the kubelet on the nodes with a lower node-monitor-grace-period and pod-eviction-timeout. This directly reduces pod rescheduling time during an EKS node failure by shortening the interval the kubelet waits before marking the node as unhealthy and triggering pod eviction, allowing the control plane to reschedule pods onto healthy nodes much faster. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this tests your understanding of kubelet parameters that control node health monitoring and pod lifecycle, often appearing as a trap where candidates mistakenly increase pod disruption budgets or rely on cluster autoscaler. The key distinction is that autoscaler adds new nodes but does not speed up eviction of pods on a failed node, while node auto-repair is a managed feature that operates on a longer timescale. A useful memory tip is to think of the kubelet as the node’s heartbeat monitor: lowering its grace period means the system detects a flatline sooner, triggering faster pod recovery.
DOP-C02 Resilient Cloud Solutions Practice Question
This DOP-C02 practice question tests your understanding of resilient cloud solutions. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
A company runs a containerized application on Amazon EKS. The application uses an Application Load Balancer (ALB) as the ingress controller. The DevOps team wants to ensure that the application can automatically recover from node failures. The cluster consists of managed node groups across three Availability Zones. The team noticed that when a node fails, the pods on that node are not rescheduled for several minutes. The team wants to reduce the time to reschedule pods. Which configuration change should the team make?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the kubelet on the nodes to have a lower node-monitor-grace-period and pod-eviction-timeout.
Option B is correct because configuring the kubelet with a lower node-monitor-grace-period (e.g., 40 seconds) and pod-eviction-timeout reduces the time before the node is considered unhealthy and pods are evicted. Option A (increasing pod disruption budgets) would delay rescheduling. Option C (node auto-repair) is a managed feature but doesn't directly reduce pod rescheduling time. Option D (cluster autoscaler) adds nodes but does not reduce rescheduling time for existing pods.
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.
✗
Increase the pod disruption budget for the application deployments.
Why it's wrong here
A higher PDB delays pod eviction, increasing rescheduling time.
✗
Enable the AWS node auto-repair feature on the managed node group.
Why it's wrong here
Node auto-repair replaces unhealthy nodes but does not speed up pod rescheduling.
✗
Enable cluster autoscaler to add new nodes quickly.
Why it's wrong here
Cluster autoscaler adds nodes but does not reduce the time to reschedule existing pods onto other nodes.
✓
Configure the kubelet on the nodes to have a lower node-monitor-grace-period and pod-eviction-timeout.
Why this is correct
Reduces the time the control plane waits before marking the node as unhealthy and evicting pods.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
Use explanations to understand the rule behind the answer.
TExam Day Tips
→Underline the problem statement mentally.
→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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
Resilient Cloud Solutions — This question tests Resilient Cloud Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure the kubelet on the nodes to have a lower node-monitor-grace-period and pod-eviction-timeout. — Option B is correct because configuring the kubelet with a lower node-monitor-grace-period (e.g., 40 seconds) and pod-eviction-timeout reduces the time before the node is considered unhealthy and pods are evicted. Option A (increasing pod disruption budgets) would delay rescheduling. Option C (node auto-repair) is a managed feature but doesn't directly reduce pod rescheduling time. Option D (cluster autoscaler) adds nodes but does not reduce rescheduling time for existing pods.
What should I do if I get this DOP-C02 question wrong?
Identify which DOP-C02 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 DOP-C02 practice question is part of Courseiva's free Amazon Web Services 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 DOP-C02 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.