A - DynamoDB global tables provides multi-Region, and multi-active database, but it not valid "in case of data corruption". In this case, you need a backup. This solutions isn't valid. **B** - Point in Time Recovery is designed as a continuous backup juts to recover it fast. It covers perfectly the RPO, and probably the RTO. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.html C - A daily export will not cover the RPO of 15min. D - DynamoDB is serverless... so what are these EBS snapshots taken from???

The best solution to meet the RPO and RTO requirements would be to use DynamoDB point-in-time recovery (PITR). This feature allows you to restore your DynamoDB table to any point in time within the last 35 days, with a granularity of seconds. To recover data within a 15-minute RPO, you would simply restore the table to the desired point in time within the last 35 days. To meet the RTO requirement of 1 hour, you can use the DynamoDB console, AWS CLI, or the AWS SDKs to enable PITR on your table. Once enabled, PITR continuously captures point-in-time copies of your table data in an S3 bucket. You can then use these point-in-time copies to restore your table to any point in time within the retention period. ***CORRECT*** Option B. Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.

With point-in-time recovery, you can restore that table to any point in time during the last 35 days. After you enable point-in-time recovery, you can restore to any point in time from five minutes before the current time until 35 days ago. DynamoDB maintains incremental backups of your table.

A: Scalability across regions which is not required C: Glacier exports and backup restore won't meet 1 hour RPO time D EBS for DynamoDB table? Sounds impractical B: DynamoDB point-in-time recovery is for this scenario. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.html

The best option to meet the RPO of 15 minutes and RTO of 1 hour is B) Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time. The key points: DynamoDB point-in-time recovery can restore to any point in time within the last 35 days. This supports an RPO of 15 minutes. Restoring from a point-in-time backup meets the 1 hour RTO. Point-in-time recovery is specifically designed to restore DynamoDB tables with second-level granularity.

A. Global tables provide multi-region replication for disaster recovery purposes, they may not meet the desired RPO of 15 minutes without additional configuration and potential data loss. C. Exporting and importing data on a daily basis does not align with the desired RPO of 15 minutes. D. EBS snapshots can be used for data backup, they are not directly applicable to DynamoDB and cannot provide the desired RPO and RTO without custom implementation. In comparison, option B utilizing DynamoDB's built-in point-in-time recovery functionality provides the most straightforward and effective solution for meeting the specified RPO of 15 minutes and RTO of 1 hour. By enabling PITR and restoring the table to the desired point in time, the company can recover the customer information with minimal data loss and within the required time frame.

The answer is in the question. Read the question again!!! Option B. Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.

If there is anyone who is willing to share his/her contributor access, then please write to [email protected]

Option B

B is correct DynamoDB point-in-time recovery allows the solutions architect to recover the DynamoDB table to a specific point in time, which would meet the RPO of 15 minutes. This feature also provides an RTO of 1 hour, which is the desired recovery time objective for the application. Additionally, configuring DynamoDB point-in-time recovery does not require any additional infrastructure or operational effort, making it the best solution for this scenario. Option D is not correct because scheduling Amazon EBS snapshots for the DynamoDB table every 15 minutes would not meet the RPO or RTO requirements. While EBS snapshots can be used to recover data from a DynamoDB table, they are not designed to provide real-time data protection or recovery capabilities

B is correct

B is the answer

I think DynamoDB global tables also work here, but Point in Time Recovery is a better choice

I THINK B. https://dynobase.dev/dynamodb-point-in-time-recovery/

answer is D