What should the solutions architect recommend to meet these requirements?
Configure DynamoDB global tables. For RPO recovery, point the application to a different AWS Region.
Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.
Export the DynamoDB data to Amazon S3 Glacier on a daily basis. For RPO recovery, import the data from S3 Glacier to DynamoDB.
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.
Explanations:
While global tables provide cross-region replication, they do not specifically address RPO or RTO requirements related to data corruption within a single region. Additionally, pointing to a different AWS Region does not guarantee recovery from corruption within the RPO of 15 minutes.
DynamoDB point-in-time recovery (PITR) allows you to restore the table to any point in the last 35 days with a maximum RPO of 5 minutes, which meets the 15-minute RPO requirement. It also supports a relatively quick recovery time within the RTO of 1 hour.
Exporting data to Amazon S3 Glacier is not suitable for RPO recovery as S3 Glacier is designed for archival storage with longer retrieval times. Restoring from S3 Glacier can take hours to retrieve data, which exceeds the RTO of 1 hour.
Amazon EBS snapshots are not applicable to DynamoDB, as they are intended for EBS volumes. DynamoDB does not use EBS, so this approach would not work for RPO or RTO requirements related to DynamoDB data recovery.
I believe the answer is:
Configure DynamoDB point-in-time recovery. For RPO recovery, restore to the desired point in time.