An application uses Amazon RDS for MySQL deployed in Multi-AZ configuration as the backend database.Users have started raising complaints regarding the performance of the application.It has been identified that the performance issues are caused by increased read activity on the database.What is the most performance optimized resolution to this problem?

Answer options:

A.Configure the application to read from the Multi-AZ standby instance.
B.Deploy an RDS Read Replica in the same AZ as the master DB instance.
C.Deploy an RDS Read Replica in a different AZ to the master DB instance.
D.Deploy an Amazon ElastiCache cluster in front of the RDS DB instance.

Answer: D
Option A is incorrect because Multi-AZ standby instances can’t be used for read queries.
Option B is incorrect because Read Replicas is not the most performant solution.Read replica performance is dependent on the instance size.Amazon ElastiCache offers a better read performance solution.
Option C is incorrect because Read Replicas is not the most performant solution.Read replica performance is dependent on the instance size.Amazon ElastiCache offers a better read performance solution.
Option D is incorrect because Amazon ElastiCache provides a sub-millisecond response for read queries.
Reference:
https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/elasticache-use-cases.html#elasticache-use-cases-data-store