Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 861 discussion

A or B. Can't be B because there is high volume of write no need for Elasticache

Even though option "A" makes sense, everybody discarding option "B" is focusing on improving the import process performance itself by using ElastiCache, which is basically correct. However, there is not a clear indicator that the “client-facing application” ONLY performs high volumes of write operations. In fact, this can be pointless (a “write only” database?). In my opinion, the main concern of the company is how THE REST of the application processes might be affected while this write-intensive operations run in the database. And those operations surely includes reads. Using an ElastiCache in front of the RDB instance or creating a read replica to redirect reads to might help with performance of THE REST of application when write-intensive imports processes are executing, as the query result might be cached. My vote goes to “B”

high volume of write operation -> Provisioned IOPS SSD storage

Answer A For sure we cannot choose generar purpose IOPS SSD hence I would choos provisioned one. addtionally it is a good idea to monitor performance with CloudWatch and adjust setup(provisioned IOPS) if there will be a need.

The most effective strategy for coping with that limit is to supplement disk-based databases with in-memory caching (Elasticache for Redis, Write-through strategy) I'd go for B...

Amazon RDS for MySQL DB instance with Provisioned IOPS SSD storage