SAA-C03 Design High-Performing Architectures Practice Question
An application has been migrated to AWS, but the performance is inconsistent. The architect finds that the application uses a legacy database driver that requires persistent connections, which is exhausting database connections. What is the best way to handle this?
⚠ Common exam trap
SAA-C03 often tests the misconception that raising max_connections or adding a local pooler solves connection exhaustion, when the real fix is a managed proxy that multiplexes connections at the database endpoint.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Amazon RDS Proxy.
Amazon RDS Proxy sits between the application and the database, pooling and reusing persistent connections so that many application connections map to a small number of database connections. This directly addresses the legacy driver's persistent-connection behavior that is exhausting the database's connection limit, without requiring application changes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the max_connections parameter.
Why it's wrong here
Simply increasing the connection limit does not address the underlying issue of connection management. High numbers of open connections consume significant memory and CPU on the database server, eventually leading to performance degradation or crashes. Connection pooling is the correct architectural approach to handle high connection volume and improve efficiency.
- ✓
Use Amazon RDS Proxy.
Why this is correct
RDS Proxy sits between the application and the database to pool and reuse connections. This effectively reduces the load on the database engine, as it no longer needs to manage thousands of individual client connections. This is the optimal solution for applications that cannot be modified to use modern, efficient connection pooling.
- ✗
Implement a local database connection pooler.
Why it's wrong here
While a local pooler helps, it is not as effective as a managed service like RDS Proxy, which works across the entire application fleet. Furthermore, local poolers are harder to manage and maintain in a distributed environment, whereas RDS Proxy is a managed AWS service that offers better reliability and performance.
- ✗
Migrate to Amazon Aurora Serverless.
Why it's wrong here
Aurora Serverless is a database engine, not a connection management tool. While it is highly scalable, it still has connection limits and is not designed to solve the connection exhaustion problems caused by legacy drivers. RDS Proxy can be used with Aurora to solve the specific connection management issues identified.
About these practice questions
This SAA-C03 question is part of Courseiva's 149-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.