A stateless application runs behind an ALB on EC2 instances in an Auto Scaling group. The group uses a fully baked custom AMI with no bootstrap. That AMI was recently deleted, causing the Auto Scaling group to fail to launch instances because the AMI ID no longer exists. Which sequence of actions should a DevOps engineer perform to restore functioning scaling? (Choose three.)

To restore the Auto Scaling group, you first need a valid AMI. Since the original custom AMI was deleted, you must create a new one. The most reliable way to ensure the new AMI is identical to the previous one is to create it from an existing, running EC2 instance within the Auto Scaling group, as these instances were launched from the original, now-deleted AMI. After creating the new AMI, you need to update the Auto Scaling group's configuration to use it. This is done by creating a new launch template that references the newly created AMI. Finally, you must update the Auto Scaling group to use this new launch template. Reducing or increasing desired capacity will not resolve the underlying issue of a missing AMI. Copying a public OS AMI would require re-installing and configuring the application, which is not ideal for a "fully baked" custom AMI.