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

the best solution is to implement Amazon ElastiCache to cache the large datasets, which will store the frequently accessed data in memory, allowing for faster retrieval times. This can help to alleviate the frequent calls to the database, reduce latency, and improve the overall performance of the backend tier.

Key term is identical datasets from the database it means caching can solve this issue by cached in frequently used dataset from DB

Answer is B This will help reduce the frequency of calls to the database and improve overall performance by serving frequently accessed data from the cache instead of fetching it from the database every time. It’s is not option C as it suggests implementing an RDS for MySQL read replica to cache database calls. While read replicas can offload read operations from the primary database instance and improve read scalability, they are primarily used for read scaling and high availability rather than caching. Read replicas are intended to handle read-heavy workloads by distributing read requests across multiple instances. However, they do not inherently cache data like ElastiCache does.

Answer is B This will help reduce the frequency of calls to the database and improve overall performance by serving frequently accessed data from the cache instead of fetching it from the database every time. It’s is not option C as it suggests implementing an RDS for MySQL read replica to cache database calls. While read replicas can offload read operations from the primary database instance and improve read scalability, they are primarily used for read scaling and high availability rather than caching. Read replicas are intended to handle read-heavy workloads by distributing read requests across multiple instances. However, they do not inherently cache data like ElastiCache does.

Keyword is identical datasets

As per Amazon Q: ElastiCache can be used to cache datasets from queries to RDS databases. Some key points: While creating an ElastiCache cluster from the RDS console provides convenience, the application is still responsible for leveraging the cache. Caching query results in ElastiCache can significantly improve performance by allowing high-volume read operations to be served from cache versus hitting the database. This is especially useful for applications with high read throughput needs, as scaling the database can become more expensive compared to scaling the cache as needs increase. ElastiCache nodes can support up to 400,000 queries per second. Cost savings are directly proportional to read throughput - higher throughput applications see greater savings.

The best scenario to implement caching, identical calls to the same data sets.

B) Implement Amazon ElastiCache to cache the large datasets. The key issue is repeated calls to return identical datasets from the RDS database causing performance slowdowns. Implementing Amazon ElastiCache for Redis or Memcached would allow these repeated query results to be cached, improving backend performance by reducing load on the database.

B) Implement Amazon ElastiCache to cache the large datasets. The key issue is repeated calls to return identical datasets from the RDS database causing performance slowdowns. Implementing Amazon ElastiCache for Redis or Memcached would allow these repeated query results to be cached, improving backend performance by reducing load on the database.

Thanks Tariq for the simplified answer below: frequent identical calls = ElastiCache

frequent identical calls = ElastiCache

Tricky question, anyway.

Yes, cashing is the solution but is Elasticache compatible with RDS MySQL DB? So, what about the answer C with a DB read replica? For me it's C.

B https://www.examtopics.com/discussions/amazon/view/27874-exam-aws-certified-solutions-architect-associate-saa-c02/