Q68 — AWS SAA-C03 Ch.14

Question 68 of 100 | ← Chapter 14

Q1068. A social media application is experiencing high volumes of new user requests after a recent marketing campaign. The application is served by an Amazon RDS for MySQL instance.A solutions architect examines the database performance and notices high CPU usage and many "too many connections" errors that lead to failed requests on the database. The solutions architect needs to address the failed requests.Which solution will meet this requirement?

Correct Answer: B. Deploy an RDS Proxy. Configure the application to use the RDS Proxy.

Explanation

The solution that will best address the high CPU usage and "too many connections" errors in the Amazon RDS for MySQL instance is:B. Deploy an RDS Proxy. Configure the application to use the RDS Proxy.Explanation:- RDS Proxy: This service acts as an intermediary between the application and the RDS database. It helps manage database connections more efficiently by pooling connections, which reduces the number of connections that reach the database directly. This can alleviate high CPU usage and connection limit issues, making it easier to handle spikes in user requests.Other Options:- A. Deploy an Amazon DynamoDB Accelerator (DAX) cluster: DAX is specifically designed for DynamoDB and will not help with RDS for MySQL. It won't address the connection issues or high CPU usage.- C. Migrate the database to an Amazon RDS for PostgreSQL instance: While PostgreSQL may offer different performance characteristics, migrating to a different database engine might not resolve the immediate connection issues and would require significant changes to the application.- D. Deploy an Amazon ElastiCache (Redis OSS) cluster: While caching can help reduce load on the database by storing frequently accessed data, it does not directly address connection management or the high CPU usage problem.Conclusion:Option B is the most appropriate solution, as it effectively manages connections to the RDS instance, reducing CPU load and preventing "too many connections" errors while allowing the application to scale under high demand.