The company is backing up EC2 instances, Amazon EFS file systems, and Amazon RDS DB instances and must meet these constraints: custom daily/weekly/monthly retention; immediate cross-Region replication of backups; a single view of backup status across the environment; immediate notifications on any backup failure. Which combination of steps meets these requirements with minimal operational overhead? (Choose three.)

AWS Backup is the central service for managing backups across multiple AWS services, including EC2, EFS, and RDS, directly addressing the need for a single view and custom retention. Creating an AWS Backup plan with backup rules for daily, weekly, and monthly retention allows for granular control over backup schedules and retention periods. Configuring the AWS Backup plan to copy backups to another AWS Region provides immediate cross-Region replication, a key requirement. Integrating an Amazon SNS topic with the AWS Backup plan allows for immediate notifications on backup failures by filtering for jobs not in the BACKUPJOBCOMPLETED state. Incorrect options: A Lambda function for replication and notifications would add unnecessary operational overhead and complexity, as AWS Backup handles these natively. Amazon Data Lifecycle Manager (DLM) is primarily for EC2 instance and EBS volume snapshots, not EFS or RDS, and wouldn't provide a single view. Native manual RDS snapshots are not scalable, introduce significant operational overhead, and do not integrate with a centralized backup solution or cross-Region replication requirements.