What should the solutions architect do to meet these requirements?
Create an Amazon CloudFront distribution to serve assets from the S3 bucket. Configure S3 Cross-Region Replication. Create a new DynamoDB table in a new Region. Use the new table as a replica target for DynamoDB global tables.
Create an Amazon CloudFront distribution to serve assets from the S3 bucket. Configure S3 Same-Region Replication. Create a new DynamoDB table in a new Region. Configure asynchronous replication between the DynamoDB tables by using AWS Database Migration Service (AWS DMS) with change data capture (CDC).
Create another S3 bucket in a new Region, and configure S3 Cross-Region Replication between the buckets. Create an Amazon CloudFront distribution and configure origin failover with two origins accessing the S3 buckets in each Region. Configure DynamoDB global tables by enabling Amazon DynamoDB Streams, and add a replica table in a new Region.
Create another S3 bucket in the sine Region, and configure S3 Same-Region Replication between the buckets. Create an Amazon CloudFront distribution and configure origin failover with two origins accessing the S3 buckets. Create a new DynamoDB table in a new Region. Use the new table as a replica target for DynamoDB global tables.
Explanations:
S3 Cross-Region Replication is not necessary with CloudFront, as CloudFront will distribute the content across regions. Also, DynamoDB Global Tables should be used instead of creating a separate table and using AWS DMS for replication.
S3 Same-Region Replication is only useful within the same region and does not address the requirement of a multi-region setup. AWS DMS is also not the best choice for DynamoDB replication; DynamoDB Global Tables would be more appropriate.
This option correctly uses S3 Cross-Region Replication for assets and CloudFront for distribution, which reduces latency. DynamoDB Global Tables with replica tables in multiple regions meet the requirements for improved reliability and reduced latency.
S3 Same-Region Replication only works within the same region and does not help with reducing latency across regions. DynamoDB Global Tables are correctly mentioned, but the S3 setup is not ideal for multi-region deployment.