Q54 — AWS SAA-C03 Ch.11

Question 54 of 100 | ← Chapter 11

Q754. 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?

• 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.

Correct Answer: B. Use Amazon RDS Proxy with a target group for the database. Change the applications to use the RDS Proxy endpoint.

Explanation

To scale the database more effectively for applications that connect to the database with the least operational overhead, the most suitable solution is:B. Use Amazon RDS Proxy with a target group for the database. Change the applications to use the RDS Proxy endpoint.Amazon RDS Proxy is a fully managed database proxy service provided by AWS. It helps improve scalability and availability of applications that connect to Amazon RDS databases. By using RDS Proxy, you can offload connection management and pooling tasks from your applications, allowing for efficient scaling and reducing the operational overhead.Here's why option B is the best choice:\1. Operational simplicity: Amazon RDS Proxy is a managed service, which means AWS takes care of the underlying infrastructure and maintenance tasks. This reduces the operational overhead for the company, allowing them to focus more on their applications.\2. Efficient connection pooling: RDS Proxy handles connection pooling, which eliminates the need for the applications to manage individual database connections. Connection pooling helps optimize resource utilization and improves scalability, especially during peak times.\3. Seamless integration: By changing the applications to use the RDS Proxy endpoint, the company can seamlessly integrate with the existing applications without requiring significant code changes. This ensures a smooth transition to using RDS Proxy.Options A, C, and D are not the most suitable choices in this scenario:Option A suggests using Amazon DynamoDB with connection pooling and changing the applications to use the DynamoDB endpoint. However, DynamoDB is a NoSQL database service and may not be a direct replacement for Amazon RDS. Additionally, changing the database service itself introduces complexity and may require significant modifications to the applications.Option C suggests using a custom proxy running on Amazon EC2. While this approach provides flexibility, it also introduces additional management and operational overhead. Developing and maintaining a custom proxy requires ongoing effort and resources.Option D suggests using an AWS Lambda function for connection pooling. While Lambda can be used in various scenarios, using it specifically for connection pooling introduces additional complexity. Managing and scaling the Lambda function along with the database may result in higher operational overhead.Therefore, the most appropriate solution with the least operational overhead is B: Use Amazon RDS Proxy with a target group for the database and change the applications to use the RDS Proxy endpoint.