In order to scale and off-load read traffic of an Amazon RDS database, multiple Amazon RDS Read Replicas have been configured. What is the optimal solution to distribute the read traffic to the Amazon read replicas?

Answer options:

A.Add each read replica endpoint to a Route 53 record set. Use a Weighted routing policy to distribute the traffic.
B.Create a Network Load Balancer. Register each read replica endpoint with the load balancer target group.
C.Create an Application Load Balancer. Register each read replica endpoint with the load balancer target group.
D.Amazon RDS has a cluster reader endpoint xxx.cluster-ro-xxxxxx.us-east1.rds.amazonaws.com that provides load-balancing for read traffic.

Answer: A
Option A is CORRECT because it is possible to create a Route 53 hosted zone and record set to store the DNS endpoints of the RDS read replica instances.Each endpoint should have the same value for the weighted routing configuration to ensure equal distribution of traffic among the RDS read replicas.
Option B is incorrect because Network Load Balancer does not support RDS endpoints as a load balancing target type. IP addresses or EC2 Instance IDs are the only supported target types.
Option C is incorrect because Application Load Balancer does not support RDS endpoints as a load balancing target type. IP addresses, instance IDs, or Lambda functions are the only supported target types.
Option D is incorrect because Amazon RDS does not support the reader endpoint with automatic load-balancing of read traffic. This feature is only available for Amazon Aurora. The question does not specify that this is an Amazon Aurora cluster.
Reference:
https://aws.amazon.com/premiumsupport/knowledge-center/requests-rds-read-replicas/
https://docs.aws.amazon.com/elasticloadbalancing/latest/network/target-group-register-targets.html
https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-target-groups.html#target-type