- A
Configure a pod disruption budget to prevent too many pods from being terminated simultaneously.
Why wrong: Pod disruption budgets are for voluntary disruptions, not node failures.
- B
Use a horizontal pod autoscaler to increase the number of pods during high load.
Why wrong: Horizontal pod autoscaler scales based on metrics, not node failures.
- C
Configure the EKS managed node group with a health check and ensure that the Kubernetes control plane automatically reschedules pods from failed nodes.
EKS managed node groups automatically replace unhealthy nodes, and Kubernetes reschedules pods.
- D
Use a cluster autoscaler to automatically add new nodes when pods are pending.
Why wrong: Cluster autoscaler adds nodes but does not reschedule pods from failed nodes.
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. They want to ensure that if a node fails, the pods are rescheduled on healthy nodes. Which configuration is necessary?
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
Configure the EKS managed node group with a health check and ensure that the Kubernetes control plane automatically reschedules pods from failed nodes.
Option C is correct because EKS managed node groups automatically register nodes with the Kubernetes control plane, and the Kubernetes node controller (part of the kube-controller-manager) monitors node health via the NodeLifecycleController. When a node fails (e.g., due to an EC2 instance termination or health check failure), the control plane marks the node as `NotReady` and, after the default pod eviction timeout (5 minutes), evicts pods from the failed node, rescheduling them on healthy nodes. This behavior is inherent to Kubernetes and does not require additional configuration beyond using a managed node group.
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.
- ✗
Configure a pod disruption budget to prevent too many pods from being terminated simultaneously.
Why it's wrong here
Pod disruption budgets are for voluntary disruptions, not node failures.
- ✗
Use a horizontal pod autoscaler to increase the number of pods during high load.
Why it's wrong here
Horizontal pod autoscaler scales based on metrics, not node failures.
- ✓
Configure the EKS managed node group with a health check and ensure that the Kubernetes control plane automatically reschedules pods from failed nodes.
Why this is correct
EKS managed node groups automatically replace unhealthy nodes, and Kubernetes reschedules pods.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a cluster autoscaler to automatically add new nodes when pods are pending.
Why it's wrong here
Cluster autoscaler adds nodes but does not reschedule pods from failed nodes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the Cluster Autoscaler (which adds nodes) with the node controller's pod rescheduling behavior, or they think a PodDisruptionBudget is needed for failure recovery when it only applies to voluntary disruptions.
Detailed technical explanation
How to think about this question
Under the hood, the Kubernetes node controller uses the `node-monitor-grace-period` (default 40 seconds) and `pod-eviction-timeout` (default 5 minutes) to determine when to evict pods from a failed node. The kubelet on each node sends periodic heartbeats (NodeStatus updates) to the control plane; if these stop, the node is considered `Unknown` and eventually `NotReady`. In EKS, managed node groups integrate with EC2 Auto Scaling health checks, so if an EC2 instance fails, the node group replaces it, but pod rescheduling is handled by the Kubernetes control plane, not the node group itself.
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
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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Resilient Cloud Solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Resilient Cloud Solutions practice questions
Targeted practice on this topic area only
- →
All DOP-C02 questions
1,750 questions across all exam domains
- →
AWS Certified DevOps Engineer Professional DOP-C02 study guide
Full concept coverage aligned to exam objectives
- →
DOP-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DOP-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Configuration Management and IaC practice questions
Practise DOP-C02 questions linked to Configuration Management and IaC.
Resilient Cloud Solutions practice questions
Practise DOP-C02 questions linked to Resilient Cloud Solutions.
Monitoring and Logging practice questions
Practise DOP-C02 questions linked to Monitoring and Logging.
Incident and Event Response practice questions
Practise DOP-C02 questions linked to Incident and Event Response.
Security and Compliance practice questions
Practise DOP-C02 questions linked to Security and Compliance.
SDLC Automation practice questions
Practise DOP-C02 questions linked to SDLC Automation.
DOP-C02 fundamentals practice questions
Practise DOP-C02 questions linked to DOP-C02 fundamentals.
DOP-C02 scenario practice questions
Practise DOP-C02 questions linked to DOP-C02 scenario.
DOP-C02 troubleshooting practice questions
Practise DOP-C02 questions linked to DOP-C02 troubleshooting.
Practice this exam
Start a free DOP-C02 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 DOP-C02 question test?
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 EKS managed node group with a health check and ensure that the Kubernetes control plane automatically reschedules pods from failed nodes. — Option C is correct because EKS managed node groups automatically register nodes with the Kubernetes control plane, and the Kubernetes node controller (part of the kube-controller-manager) monitors node health via the NodeLifecycleController. When a node fails (e.g., due to an EC2 instance termination or health check failure), the control plane marks the node as `NotReady` and, after the default pod eviction timeout (5 minutes), evicts pods from the failed node, rescheduling them on healthy nodes. This behavior is inherent to Kubernetes and does not require additional configuration beyond using a managed node group.
What should I do if I get this DOP-C02 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 DOP-C02 practice questions
- A company uses AWS CodePipeline with a multi-branch strategy. A new feature branch triggers a pipeline that runs unit te…
- A development team uses AWS CodeBuild to compile a Java application and run unit tests. The build takes 30 minutes, but…
- A company uses AWS CodePipeline with multiple stages: Source (Amazon S3), Build (AWS CodeBuild), and Deploy (AWS CodeDep…
- A company uses AWS CodeCommit for source control. Developers frequently push large binary files (e.g., compiled JARs) to…
- A company runs a Stateful application on EC2 that requires sticky sessions. They use an ALB with duration-based stickine…
- An organization uses AWS CodePipeline to orchestrate deployments to multiple environments (dev, test, prod). Each enviro…
Last reviewed: Jul 4, 2026
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.