You are working as an AWS Architect for a start-up company. They have a two-tier production website. Database servers are spread across multiple Availability Zones and are stateful.
You have configured Auto Scaling Group for these database servers with a minimum of 2 instances & a maximum of 6 instances. During post-peak hours, you observe some data loss. Which feature needs to be configured additionally to avoid future data loss (and copy data before instance termination)?

Answer options:

A.Modify the cooldown period to complete custom actions before the Instance terminates.
B.Add lifecycle hooks to Auto Scaling group.
C.Customize Termination policy to complete data copy before termination.
D.Suspend Terminate process that will avoid data loss.

Correct Answer – B
Adding Lifecycle Hooks to the Auto Scaling group puts the instance into a wait state before termination. During this wait state, you can perform custom activities to retrieve critical operational data from a stateful instance. The Default Wait period is 1 hour.
Option A is incorrect as the cooldown period will not help copy data from the instance before termination.
Option C is incorrect as the Termination policy is used to specify which instances to terminate first during scale in. Configuring termination policy for the Auto Scaling group will not copy data before instance termination.
Option D is incorrect as the Suspending Terminate policy will not prevent data loss but disrupt other processes & prevent scale-in.
For more information on lifecycle-hooks, refer to the following URLs:
https://docs.aws.amazon.com/autoscaling/ec2/userguide/lifecycle-hooks.html
https://aws.amazon.com/ec2/autoscaling/faqs/