Your company is getting ready to make a major public announcement of a social media site on AWS. The website runs on EC2 instances deployed across multiple Availability Zones with a Multi-AZ RDS MySQL Extra Large DB Instance. The site performs many small reads and writes per second and relies on an eventual consistency model. After comprehensive tests, you discover that there is read contention on RDS MySQL. Which are the best approaches to meet these requirements? Choose 2 answers from the options below.

Answer options:

A.Deploy ElasticCache in-memory cache with Multi-AZ.
B.Implement sharding to distribute load to multiple RDS MySQL instances.
C.Increase the RDS MySQL Instance size and Implement provisioned IOPS.
D.Add an RDS MySQL read replica in each availability zone.

Answer – A and D
Implement Read Replicas and Elastic Cache.
Amazon RDS Read Replicas provide enhanced performance and durability for database (DB) instances. This replication feature makes it easy to elastically scale out beyond the capacity constraints of a single DB Instance for read-heavy database workloads. You can create one or more replicas of a given source DB Instance and serve high-volume application read traffic from multiple copies of your data, thereby increasing aggregate read throughput.
For more information on Read Replica’s, please visit the below link:
https://aws.amazon.com/rds/details/read-replicas/
Amazon ElastiCache is a web service that makes it easy to deploy, operate, and scale an in-memory data store or cache in the cloud. The service improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory data stores instead of relying entirely on slower disk-based databases. 
For more information on Amazon ElastiCache, please visit the below link:
https://aws.amazon.com/elasticache/