Solve Database Connection Storms with RDS Proxy and Lambda
A mobile game backend uses Amazon Aurora. The workload has many short-lived database connections from Lambda functions, causing connection storms. What should be added?
Quick Answer
RDS Proxy is the right addition because it sits between the database and the many short-lived Lambda invocations, pooling a smaller, stable set of actual database connections that it hands out to Lambda on demand instead of letting every invocation open and close its own direct connection to Aurora. That distinction matters because Lambda functions are inherently bursty and short-lived; each concurrent invocation can attempt its own connection, and at scale that pattern is exactly what produces a connection storm, since the database has a limit on concurrent connections that direct, uncoordinated access can quickly exhaust. By pooling and reusing connections behind the proxy, the overhead of establishing a new connection for every invocation disappears, and the database sees a much smaller, steadier number of connections regardless of how many Lambda invocations are happening concurrently. This is a targeted fix for the specific problem here, connection churn from serverless compute, rather than something like resizing the Aurora instance, which would add capacity without addressing the connection-management issue itself. Whenever a scenario describes a serverless or otherwise bursty compute layer overwhelming a relational database with many brief connections, that connection-storm pattern is the signal to reach for RDS Proxy rather than scaling the database or the compute layer directly.
⚠ Common exam trap
Candidates often think scaling the database (e.g., increasing instance size) is the answer, but the question specifically targets connection management, not compute or storage capacity, and RDS Proxy is the AWS-managed service designed exactly for this use case.
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
✓
RDS Proxy
RDS Proxy is the correct solution because it sits between Lambda functions and the Aurora database, pooling and reusing database connections. This prevents connection storms by reducing the overhead of establishing new connections for each short-lived Lambda invocation, and it also helps manage IAM authentication for Lambda functions without storing database credentials.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
An internet gateway
Why it's wrong here
An internet gateway provides VPC connectivity to the public internet and cannot pool or broker database connections. It is tempting because Lambda functions in a private subnet need it for outbound traffic, which would be the correct addition when the problem is functions unable to reach the internet, not connection storms.
- ✗
S3 Select
Why it's wrong here
S3 Select filters object contents during retrieval; it has no connection to Aurora's connection handling. It is tempting because it reduces data transferred from S3 objects, which would be the right choice for querying a subset of columns from a large CSV or JSON file stored in S3, not for pooling database connections.
- ✓
RDS Proxy
Why this is correct
RDS Proxy pools and reuses database connections, so Lambda invocations share established connections instead of opening a new one each time. This directly absorbs the short-lived connection storms described in the stem, preventing Aurora from exhausting its connection limit.
- ✗
A larger Route 53 hosted zone
Why it's wrong here
Route 53 hosted zones resolve DNS names; they play no part in database connection handling, so connection storms persist. DNS is tempting because it fronts many AWS services, but the fix is Amazon RDS Proxy, which pools and reuses Aurora connections from Lambda.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 935-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 →
Same concept, more angles
5 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A mobile game backend uses Amazon Aurora. The workload has many short-lived database connections from Lambda functions, causing connection storms. What should be added? The design must avoid adding custom operational scripts.
medium- A.An internet gateway
- B.S3 Select
- ✓ C.RDS Proxy
- D.A larger Route 53 hosted zone
Why C: RDS Proxy is the correct choice because it pools and shares database connections, reducing the overhead of establishing new connections for each Lambda invocation. This prevents connection storms by maintaining a persistent pool of connections to Aurora, which is ideal for short-lived, high-frequency connections from serverless functions like Lambda.
Variation 2. A mobile game backend uses Amazon Aurora. The workload has many short-lived database connections from Lambda functions, causing connection storms. What should be added? The architecture review board prefers a managed AWS-native control.
medium- A.An internet gateway
- B.S3 Select
- ✓ C.RDS Proxy
- D.A larger Route 53 hosted zone
Why C: RDS Proxy is a fully managed, AWS-native service that sits between Lambda functions and Aurora, pooling and reusing database connections. This prevents connection storms by reducing the overhead of establishing new connections for each short-lived Lambda invocation, and it also improves scalability and resilience by handling failover transparently.
Variation 3. A video platform uses Amazon Aurora. The workload has many short-lived database connections from Lambda functions, causing connection storms. What should be added?
medium- A.S3 Select
- B.An internet gateway
- C.A larger Route 53 hosted zone
- ✓ D.RDS Proxy
Why D: RDS Proxy sits between Lambda functions and the Aurora database, pooling and reusing database connections. This prevents the Lambda functions from overwhelming the database with many short-lived connections, which can cause connection storms and degrade performance. RDS Proxy also reduces the overhead of establishing new connections and improves scalability.
Variation 4. A video platform uses Amazon Aurora. The workload has many short-lived database connections from Lambda functions, causing connection storms. What should be added? The design must avoid adding custom operational scripts.
medium- A.S3 Select
- B.An internet gateway
- C.A larger Route 53 hosted zone
- ✓ D.RDS Proxy
Why D: RDS Proxy is the correct choice because it sits between Lambda functions and the Aurora database, pooling and reusing database connections. This prevents connection storms by reducing the overhead of establishing new connections for each short-lived Lambda invocation, without requiring custom scripts or application changes.
Variation 5. A video platform uses Amazon Aurora. The workload has many short-lived database connections from Lambda functions, causing connection storms. What should be added? The architecture review board prefers a managed AWS-native control.
medium- A.S3 Select
- B.An internet gateway
- C.A larger Route 53 hosted zone
- ✓ D.RDS Proxy
Why D: RDS Proxy is the correct choice because it manages a pool of reusable database connections, allowing Lambda functions to share and reuse connections rather than opening and closing them with each invocation. This eliminates connection storms by buffering short-lived connections from Lambda and reducing the load on the Aurora database, all as a fully managed AWS-native service.
You might also like
Similar SAA-C03 questions
- A media company serves a global audience from an Amazon S3 bucket in the us-east-1 Region. Users in Asia and Europe repo…
- A company is deploying a high-performance computing (HPC) cluster with 16 EC2 instances. The workload requires the lowes…
- A research team runs a latency-sensitive distributed training job on Amazon EC2. They deploy 80 identical nodes that exc…
- A game streaming service must use UDP for real-time gameplay traffic. For external firewall allowlisting, the service re…
- Based on the exhibit, which design change is the best way to reduce the observed read latency for this DynamoDB-backed s…
Written by Johnson Ajibi, MSc IT Security
Security Systems Architect · founder of Courseiva
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.