Handling Lambda RDS Connection Exhaustion
Short answer
B Point the application to Amazon RDS Proxy to pool connections and prevent RDS exhaustion without code changes.
Question
A CloudOps Administrator must make the application more resilient to increased load without making modifications to the application code.
Which solution will meet these requirements?
Key Takeaways
RDS Proxy pools database connections to prevent Lambda-induced connection exhaustion on RDS, requiring no code changes other than the endpoint configuration.
Amazon RDS Proxy allows AWS Lambda functions to share database connections, preventing connection exhaustion on an Amazon RDS instance. This solution improves resilience without requiring application code modifications.
Common mistake: Choosing ElastiCache (A or D) because it reduces database load, but implementing caching logic strictly requires modifying application code.
Expert Analysis
Why the Answer Is Correct
Amazon RDS Proxy is specifically designed to manage database connection pooling for serverless applications like AWS Lambda. By sitting between the Lambda functions and the RDS instance, it multiplexes database connections, allowing thousands of concurrent Lambda invocations to share a much smaller number of database connections. This prevents the RDS instance from exhausting its compute resources due to connection overhead, meeting the requirement without modifying the application logic.
Why the Other Options Are Wrong
Options A and D suggest using Amazon ElastiCache (Redis or Memcached). While caching can reduce database load, integrating a caching layer requires significant modifications to the application code to implement cache-aside logic, violating the requirement. Option C suggests scaling the RDS instance based on usage via EventBridge. Scaling up compute does not inherently increase the maximum connection limit efficiently enough to handle sudden Lambda bursts, and scaling takes time, failing to prevent immediate connection exhaustion.
Community Comment Notes
As Bad_Mat noted, the correct approach is to "Use Amazon RDS Proxy with Amazon RDS" because it directly addresses the connection pooling need for Lambda without code changes.
Official Reference
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-proxy.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question involves Lambda functions overwhelming a database with connections and forbids code changes, immediately look for Amazon RDS Proxy. It is the AWS-native solution for connection pooling and multiplexing for serverless compute.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Bad_Mat 👍 1 Answered BB. Use Amazon RDS Proxy with Amazon RDS. Point the application to Amazon RDS Proxy
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All SOA-C03 Questions
Access 100 questions with complete answers and detailed explanations.
View Full SOA-C03 Practice Test →