- A
Modify the Auto Scaling group's health check type to ELB
When the health check type is set to ELB, the Auto Scaling group uses the Application Load Balancer's health checks. If the test hook fails, the instance will be marked unhealthy by the ALB, and the Auto Scaling group will terminate and replace it, ensuring only healthy instances remain.
- B
Modify the CodeDeploy deployment configuration to use an increased minimum healthy instance count
Why wrong: Increasing the minimum healthy instance count affects how many instances must remain healthy during the deployment, but it does not automatically replace instances that fail the test hook. It may cause the deployment to wait longer but does not trigger replacement.
- C
Modify the Auto Scaling group's health check grace period to a lower value
Why wrong: The grace period defines how long after an instance launches before health checks start. Lowering it could cause earlier evaluation but does not address the fact that the test hook failure is not being detected by the current health check type.
- D
Modify the CodeDeploy deployment to ignore the lifecycle hook failure
Why wrong: Ignoring the lifecycle hook failure would allow the instance to be marked healthy despite failing the test, which contradicts the requirement to replace failed instances. This does not solve the problem of ensuring only healthy instances remain.
Quick Answer
The answer is to modify the Auto Scaling group's health check type to ELB. This is correct because when the health check type is set to ELB, the Auto Scaling group relies on the Elastic Load Balancer’s health checks to determine instance health, rather than the default EC2 status checks which only verify the instance is running. Since the deployment strategy CodeDeployDefault.HalfAtATime launches new instances that fail the test lifecycle hook, the ELB marks them as unhealthy, triggering the Auto Scaling group to automatically terminate and replace those failed instances. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your understanding of how CodeDeploy and Auto Scaling lifecycle hooks interact with ELB health checks—a common trap is assuming EC2 health checks catch application-level failures, but they do not. Remember the memory tip: “ELB checks the app, EC2 checks the box”—so for application health, always point the health check to the load balancer.
SOA-C02 Deployment, Provisioning, and Automation Practice Question
This SOA-C02 practice question tests your understanding of deployment, provisioning, and automation. 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 uses AWS CodeDeploy to deploy an application to an Auto Scaling group. The deployment strategy is set to CodeDeployDefault.HalfAtATime. The lifecycle hooks for the Auto Scaling group include a test hook that runs during instance launch. During a recent deployment, the deployment failed because the new instances failed the test hook and were not marked as healthy. The SysOps administrator needs to ensure that failed instances are automatically terminated and replaced with new ones from the Auto Scaling group. Which configuration change should the administrator make?
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
Modify the Auto Scaling group's health check type to ELB
Option A is correct because setting the Auto Scaling group's health check type to ELB (Elastic Load Balancer) ensures that the Auto Scaling group uses the ELB's health check status to determine instance health. When the test lifecycle hook fails, the new instances are not marked as healthy by the ELB, causing the Auto Scaling group to automatically terminate and replace them. This aligns with the requirement to automatically replace failed instances, as the default EC2 health check only considers instance status (e.g., running vs. stopped) and does not reflect application-level health.
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.
- ✓
Modify the Auto Scaling group's health check type to ELB
Why this is correct
When the health check type is set to ELB, the Auto Scaling group uses the Application Load Balancer's health checks. If the test hook fails, the instance will be marked unhealthy by the ALB, and the Auto Scaling group will terminate and replace it, ensuring only healthy instances remain.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Modify the CodeDeploy deployment configuration to use an increased minimum healthy instance count
Why it's wrong here
Increasing the minimum healthy instance count affects how many instances must remain healthy during the deployment, but it does not automatically replace instances that fail the test hook. It may cause the deployment to wait longer but does not trigger replacement.
- ✗
Modify the Auto Scaling group's health check grace period to a lower value
Why it's wrong here
The grace period defines how long after an instance launches before health checks start. Lowering it could cause earlier evaluation but does not address the fact that the test hook failure is not being detected by the current health check type.
- ✗
Modify the CodeDeploy deployment to ignore the lifecycle hook failure
Why it's wrong here
Ignoring the lifecycle hook failure would allow the instance to be marked healthy despite failing the test, which contradicts the requirement to replace failed instances. This does not solve the problem of ensuring only healthy instances remain.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume the default EC2 health check is sufficient for detecting application-level failures, but it only monitors instance status (e.g., running/stopped), not the success of lifecycle hooks or application health, so the ELB health check type is required to trigger automatic replacement.
Detailed technical explanation
How to think about this question
Under the hood, lifecycle hooks in Auto Scaling groups place instances in a 'wait' state during launch (e.g., after the test hook), and the instance is not considered healthy until the hook completes successfully. When the health check type is set to ELB, the Auto Scaling group polls the ELB's health check endpoint (e.g., HTTP 200 on a specified path) to determine instance health; if the test hook fails, the instance is marked unhealthy by the ELB, and the Auto Scaling group terminates it and launches a replacement. This is distinct from the default EC2 health check, which only checks the instance's system status (e.g., reachability via EC2 API) and does not evaluate application-level health.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
- →
Deployment, Provisioning, and Automation — study guide chapter
Learn the concepts, then practise the questions
- →
Deployment, Provisioning, and Automation practice questions
Targeted practice on this topic area only
- →
All SOA-C02 questions
1,546 questions across all exam domains
- →
AWS Certified SysOps Administrator Associate SOA-C02 study guide
Full concept coverage aligned to exam objectives
- →
SOA-C02 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SOA-C02 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Monitoring, Logging, and Remediation practice questions
Practise SOA-C02 questions linked to Monitoring, Logging, and Remediation.
Reliability and Business Continuity practice questions
Practise SOA-C02 questions linked to Reliability and Business Continuity.
Deployment, Provisioning, and Automation practice questions
Practise SOA-C02 questions linked to Deployment, Provisioning, and Automation.
Security and Compliance practice questions
Practise SOA-C02 questions linked to Security and Compliance.
Networking and Content Delivery practice questions
Practise SOA-C02 questions linked to Networking and Content Delivery.
Cost and Performance Optimization practice questions
Practise SOA-C02 questions linked to Cost and Performance Optimization.
SOA-C02 fundamentals practice questions
Practise SOA-C02 questions linked to SOA-C02 fundamentals.
SOA-C02 scenario practice questions
Practise SOA-C02 questions linked to SOA-C02 scenario.
SOA-C02 troubleshooting practice questions
Practise SOA-C02 questions linked to SOA-C02 troubleshooting.
Practice this exam
Start a free SOA-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 SOA-C02 question test?
Deployment, Provisioning, and Automation — This question tests Deployment, Provisioning, and Automation — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Modify the Auto Scaling group's health check type to ELB — Option A is correct because setting the Auto Scaling group's health check type to ELB (Elastic Load Balancer) ensures that the Auto Scaling group uses the ELB's health check status to determine instance health. When the test lifecycle hook fails, the new instances are not marked as healthy by the ELB, causing the Auto Scaling group to automatically terminate and replace them. This aligns with the requirement to automatically replace failed instances, as the default EC2 health check only considers instance status (e.g., running vs. stopped) and does not reflect application-level health.
What should I do if I get this SOA-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 →
Same concept, more angles
1 more ways this is tested on SOA-C02
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. A company uses AWS CodeDeploy to deploy a web application to an Auto Scaling group. The deployment fails with the error 'The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems.' The deployment group has a minimum of 2 healthy instances. The Auto Scaling group has 4 instances. What should the SysOps administrator check first?
medium- A.Review the deployment configuration to ensure it allows enough time for deployment.
- B.Verify that the AppSpec file includes the correct hooks.
- ✓ C.Check the Auto Scaling group's health check type and ensure it is set to ELB.
- D.Check the IAM role for CodeDeploy to ensure it has sufficient permissions.
Why C: The error indicates that the deployment could not maintain the minimum healthy instances. Checking the Auto Scaling group's health check configuration is the first step because if the health check type is not set to ELB, the instances might be marked healthy even if they are not receiving traffic. Option C is correct. Option A is wrong because the error message does not point to missing hooks. Option B is wrong because the error is about health, not about permissions. Option D is wrong because the deployment configuration is not the primary issue; the error message specifically mentions healthy instances.
Last reviewed: Jun 11, 2026
This SOA-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 SOA-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.