What should the SysOps administrator do next to make the application highly available?
Create an Auto Scaling group by using the launch configuration across at least two Availability Zones. Configure a minimum capacity of 1, a desired capacity of 1, and a maximum capacity of 1.
Create an Auto Scaling group by using the launch configuration across at least three Availability Zones. Configure a minimum capacity of 2, a desired capacity of 2, and a maximum capacity of 2.
Create an Auto Scaling group by using the launch configuration across at least two AWS Regions. Configure a minimum capacity of 1, a desired capacity of 1, and a maximum capacity of 1.
Create an Auto Scaling group by using the launch configuration across at least three AWS Regions. Configure a minimum capacity of 2, a desired capacity of 2, and a maximum capacity of 2.
Explanations:
This option suggests using only one instance across a single Availability Zone (AZ), which does not achieve high availability. High availability requires multiple AZs.
This option uses Auto Scaling across at least two AZs, which ensures high availability. A minimum of 2 instances in each AZ ensures fault tolerance.
This option suggests using multiple AWS Regions, which is unnecessary for high availability within a single application. The goal is to use AZs within the same region.
This option suggests using multiple AWS Regions, which is complex and not necessary for ensuring high availability for the application. Multiple AZs in a region are sufficient.
I gauge that the answer is:
Create an Auto Scaling group by using the launch configuration across at least three Availability Zones. Configure a minimum capacity of 2, a desired capacity of 2, and a maximum capacity of 2.
I rank that the answer is:
Create an Auto Scaling group by using the launch configuration across at least three Availability Zones. Configure a minimum capacity of 2, a desired capacity of 2, and a maximum capacity of 2.