MENU
A company is running a serverless ecommerce application on AWS. The application uses Amazon API Gateway to invoke AWS Lambda Java functions. The Lambda functions connect to an Amazon RDS for MySQL database to store data.
During a recent sale event, a sudden increase in web traffic resulted in poor API performance and database connection failures. The company needs to implement a solution to minimize the latency for the Lambda functions and to support bursts in traffic.
Which solution will meet these requirements with the LEAST amount of change to the application?
Suggested Answer: B
Get Premium SAP-C02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
CO
Coletta
11 months ago
I agree with B, it's the most efficient way to handle traffic spikes!
LA
Lanie
11 months ago
D seems like overkill, just stick with B for minimal changes.
EL
Eleonore
11 months ago
Surprised they didn't mention auto-scaling for the database!
FI
Filiberto
11 months ago
I think A is a better choice, less complexity involved.
ME
Melinda
12 months ago
Option B sounds solid, RDS Proxy can really help with connection pooling.
DI
Dick
12 months ago
I feel like option B is the best choice since it involves the least amount of changes while still addressing the connection issues.
ZE
Zena
1 year ago
I practiced a similar question where updating Lambda to open connections outside the handler was suggested, but it seems like a bigger change than using RDS Proxy.
OL
Olga
1 year ago
I'm not entirely sure, but I think increasing provisioned concurrency might help with performance too.
EL
Elenor
1 year ago
I remember that using RDS Proxy can help manage database connections more efficiently, especially during traffic spikes.
AL
Aleta
1 year ago
I'm a bit unsure about the difference between options B and D. I'll need to double-check the details on those two solutions.
EL
Elroy
1 year ago
I'm feeling pretty confident about this one. Creating an RDS Proxy and using Secrets Manager seems like the most straightforward way to address the performance and scalability issues.
HE
Heidy
1 year ago
Okay, I think I've got a handle on this. The key is to find the solution that requires the least amount of change to the existing application. I'm leaning towards option B.
CH
Chantell
1 year ago
Hmm, I'm a bit confused by the different solutions. I'll need to make sure I understand the differences between provisioned concurrency and reserved concurrency.
RO
Roselle
1 year ago
This looks like a tricky question. I'll need to carefully read through the details and think through the different options.
VE
Verona
2 years ago
Gotta love those sudden 'sale events' that bring down the whole system. Wish I could get a bonus for that kind of performance.
JU
Junita
1 year ago
B: I agree, it's all about being prepared for those peak times to ensure smooth operation.
DE
Devorah
1 year ago
A: Definitely, it's important to have a scalable solution in place for unexpected spikes in traffic.
SO
Solange
1 year ago
B: That sounds like a solid solution. It should help with the performance during high traffic.
CH
Cherelle
1 year ago
A: B) Create an RDS Proxy endpoint for the database. Store database secrets in AWS Secrets Manager. Set up the required 1AM permissions. Update the Lambda functions to connect to the RDS Proxy endpoint. Increase the provisioned concurrency for the Lambda functions.
AN
Anastacia
2 years ago
Haha, 'reserved concurrency' for Lambda? Sounds like a fancy way of saying 'put a cap on it'.
KA
Kara
2 years ago
Hold up, why not just increase the max_connections on the RDS instance? Seems like a quick fix to me.
EL
Elroy
1 year ago
C: True, Option B might provide a more comprehensive solution for minimizing latency and handling bursts in traffic.
HE
Herman
1 year ago
B: But Option B also includes setting up an RDS Proxy endpoint and using AWS Secrets Manager for database secrets.
HE
Hermila
2 years ago
A: Option C suggests increasing the max_connections parameter on the RDS instance.
TH
Thersa
2 years ago
Hmm, I see your point. Maybe we should consider all the options before making a decision.
RE
Ressie
2 years ago
I agree with Lorita, option B seems like a more comprehensive solution.
GR
Graham
2 years ago
I like the idea of increasing the provisioned concurrency for the Lambda functions. That should help handle the traffic spikes.
CO
Corazon
2 years ago
Option B seems like the way to go. Using an RDS Proxy and Secrets Manager will help with the connection management and scaling issues.
CA
Caprice
1 year ago
It's a good choice to minimize latency and support bursts in traffic without making too many changes to the application.
SH
Sherell
1 year ago
I agree, using RDS Proxy and Secrets Manager will definitely help with the scaling and connection management.
AI
Ailene
2 years ago
B) Create an RDS Proxy endpoint for the database. Store database secrets in AWS Secrets Manager. Set up the required 1AM permissions. Update the Lambda functions to connect to the RDS Proxy endpoint. Increase the provisioned concurrency for the Lambda functions.
TH
Thersa
2 years ago
But with option A, we can minimize the latency without making too many changes.
LO
Lorita
2 years ago
I disagree, I believe option B is more suitable.
TH
Thersa
2 years ago
I think option A is the best choice.