CV0-004 Operations and Support Practice Question
A cloud operations team manages a fleet of Amazon EC2 instances running a stateless web tier behind an Application Load Balancer. The team wants to replace instances automatically when an instance fails an Elastic Load Balancing health check, without manual intervention, while keeping the desired capacity constant. Which AWS feature should the team configure to meet this requirement?
⚠ Common exam trap
The trap here is assuming that EC2 status checks and ELB health checks are equivalent, when an instance can pass EC2 checks yet still be removed from load balancer rotation.
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
✓
EC2 Auto Scaling group with health check type set to ELB
Automatic replacement of instances that fail load balancer health checks requires an Auto Scaling group whose health check type is set to ELB. In that mode, the group treats an instance as unhealthy when the load balancer reports it as unhealthy, terminates it, and launches a replacement to preserve desired capacity. Other options either react to metrics rather than health checks or only evaluate EC2-level status.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
EC2 Auto Scaling group with health check type set to ELB
Why this is correct
An Auto Scaling group configured with the ELB health check type uses the load balancer's health status to determine instance health. When an instance fails the ELB health check, Auto Scaling terminates it and launches a replacement to maintain the desired capacity, providing the automatic recovery the team needs without manual intervention.
- ✗
EC2 Auto Scaling group with health check type set to EC2
Why it's wrong here
With the EC2 health check type, Auto Scaling only evaluates the instance's own status checks, such as system and instance status. An instance can pass EC2 status checks while still failing the load balancer's application-level health check, so this configuration would not replace instances that are unhealthy from the load balancer's perspective.
- ✗
AWS Lambda function triggered by Amazon CloudWatch alarms on CPU utilization
Why it's wrong here
A Lambda function invoked by a CloudWatch alarm on CPU utilization reacts to a performance metric, not to load balancer health check failures. This approach would require custom code to terminate and relaunch instances, and CPU utilization is not a reliable indicator of the application-level failures the ELB health check detects.
- ✗
AWS Elastic Beanstalk environment with rolling updates
Why it's wrong here
Elastic Beanstalk manages application deployment and can perform rolling updates during version deployments, but it does not continuously monitor ELB health checks to replace unhealthy instances outside of a deployment event. This scenario requires ongoing automatic replacement of failed instances, which Elastic Beanstalk's deployment-focused features do not provide on their own.
Go deeper
Related to this question
About these practice questions
This CV0-004 question is part of Courseiva's 834-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.