Q41 — AWS SAA-C03 Ch.10
Question 41 of 100 | ← Chapter 10
Q641. A company wants to use an event-driven programming model with AWS Lambda. The company wants to reduce startup latency for Lambda functions that run on Java 11, The company does not have strict latency requirements for the applications. The company wants to reduce cold starts and outlier latencies when a function scales up. Which solution will meet these requirements MOST cost-effectively?
- A. Configure Lambda provisioned concurrency
- B. Increase the timeout of the Lambda functions
- C. Increase the memory of the Lambda functions
- D. Configure Lambda SnapStart. ✓
Correct Answer: D. Configure Lambda SnapStart.
Explanation
The correct answer is:D. Configure Lambda SnapStart.Configuring Lambda SnapStart is the most cost-effective solution for reducing startup latency for Lambda functions running on Java 11. SnapStart allows you to reduce cold starts and outlier latencies by pre- warming the Lambda execution environment specific to your function. Options A and C are not the best solutions in this case. Provisioned concurrency (option A) can help to reduce startup latency but it may not be cost-effective as it may result in additional costs if provisioned capacity is not fully utilized. Increasing the memory (option C) may improve performance but it may not specifically address the startup latency issue.Option B, increasing the timeout of the Lambda functions, is not directly related to reducing startup latency. It may be helpful to avoid timeouts for long-running functions, but it does not address the cold start issue. Therefore, the best solution to reduce startup latency for Lambda functions running on Java 11 and minimize costs is to configure Lambda SnapStart.Both Lambda SnapStart and provisioned concurrency can reduce cold starts and outlier latencies when a function scales up. SnapStart helps you improve startup performance by up to 10x at no extra cost. Provisioned concurrency keeps functions initialized and ready to respond in double-digit milliseconds. Configuring provisioned concurrency incurs charges to your AWS account. Use provisioned concurrency if your application has strict cold start latency requirements. You can't use both SnapStart and provisioned concurrency on the same function version.