Your company is getting ready to do a major public announcement of a social media site on AWS. The website
is running on EC2 instances deployed across multiple Availability Zones with a Multi-AZ RDS MySQL Extra
Large DB Instance. The site performs a high number of 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 two.)
A.
Deploy ElasticCache in-memory cache running in each availability zone
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
ad
1
0
Correct answers – A,D
0
0
A D
1
0
AD
1
0
http://jayendrapatil.com/aws-rds-replication-multi-az-read-replica/
0
0
AC
read = elastic cache
write = Increase the RDS MySQL Instance size and Implement provisioned IOPS
0
0
Seriously? You guys keep choosing D after it clearly states “After comprehensive tests you discover that there is read contention on RDS MSQL”?
This is clearly A and C.
1
1
I’m joking btw
It’s A and D. It posted before I could say that.
1
0
😀 exam stress
0
0
A
D
Deploy ElastiCache in-memory cache running in each availability zone
Implement sharding to distribute load to multiple RDS MySQL instances –
(this is only a read contention, the writes work fine)
Increase the RDS MySQL Instance size and Implement provisioned IOPS –
(not scalable, this is only a read contention, the writes work fine)
Add an RDS MySQL read replica in each availability zone
1
0