Your company has HQ in Tokyo and branch offices all over the world and is using a logistics
software with a multi-regional deployment on AWS in Japan, Europe and USA. The logistic
software has a 3-tier architecture and currently uses MySQL 5.6 for data persistence. Each
region has deployed its own database.
In the HQ region you run an hourly batch process reading data from every region to compute
cross-regional reports that are sent by email to all offices this batch process must be
completed as fast as possible to quickly optimize logistics how do you build the database
architecture in order to meet the requirements?
A.
For each regional deployment, use RDS MySQL with a master in the region and a read replica in
the HQ region
B.
For each regional deployment, use MySQL on EC2 with a master in the region and send hourly
EBS snapshots to the HQ region
C.
For each regional deployment, use RDS MySQL with a master in the region and send hourly RDS
snapshots to the HQ region
D.
For each regional deployment, use MySQL on EC2 with a master in the region and use S3 to
copy data files hourly to the HQ region
E.
Use Direct Connect to connect all regional MySQL deployments to the HQ region and reduce
network latency for the batch process
Does multi-region support read replicas?
Yes, https://aws.amazon.com/blogs/aws/cross-region-read-replicas-for-amazon-rds-for-mysql/
https://aws.amazon.com/rds/details/read-replicas/
Increased Availability
Read replicas in Amazon RDS for MySQL, MariaDB, and PostgreSQL provide a complementary availability mechanism to Amazon RDS Multi-AZ Deployments. You can promote a read replica if the source DB instance fails. You can also replicate DB instances across AWS Regions as part of your disaster recovery strategy. This functionality complements the synchronous replication, automatic failure detection, and failover provided with Multi-AZ deployments.
Yes for RDS MYSQL
https://aws.amazon.com/blogs/aws/cross-region-read-replicas-for-amazon-rds-for-mysql/
A