AWS SAP-C02 · Question 36 · Domain 3.3: Performance Improvement
A company is running a popular mobile game. The backend uses Amazon API Gateway and AWS Lambda. During special events, traffic spikes from 1,000 to 50,000 requests per second within minutes. Users are experiencing 502 Bad Gateway errors during these spikes. The Lambda functions connect to an Amazon RDS Proxy, which connects to an Aurora PostgreSQL database. What is the MOST likely cause of the errors and how should it be resolved?
Answer options:
Lambda is hitting its account-level concurrency limit. Request a quota increase for Lambda concurrent executions.
API Gateway is throttling the requests. Increase the API Gateway default rate limit.
RDS Proxy is running out of connections. Increase the MaxConnections setting on the RDS Proxy.
Lambda cold starts are causing timeouts. Enable Provisioned Concurrency for the Lambda functions.
75 questions · hints · full answers · grading
Expert