Your company is running a business analytics service that uses RDS with MySQL as the main database. The database is configured with Multi-AZ. Most recently, the load on the database has increased rapidly with the launch of new features. By looking at the logs, most of the load is generated by the read-only queries. Because of the heavy read loads, the operations team has decided to put a set of read-replicas in place. The new application features are launched via a cluster of containers into the virtual machines, where all the containers are having access to the same set of configurations. How can you pair the read replicas together to make sure the application running in the containers can access them properly?

Answer options:

A.Create Amazon Route 53 weighted record sets to distribute requests across the read replicas.
B.Create an ELB and point to all the read replicas. Use the URL of the ELB to access the read replicas from the application.
C.Create an Elastic IP and create a route table entry to point the IP to the read replicas. Use the IP to access the read replicas from the application.
D.Read replica cluster is not supported in AWS. Use an external utility to create a DNS record and use the record to access the read replicas from the application.

Correct Answer: A
Option A is CORRECT because, in Route 53, you can create individual record sets for each DNS endpoint associated with your read replicas and give them the same weight. Then the read requests are distributed across multiple read replicas.
Option B is INCORRECT because the ELB cannot point to multiple replicas.
Option C is INCORRECT because this is not a workable solution. Elastic IP is an external resource, and routing the Elastic IP to read replica set is impossible.
Option D is INCORRECT because it is possible to route internal Route53 multivalve answer records to a set of IPs.