AWS Certified DevOps Engineer – Professional (DOP-C02) — Question 196
A company recently deployed its web application on AWS. The company is preparing for a large-scale sales event and must ensure that the web application can scale to meet the demand.
The application's frontend infrastructure includes an Amazon CloudFront distribution that has an Amazon S3 bucket as an origin. The backend infrastructure includes an Amazon API Gateway API, several AWS Lambda functions, and an Amazon Aurora DB cluster.
The company's DevOps engineer conducts a load test and identifies that the Lambda functions can fulfil the peak number of requests. However, the DevOps engineer notices request latency during the initial burst of requests. Most of the requests to the Lambda functions produce queries to the database. A large portion of the invocation time is used to establish database connections.
Which combination of steps will provide the application with the required scalability? (Choose three.)
Answer options
- A. Configure a higher reserved concurrency for the Lambda functions.
- B. Configure a higher provisioned concurrency for the Lambda functions.
- C. Convert the DB cluster to an Aurora global database. Add additional Aurora Replicas in AWS Regions based on the locations of the company's customers.
- D. Refactor the Lambda functions. Move the code blocks that initialize database connections into the function handlers.
- F. Use Amazon RDS Proxy to create a proxy for the Aurora database. Update the Lambda functions to use the proxy endpoints for database connections.
Correct answer: B, C, F
Explanation
Option B is correct because increasing the provisioned concurrency allows Lambda functions to pre-warm and respond faster to requests, reducing latency. Option C is also valid as converting to an Aurora global database and adding replicas can enhance performance by reducing latency for geographically distributed users. Option F is appropriate because using Amazon RDS Proxy can help manage database connections efficiently, thus reducing the overhead of establishing connections. Options A and D are not as effective in addressing the initial request latency issue as the chosen options.