AWS Certified Solutions Architect - Associate
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company has launched an Amazon RDS for MySQL DB instance. Most of the connections to the database come from serverless applications. Application traffic to the database changes significantly at random intervals. At times of high demand, users report that their applications experience database connection rejection errors.
Which solution will resolve this issue with the LEAST operational overhead?
Other
Community
UAnonymous
A
Create a proxy in RDS Proxy. Configure the users' applications to use the DB instance through RDS Proxy.
B
Deploy Amazon ElastiCache for Memcached between the users' applications and the DB instance.
C
Migrate the DB instance to a different instance class that has higher I/O capacity. Configure the users' applications to use the new DB instance.
D
Configure Multi-AZ for the DB instance. Configure the users' applications to switch between the DB instances.
Explanation:
Explanation
Correct Answer: A
Why RDS Proxy is the best solution:
-
Connection Pooling: RDS Proxy maintains a pool of established database connections that can be shared across multiple applications. This prevents connection exhaustion during traffic spikes.
-
Serverless Compatibility: RDS Proxy is specifically designed to work well with serverless applications (like AWS Lambda) that can create many concurrent connections during high demand.
-
Least Operational Overhead: RDS Proxy is a managed service that automatically handles connection management, requiring minimal configuration and maintenance.
-
Connection Reuse: Instead of each application creating new connections (which can hit database connection limits), RDS Proxy reuses existing connections efficiently.
Why other options are incorrect:
B. Amazon ElastiCache for Memcached:
- This is a caching solution, not a connection management solution
- It adds complexity for caching data, not solving connection pooling issues
- Requires application changes to implement caching logic
C. Migrate to higher I/O capacity instance:
- Higher I/O capacity doesn't solve connection limit issues
- Database connections are limited by instance type and memory, not just I/O
- Requires downtime for migration and doesn't address the root cause
D. Configure Multi-AZ:
- Multi-AZ provides high availability and failover capabilities
- Doesn't solve connection pooling or connection limit issues
- Applications would need complex logic to switch between instances
Key AWS Concepts:
- RDS Proxy is specifically designed to handle connection management for serverless applications
- Database connection limits are based on instance class (max_connections parameter)
- Serverless applications can create connection storms due to their stateless nature
- RDS Proxy helps with both security (IAM authentication) and connection management
Comments
Loading comments...