AWS Certified SysOps Administrator Practice Exam

Disable ads (and more) with a membership for a one time $4.99 payment

Prepare for the AWS Certified SysOps Administrator Exam. Utilize flashcards, multiple-choice questions, tips, and in-depth explanations. Get exam-ready!

Practice this question and more.


What adjustment is needed to automate the replacement of unhealthy EC2 instances in an Elastic Beanstalk environment?

  1. Set the health check type to ELB in the Auto Scaling group configuration

  2. Increase the instance count in the Elastic Beanstalk environment settings

  3. Implement much lower instance scaling limits in the Auto Scaling group

  4. Change the instance type to ensure compatibility with health checks

The correct answer is: Set the health check type to ELB in the Auto Scaling group configuration

Setting the health check type to ELB (Elastic Load Balancer) in the Auto Scaling group configuration is the key adjustment needed to automate the replacement of unhealthy EC2 instances within an Elastic Beanstalk environment. When the health check type is set to ELB, the Auto Scaling group can receive health information directly from the Elastic Load Balancer, allowing it to determine the health of the instances more effectively based on the defined health check settings. This means that if an instance becomes unhealthy as per the ELB health checks, the Auto Scaling group automatically replaces it with a new instance, ensuring high availability and reliability of the application. By utilizing ELB health checks, the system not only monitors the health of instances but also responds dynamically to changes, providing an automated mechanism for maintaining application health. This is especially important in environments where application uptime and constant availability are paramount, as it ensures that end-users always receive service through healthy instances. Adjusting other configurations such as increasing the instance count, setting lower scaling limits, or changing the instance type may affect application performance or scaling behavior but do not directly address the automation of replacing unhealthy instances. These actions focus on resource allocation and scalability rather than monitoring and recovery from failure, which is precisely what setting the health check