Q66 — AWS SAA-C03 Ch.10

Question 66 of 100 | ← Chapter 10

Q666. A company has a mobile game that reads most of its metadata from an Amazon RDS DB instance. As the game increased in popularity, developers noticed slowdowns related to the game's metadata load times. Performance metrics indicate that simply scaling the database will not help. A solutions architect must explore all options that include capabilities for snapshots, replication, and sub-millisecond response times. What should the solutions architect recommend to solve these issues?

Correct Answer: C. Add an Amazon ElastiCache for Redis laver in front of the database

Explanation

To solve the issues related to slowdowns in metadata load times for a mobile game that reads most of its metadata from an Amazon RDS DB instance, and considering the requirements of snapshots, replication, and sub-millisecond response times, the solution that the solutions architect should recommend is:C. Add an Amazon ElastiCache for Redis layer in front of the database.Here's the rationale behind this solution:Option C: Add an Amazon ElastiCache for Redis layer in front of the database. Adding an Amazon ElastiCache for Redis layer in front of the database can significantly improve performance and reduce load times. Redis is an in-memory data store that provides sub-millisecond response times, making it well-suited for use cases that require fast data retrieval. By caching frequently accessed metadata in ElastiCache for Redis, subsequent read requests can be served directly from the cache, avoiding the need to query the database every time. This reduces the load on the database and improves overall performance.Option A: Migrate the database to Amazon Aurora with Aurora Replicas. While migrating to Amazon Aurora with Aurora Replicas can provide benefits like replication and improved performance, it may not address the sub-millisecond response time requirement. Aurora is a highly scalable and performant database engine, but it may not provide the same level of response times as an in-memory cache like ElastiCache for Redis.Option B: Migrate the database to Amazon DynamoDB with global tables. Migrating the database to Amazon DynamoDB with global tables can provide scalability and replication capabilities, but it may not directly address the sub-millisecond response time requirement. DynamoDB is a NoSQL database and may have different performance characteristics compared to an RDS DB instance.Option D: Add an Amazon ElastiCache for Memcached layer in front of the database. While adding an Amazon ElastiCache for Memcached layer in front of the database can provide caching capabilities, it may not offer the same level of performance and advanced features as ElastiCache for Redis. Redis is generally preferred for use cases that require more advanced data structures and features.Therefore, the most suitable solution to solve the slowdown issues and meet the requirements of snapshots, replication, and sub-millisecond response times is to add an Amazon ElastiCache for Redis layer in front of the database (Option C). This approach allows for caching frequently accessed metadata and serving read requests directly from the cache, improving performance and reducing load times.