Which combination of steps will meet these requirements with the LEAST amount of operational overhead?
(Choose three.)
Create an AWS Backup plan with a backup rule for each of the retention requirements.
Configure an AWS Backup plan to copy backups to another Region.
Create an AWS Lambda function to replicate backups to another Region and send notification if a failure occurs.
Add an Amazon Simple Notification Service (Amazon SNS) topic to the backup plan to send a notification for finished jobs that have any status except BACKUP_JOB_COMPLETED.
Create an Amazon Data Lifecycle Manager (Amazon DLM) snapshot lifecycle policy for each of the retention requirements.
Set up RDS snapshots on each database.
Explanations:
Creating an AWS Backup plan with a backup rule for each retention requirement allows for customized daily, weekly, and monthly backup schedules, aligning with regulatory and business needs.
Configuring an AWS Backup plan to copy backups to another Region ensures that backups are replicated immediately after capture, meeting the requirement for cross-region redundancy.
Creating an AWS Lambda function for backup replication and notifications adds unnecessary operational overhead compared to built-in features provided by AWS Backup, which can handle these tasks more efficiently.
Adding an Amazon SNS topic to the backup plan allows for immediate notifications upon failure of any resource backup, as it can alert when jobs have any status except BACKUP_JOB_COMPLETED.
While creating Amazon Data Lifecycle Manager (DLM) policies for snapshots could manage backup retention, it is not designed to centralize backup management or cross-region replication, thus not fully addressing the requirements.
Setting up RDS snapshots does not provide a unified backup management solution across the AWS environment and does not meet the requirement for replication to another Region or centralized status.