What step should the Administrator complete next to make the application highly available?
Create an Auto Scaling group by using the launch configuration across at least 2 Availability Zones with a minimum size of 1, desired capacity of 1, and a maximum size of 1.
Create an Auto Scaling group by using the launch configuration across at least 3 Availability Zones with a minimum size of 2, desired capacity of 2, and a maximum of 2.
Create an Auto Scaling group by using the launch configuration across at least 2 regions with a minimum size of 1, desired capacity of 1, and a maximum size of 1.
Create an Auto Scaling group by using the launch configuration across at least 3 regions with a minimum size of 2, desired capacity of 2, and a maximum size of 2.
Explanations:
While the Auto Scaling group is being created across at least 2 Availability Zones, the minimum, desired, and maximum sizes are too small to ensure high availability. A minimum size of 1 and maximum size of 1 means only one instance will be running, which does not provide redundancy or failover capability.
This option creates an Auto Scaling group with a desired capacity of 2 EC2 instances, spread across at least 2 Availability Zones. This ensures high availability, with load balancing and automatic scaling to ensure fault tolerance and redundancy.
The option specifies scaling across regions, but high availability within the same region is typically achieved using multiple Availability Zones, not multiple regions. Additionally, the minimum and maximum size of 1 does not provide redundancy or failover.
Similar to option C, this option focuses on scaling across regions, which is not necessary for achieving high availability within a single region. Also, the minimum and maximum size of 2 is correct, but multi-region scaling is not needed here.