Q73 — AWS SAA-C03 Ch.16

Question 73 of 100 | ← Chapter 16

Q1273. A company has a transaction-processing application that is backed by an Amazon RDS MySQL database. When the load on the application increases, a large number of database connections are opened and closed frequently, which causes latency for the database transactions.A solutions architect determines that the root cause of the latency is poor connection handling by the application. The solutions architect cannot modify the application code. The solutions architect needs to manage database connections to improve the database performance during periods of high load.Which solution will meet these requirements?

Correct Answer: C. Use Amazon RDS Proxy to pool and share database connections.

Explanation

The correct solution must improve database performance during high load by optimizing connection handling without modifying the application code. Let's evaluate each option:Correct Answer: C. Use Amazon RDS Proxy to pool and share database connections.Why Option C is Best:Connection Pooling (No Code Changes Needed):Amazon RDS Proxy sits between the application and the database, managing a pool of reusable connections.Reduces connection churn (frequent opening/closing of connections) by sharing connections among multiple application requests.No application modifications are required--RDS Proxy integrates transparently via a proxy endpoint.Improves Performance & Scalability:Lowers latency by eliminating the overhead of establishing new connections for each request. Handles spikes in traffic more efficiently by reusing existing connections.Supports failover (works with Multi-AZ RDS deployments).AWS-Managed & Secure:Fully managed by AWS (no need to maintain a separate connection pooling service). Supports IAM authentication and SSL encryption for secure connections.Why Other Options Fail:A. Upgrade the database instance to a larger instance type to handle a large number of database connections.Does not address the root cause: Scaling up the instance may temporarily improve performance but does not fix inefficient connection handling.Higher costs without solving the underlying issue.Connection limits still exist (larger instances support more connections but still suffer from churn). B. Configure Amazon RDS storage autoscaling to dynamically increase the provisioned IOPS. Irrelevant to connection handling: Storage autoscaling adjusts disk performance (IOPS), not connection management.Does not reduce latency caused by frequent connection opening/closing. D. Convert the database instance to a Multi-AZ deployment. Improves high availability, not connection performance: Multi-AZ provides failover support but does not optimize connection handling.No impact on latency from connection churn.Key Comparison:RequirementAmazon RDS Proxy (C)Other OptionsFixes connection churn (root cause) (Scaling/storage/Multi-AZ don't address this) No application code changes (All others require indirect fixes or no fix) Improves latency under high load (Only RDS Proxy optimizes connections)Conclusion:Option C (Amazon RDS Proxy) is the only solution that:Directly addresses poor connection handling (root cause).Requires no code changes.Improves performance efficiently and cost-effectively.Final Answer: C