A company has a web application running on Amazon EC2 instances inside an Auto Scaling group (ASG). The instances are registered with an Amazon Application Load Balancer (ALB). The application process on several instances crashes, causing the ALB target group health checks to mark those instances as unhealthy. However, the ASG does not terminate and replace the unhealthy instances. Which configuration change will ensure that the Auto Scaling group automatically replaces instances that fail the Application Load Balancer health check?
- Update the Auto Scaling group health check type configuration from EC2 to ELB.Cevap
- BConfigure an Amazon Route 53 latency routing policy with health checks to route traffic away from the unhealthy instances.
- CModify the subnet's stateless Network Access Control List (NACL) outbound rules to allow return traffic on all ephemeral ports.
- DChange the target group health check settings to query the default HTTP port 80 instead of the custom port where the application runs.
Cevap
Update the Auto Scaling group health check type configuration from EC2 to ELB.
The correct answer is to update the Auto Scaling group's health check configuration to use ELB. By default, Auto Scaling groups only monitor EC2 status checks. If an application process crashes but the underlying EC2 instance remains running, the EC2 status checks will pass, and the Auto Scaling group will not replace the instance. Changing the health check type to ELB ensures the Auto Scaling group replaces any instance that fails the target group health checks.
Adım Adım Çözüm
Anahtar Kavram
Auto Scaling Group Health Check Types
Tahmini Süre:1m 0s