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 runs applications on AWS that connect to the company's Amazon RDS database. The applications scale on weekends and at peak times of the year. The company wants to scale the database more effectively for its applications that connect to the database.
Which solution will meet these requirements with the LEAST operational overhead?
Other
Community
UAnonymous
A
Use Amazon DynamoDB with connection pooling with a target group configuration for the database. Change the applications to use the DynamoDB endpoint.
B
Use Amazon RDS Proxy with a target group for the database. Change the applications to use the RDS Proxy endpoint.
C
Use a custom proxy that runs on Amazon EC2 as an intermediary to the database. Change the applications to use the custom proxy endpoint.
D
Use an AWS Lambda function to provide connection pooling with a target group configuration for the database. Change the applications to use the Lambda function.
Explanation:
Explanation
Amazon RDS Proxy is the correct solution because:
-
Purpose-built for RDS: RDS Proxy is specifically designed to manage database connections for Amazon RDS databases, providing connection pooling and multiplexing.
-
Least operational overhead: RDS Proxy is a fully managed service that automatically handles connection pooling, failover, and scaling without requiring manual intervention or infrastructure management.
-
Automatic scaling: RDS Proxy automatically scales to handle increased connection demands during peak times (weekends and peak seasons) without manual scaling operations.
-
Improved database efficiency: By pooling and reusing connections, RDS Proxy reduces the overhead on the RDS database, allowing it to handle more application connections efficiently.
-
Easy integration: Applications simply need to connect to the RDS Proxy endpoint instead of directly to the database, with minimal code changes.
Why other options are incorrect:
-
A (DynamoDB): DynamoDB is a NoSQL database service, not a connection pooling solution for RDS. This would require migrating from SQL to NoSQL, which is a major architectural change.
-
C (Custom EC2 proxy): While this could work, it requires significant operational overhead to manage, monitor, scale, and maintain the EC2 instances running the custom proxy.
-
D (Lambda function): Lambda is not designed for persistent connection pooling. Lambda functions are stateless and have execution time limits, making them unsuitable for managing persistent database connections.
Key benefits of RDS Proxy:
- Reduces database connection overhead by up to 90%
- Improves application scalability
- Enhances database failover handling
- Provides built-in security features
- Fully managed service with automatic scaling
Comments
Loading comments...