A database administrator needs to automate the backup process for an Amazon RDS for MySQL DB instance. The backups must be retained for 30 days and should be taken daily. Which AWS service should be used to implement this automation?
RDS automated backups can be enabled with a retention period of up to 35 days and perform daily backups automatically.
Why this answer
Amazon RDS automated backups are the native, built-in mechanism for backing up RDS DB instances. They automatically take daily snapshots during the backup window and retain transaction logs for point-in-time recovery. By default, the retention period can be set from 1 to 35 days, so configuring it to 30 days meets the requirement without any additional services or custom scripting.
Exam trap
The trap here is that candidates may over-engineer the solution by choosing AWS Backup or Lambda, not realizing that RDS automated backups natively support daily backups with a configurable retention period up to 35 days, making them the simplest and most appropriate choice.
How to eliminate wrong answers
Option A is wrong because Amazon S3 lifecycle policies manage the transition and expiration of objects stored in S3 buckets, not the scheduling or retention of RDS backups. Option B is wrong because AWS Backup is a centralized backup service that can back up RDS instances, but it is not required for this simple automation—RDS automated backups already provide daily backups with configurable retention natively. Option C is wrong because while AWS Lambda with custom scripts could be used to trigger manual snapshots, it adds unnecessary complexity and operational overhead when the built-in automated backup feature of RDS directly satisfies the requirement.