AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company runs a web application that is backed by Amazon RDS. A new database administrator caused data loss by accidentally editing information in a database table. To help recover from this type of incident, the company wants the ability to restore the database to its state from 5 minutes before any change within the last 30 days.
Which feature should the solutions architect include in the design to meet this requirement?
Other
Community
UAnonymous
A
Read replicas
B
Manual snapshots
C
Automated backups
D
Multi-AZ deployments
Explanation:
Explanation
Correct Answer: C. Automated backups
Amazon RDS automated backups provide point-in-time recovery (PITR) capabilities, which is exactly what the requirement describes. Here's why:
Key Requirements Analysis:
- Restore to any point within the last 30 days - RDS automated backups retain transaction logs for the retention period (up to 35 days)
- Restore to 5 minutes before any change - Point-in-time recovery allows restoration to any second within the retention period
- Recover from accidental data modification - This is a classic use case for PITR
How Automated Backups Work:
- Daily snapshots are taken during the backup window
- Transaction logs are saved every 5 minutes
- Retention period can be configured from 1 to 35 days
- Point-in-time recovery allows restoration to any specific second within the retention period
Why Other Options Are Incorrect:
A. Read replicas - These are for scaling read operations, not for point-in-time recovery. They replicate data in near real-time but don't provide historical recovery capabilities.
B. Manual snapshots - These are user-initiated snapshots that persist until manually deleted. While they can be used for recovery, they don't provide the granular 5-minute recovery point objective (RPO) or automatic retention for 30 days.
D. Multi-AZ deployments - These provide high availability and automatic failover in case of AZ failure, but they don't provide point-in-time recovery capabilities. Multi-AZ maintains a synchronous standby replica in another AZ for failover purposes.
Best Practice Implementation:
To meet this requirement, the solutions architect should:
- Enable automated backups with a retention period of at least 30 days
- Ensure the backup window is configured appropriately
- Test the point-in-time recovery process regularly
- Consider enabling deletion protection to prevent accidental deletion of the database
This solution provides the required recovery point objective (RPO) of 5 minutes and retention period of 30 days for accidental data modifications.
Comments
Loading comments...