SAA-C03 · Question #524
SAA-C03 Question #524: Real Exam Question with Answer & Explanation
The correct answer is D: Use Lambda provisioned concurrency for the simulator functions.. When an AWS Lambda function is invoked, especially after periods of inactivity, it may experience cold starts that delay execution. As demand increases, the scaling behavior and latency of Lambda can affect performance. Provisioned Concurrency is an AWS feature designed specifica
Question
A manufacturing company develops an application to give a small team of executives the ability to track sales performance globally. The application provides a real-time simulator in a popular programming language. The company uses AWS Lambda functions to support the simulator. The simulator is an algorithm that predicts sales performance based on specific variables. Although the solution works well initially, the company notices that the time required to complete simulations is increasing exponentially. A solutions architect needs to improve the response time of the simulator. Which solution will meet this requirement in the MOST cost-effective way?
Options
- AUse AWS Fargate to run the simulator. Serve requests through an Application Load Balancer
- BUse Amazon EC2 instances to run the simulator. Serve requests through an Application Load
- CUse AWS Batch to run the simulator. Serve requests through a Network Load Balancer (NLB).
- DUse Lambda provisioned concurrency for the simulator functions.
Explanation
When an AWS Lambda function is invoked, especially after periods of inactivity, it may experience cold starts that delay execution. As demand increases, the scaling behavior and latency of Lambda can affect performance. Provisioned Concurrency is an AWS feature designed specifically to solve this issue. "Provisioned Concurrency keeps functions initialized and hyper-ready to respond in double-digit Why Option D is correct: Provisioned Concurrency ensures that a specified number of Lambda function instances are always warm and ready to serve requests, eliminating cold start latency. It's cost-effective for workloads with consistent usage patterns, like real-time simulations for a small user group. Maintains scalability and low overhead of Lambda without moving to managed container or EC2 Why the other options are less optimal: Option A (Fargate) and Option B (EC2): Introduce more infrastructure and higher ongoing costs for a small team with likely intermittent usage. Option C (AWS Batch): Ideal for batch jobs, not real-time simulations; also incurs higher latency due to job queuing.
Community Discussion
No community discussion yet for this question.