Ultimate access to all questions.
Answer-first summary for fast verification
Answer: Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.
## Explanation **Correct Answer: B** - Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time. **Why this is correct:** 1. **DynamoDB Point-in-Time Recovery (PITR)** provides continuous backups with a recovery point objective (RPO) of up to 35 days in the past, with granularity down to the second. This easily meets the 15-minute RPO requirement. 2. **RTO of 1 hour** is achievable with PITR as the restore process creates a new table with the data from the specified point in time, which can typically be completed within the required timeframe. 3. **PITR is specifically designed** for DynamoDB backup and recovery scenarios, offering automated, continuous backups without impacting performance. **Why other options are incorrect:** **A. Configure DynamoDB global tables:** - Global tables provide multi-region replication for disaster recovery, but they don't protect against data corruption since corruption would be replicated across regions. - This solution doesn't provide point-in-time recovery capabilities. **C. Export to Amazon S3 Glacier daily:** - Daily exports don't meet the 15-minute RPO requirement. - Glacier is designed for long-term archival, not rapid recovery scenarios. - Importing from Glacier would likely exceed the 1-hour RTO. **D. Schedule EBS snapshots for DynamoDB table:** - This is fundamentally incorrect because DynamoDB is a managed NoSQL database service that doesn't use EBS volumes. - You cannot take EBS snapshots of DynamoDB tables as they are serverless and don't have underlying EBS volumes. - Even if it were possible, the RTO would likely exceed 1 hour for a full table restore. **Key AWS Concepts:** - **RPO (Recovery Point Objective)**: Maximum acceptable amount of data loss measured in time (15 minutes) - **RTO (Recovery Time Objective)**: Maximum acceptable downtime (1 hour) - **DynamoDB PITR**: Provides continuous backups with 1-second granularity for up to 35 days - **Restore Process**: Creates a new table with restored data, maintaining the original table's settings **Best Practice:** Always enable PITR for production DynamoDB tables to protect against accidental data deletion or corruption, as it provides the most granular recovery capabilities with minimal operational overhead.
Author: LeetQuiz Editorial Team
No comments yet.
A company runs a shopping application that uses Amazon DynamoDB to store customer information. In case of data corruption, a solutions architect needs to design a solution that meets a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 1 hour.
What should the solutions architect recommend to meet these requirements?
A
Configure DynamoDB global tables. For RPO recovery, point the application to a different AWS Region.
B
Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.
C
Export the DynamoDB data to Amazon S3 Glacier on a daily basis. For RPO recovery, import the data from S3 Glacier to DynamoDB.
D
Schedule Amazon Elastic Block Store (Amazon EBS) snapshots for the DynamoDB table every 15 minutes. For RPO recovery, restore the DynamoDB table by using the EBS snapshot.