When needs require low-latency access to data from multiple regions, which pattern is commonly used?

When needs require low-latency access to data from multiple regions, which pattern is commonly used?

• A. DynamoDB Global Tables
• B. S3 Cross-Region Replication
• C. RDS Cross-Region Read Replicas
• D. CloudFront for content

Answer: (A)

When you need low-latency access to data from users in multiple regions, the pattern is to use a globally replicated data store that supports multi-region writes. DynamoDB Global Tables fit this need by creating a single logical table replicated across multiple AWS regions. Writes can occur in any region and are asynchronously replicated to the others, enabling local reads and writes with low latency in all regions. This active‑active setup means you don’t have to route all traffic to a single region, which reduces cross‑region latency and improves resilience. Be aware that replication across regions is eventual, so cross‑region reads may reflect the latest write with a small delay. Within a single region you can perform strongly consistent reads if needed. Among the other options, S3 Cross-Region Replication targets object copies and is not a multi-master database pattern; RDS cross-region read replicas are read-only in replica regions and do not provide multi-region write capability; CloudFront serves cached static content rather than serving as a global data store for dynamic reads/writes.

When you need low-latency access to data from users in multiple regions, the pattern is to use a globally replicated data store that supports multi-region writes. DynamoDB Global Tables fit this need by creating a single logical table replicated across multiple AWS regions. Writes can occur in any region and are asynchronously replicated to the others, enabling local reads and writes with low latency in all regions. This active‑active setup means you don’t have to route all traffic to a single region, which reduces cross‑region latency and improves resilience.

Be aware that replication across regions is eventual, so cross‑region reads may reflect the latest write with a small delay. Within a single region you can perform strongly consistent reads if needed. Among the other options, S3 Cross-Region Replication targets object copies and is not a multi-master database pattern; RDS cross-region read replicas are read-only in replica regions and do not provide multi-region write capability; CloudFront serves cached static content rather than serving as a global data store for dynamic reads/writes.