Launch Configurations

Correct Answer: Create an updated AMI and update the Launch Configuration (LC) to use the new AMI

For creating an immutable infrastructure, an updated AMI should be created with the latest code and then update the Launch Configuration to use the new AMI. Updating the User Data script or applying patches on existing instances break the immutable infrastructure concept, and other wrong answers are not efficient and add unnecessary complexity.

Correct Answer: Increase the desired capacity of the Auto Scaling group

Desired capacity is the target number of instances an Auto Scaling group maintains. Increasing it triggers immediate scale-out, launching additional instances behind the Application Load Balancer to handle the surge. Changing the instance type size involves modifying the launch configuration/template and replacing instances, which is slower and not necessary for an immediate response. Adding an Availability Zone is configured on the Auto Scaling group (not the launch configuration) and does not, by itself, increase capacity. Enabling suspended processes actually prevents scaling activities and would hinder scale-out.

Correct Answer: Create a Launch Configuration (LC) for each tier with a specific User Data

The best approach is to create a Launch Configuration for each tier of the application and each has a specific User Data. This ensures that instances in each tier are provisioned and configured correctly. Other options are either not suitable for provisioning instances or do not ensure correct configuration based on tier.