Q21 — AWS SAA-C03 Ch.6

Question 21 of 65 | ← Chapter 6

Q386. A gaming company has a web application that displays scores. The application runs on Amazon EC2 instances behind an Application Load Balancer. The application stores data in an Amazon RDS for MySQL database. Users are starting to experience long delays and interruptions that are caused by database read performance. The company wants to improve the user experience while minimizing changes to the application's architecture.What should a solutions architect do to meet these requirements?

Correct Answer: A. Use Amazon ElastiCache in front of the database

Explanation

To improve the user experience and minimize changes to the application's architecture in this scenario, the most suitable option would be to use Amazon ElastiCache in front of the database.Option A: Use Amazon ElastiCache in front of the databaseBy using Amazon ElastiCache, you can introduce an in-memory caching layer between the application and the database. This can significantly improve read performance by reducing the number of database queries required. ElastiCache is a managed in-memory data store service that supports popular caching engines like Redis and Memcached. By caching frequently accessed data in ElastiCache, subsequent read requests can be served directly from the cache, reducing the load the database and improving response times.Option B: Use RDS Proxy between the application and the database RDS Proxy is a fully managed database proxy service provided by AWS. It helps manage connections to the database and provides features like connection pooling, which can improve scalability and performance. While RDS Proxy can help with connection management, may not directly address the issue of long delays and interruptions caused by database read performance. Option C: Migrate the application from EC2 instances to AWS Lambda Migrating the application from EC2 instances to AWS Lambda is a serverless approach that can provide scalability and cost benefits. However, it may not directly address the database read performance issue. The performance bottleneck seems to be related to the database, so migrating the application to Lambda alone may not solve the problem.Option D: Migrate the database from Amazon RDS for MySQL Amazon DynamoDB Migrating the database from Amazon RDS for MySQL to Amazon DynamoDB is a significant change in the application's architecture. DynamoDB is a NoSQL database, and migrating from a relational database like MySQL to a NoSQL database requires careful consideration and potentially significant changes to the application code. Additionally, DynamoDB has different characteristics and limitations compared to MySQL, so it may not be the best fit for all use cases.In summary, to improve the user experience and minimize changes to the application's architecture, the recommended option is to use AmazonastiCache in front of the database. This will introduce an in-memory caching layer that can significantly improve read performance without requiring major changes to the existing application or database.