A company used IaC to create two EC2 instances that have remained unchanged for years. Rapid business growth caused the operations team to introduce an Auto Scaling group, which replaces instances during spikes. Company policy requires monthly OS security updates that sometimes require a reboot. After a recent patch that required reboot, the Auto Scaling group terminated the patched instances and launched new, unpatched instances. Which combination of actions should the solutions architect recommend to prevent this from happening again? (Choose two.)

Automating patching of an AMI and updating the launch configuration ensures that new instances launched by the Auto Scaling group are always based on the latest, patched image. This prevents unpatched instances from being launched. Invoking an Auto Scaling instance refresh then systematically replaces existing instances with new ones from the updated launch configuration. Modifying the Auto Scaling group's update policy to target the oldest launch configuration for replacement is not a standard or effective Auto Scaling group setting for ensuring patched instances. Auto Scaling groups typically replace instances based on health checks or scaling policies, not specifically targeting the "oldest launch configuration" in this manner. The correct approach for updating instances within an ASG is through an instance refresh, which leverages a new launch template/configuration.