Your business is building a new application that will store its entire customer database on a RDS MySQL
database, and will have various applications and users that will query that data for different purposes.
Large analytics jobs on the database are likely to cause other applications to not be able to get the query
results they need to, before time out. Also, as your data grows, these analytics jobs will start to take more
time, increasing the negative effect on the other applications.
How do you solve the contention issues between these different workloads on the same data?
A.
Enable Multi-AZ mode on the RDS instance
B.
Use ElastiCache to offload the analytics job data
C.
Create RDS Read-Replicas for the analytics work
D.
Run the RDS instance on the largest size possible
Hi, correct answer is C; create read-replica’s and use those for the analytics jobs.
see also: https://aws.amazon.com/rds/details/read-replicas/
Thanks,
Frank
0
0
This is actually a difficult question. Both Elasticache and Read Replicas could help here, depending on the scenario. Elasticache is for caching previously used database queries, so if this question is asking about frequent new queries, the answer has to be C. Based on the way the question is worded, I’d have to go with C. Here’s a good discussion on EC vs RR
http://stackoverflow.com/questions/24728634/aws-elasticache-vs-rds-readreplica
0
0
c
0
0
C
0
0
C
0
0
If Elasticache only caches queries already sent, then the load would not reduce as much, as if the Read-Replicas handled the analytics work. I will gamble with my SysOps cert and go with C
0
0
between B and C. I choose “B”
Given scenario talks about the performance issues, so elastic cache is best choice to improve the performance by having in-memory operations.
0
0
C
0
0