Explanation:
To make an application highly available, you must ensure that it can continue to operate even if an entire Availability Zone (AZ) fails. \n\n* Multi-AZ Deployment: By updating the Auto Scaling group to launch instances in at least two Availability Zones, the Application Load Balancer can route traffic to the healthy instances in the second AZ if the first one experiences an outage.\n* Comparison: \n * Options A and B increase capacity but do not address the single point of failure (the single AZ).\n * Option D involves a second Region, which is usually for disaster recovery (DR) rather than standard high availability, and involves significantly more complexity (cross-region load balancing or DNS failover).
Ultimate access to all questions.
Question #26\nA company has an internal web application that runs on Amazon EC2 instances behind an Application Load Balancer. The instances run in an Amazon EC2 Auto Scaling group in a single Availability Zone. A CloudOps engineer must make the application highly available.\nWhich action should the CloudOps engineer take to meet this requirement?
A
Increase the maximum number of instances in the Auto Scaling group to meet the capacity that is required at peak usage.
B
Increase the minimum number of instances in the Auto Scaling group to meet the capacity that is required at peak usage.
C
Update the Auto Scaling group to launch new instances in a second Availability Zone in the same AWS Region.
D
Update the Auto Scaling group to launch new instances in an Availability Zone in a second AWS Region.
No comments yet.