AWS Certified Solutions Architect Associate SAA-C03 Practice Question
A company's application relies on a managed relational database service within the AWS cloud. The database stores essential transactional data that must be safeguarded against loss and be recoverable down to any given minute within a defined retention period. What should the company implement to achieve this level of granularity in backups?
Set up a secondary replica of the primary database in a geographically distant region for disaster recovery.
Deploy the database across multiple availability zones to extend the period for backup retention.
Implement daily incremental backups for the database to an offsite location.
Configure automatic snapshots and log backups for the database with a maximum retention period.
By configuring automated snapshots and transaction logs, the managed database service allows for point-in-time recovery. This ensures that the database can be restored to any point within the retention period, which is critical for transactional data integrity and recovery after accidental data corruption or loss. On the other hand, while creating read replicas would support scalability and availability, they are not designed for point-in-time recovery. Multi-AZ deployments focus on high availability, not extending backup retention. Lastly, scheduling snapshots at daily intervals would only permit recovery to specific times rather than any point-in-time, hence this approach would not fulfill the company's requirement for minimally granular data recovery.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What are automated snapshots in AWS databases?
Open an interactive chat with Bash
What are transaction logs in the context of AWS database services?
Open an interactive chat with Bash
How does point-in-time recovery work in AWS managed databases?