Which solution will meet these requirements?
Create an AWS Backup plan to back up the DynamoDB table on the first day of each month. Specify a lifecycle policy that transitions the backup to cold storage after 6 months. Set the retention period for each backup to 7 years.
Create a DynamoDB on-demand backup of the DynamoDB table on the first day of each month. Transition the backup to Amazon S3 Glacier Flexible Retrieval after 6 months. Create an S3 Lifecycle policy to delete backups that are older than 7 years.
Use the AWS SDK to develop a script that creates an on-demand backup of the DynamoDB table. Set up an Amazon EventBridge rule that runs the script on the first day of each month. Create a second script that will run on the second day of each month to transition DynamoDB backups that are older than 6 months to cold storage and to delete backups that are older than 7 years.
Use the AWS CLI to create an on-demand backup of the DynamoDB table. Set up an Amazon EventBridge rule that runs the command on the first day of each month with a cron expression. Specify in the command to transition the backups to cold storage after 6 months and to delete the backups after 7 years.
Explanations:
This option correctly uses AWS Backup to automate the backup of the DynamoDB table every month, adheres to the compliance requirement of a 6-month availability, and retains backups for 7 years. The lifecycle policy allows transitioning to cold storage after 6 months, which meets retention needs.
While this option schedules monthly on-demand backups, transitioning to Amazon S3 Glacier Flexible Retrieval is not the optimal solution for DynamoDB backups. Also, managing the lifecycle in S3 for deletion after 7 years adds unnecessary complexity and doesn’t utilize AWS Backup capabilities.
This option relies on custom scripts and EventBridge, which introduces potential maintenance challenges. While it can meet the backup and retention requirements, it lacks the automation and lifecycle management that AWS Backup provides, making it less efficient and prone to human error.
Similar to option C, this approach uses AWS CLI and EventBridge to schedule backups. It does not utilize the native features of AWS Backup, complicating the process of transitioning and deleting backups, and could lead to errors in compliance with retention requirements.
If memory serves me right, the answer is:
Create an AWS Backup plan to back up the DynamoDB table on the first day of each month. Specify a lifecycle policy that transitions the backup to cold storage after 6 months. Set the retention period for each backup to 7 years.