Which solution meets these requirements and provides the MOST up-to-date dashboard?
Deploy an Amazon RDS DB instance in us-east-1 with a read replica instance in eu-west-2. Create an Amazon ElastiCache cluster in eu-west-2 to cache data from the read replica to generate the dashboards.
Use an Amazon DynamoDB global table in us-east-1 with replication into eu-west-2. Use multi-active replication to ensure that updates are quickly propagated to eu-west-2.
Use an Amazon Aurora global database. Deploy the primary DB cluster in us-east-1. Deploy the secondary DB cluster in eu-west-2. Configure the dashboard application to read from the secondary cluster.
Deploy an Amazon RDS for MySQL DB instance in us-east-1 with a read replica instance in eu-west-2. Configure the dashboard application to read from the read replica.
Explanations:
While deploying a read replica in eu-west-2 and using Amazon ElastiCache to cache data may improve performance, it does not meet the requirement of providing up-to-date data in less than 1 second. ElastiCache adds an additional layer that might not guarantee the fastest possible data synchronization.
DynamoDB global tables with multi-active replication are typically designed for NoSQL workloads. The company’s requirement for fast updates and complex analytical queries suggests the need for a relational database solution, making this option unsuitable.
Amazon Aurora global database allows for low-latency reads from the secondary cluster in eu-west-2, providing up-to-date data in under 1 second. Aurora also supports fast data replication between regions, which meets the performance and synchronization needs for dashboards.
Deploying a read replica in eu-west-2 for an Amazon RDS for MySQL instance in us-east-1 does not guarantee sub-second data synchronization. While read replicas are suitable for scaling read workloads, they typically have replication lag, which may not meet the requirement for real-time data access.