Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 573 discussion

The key reasons: SnapStart keeps functions initialized and ready to respond quickly, eliminating cold starts. SnapStart is optimized for applications without aggressive latency needs, reducing costs. It scales automatically to match traffic spikes, eliminating outliers when scaling up. SnapStart is a native Lambda feature with no additional charges, keeping costs low. Provisioned concurrency incurs charges for always-on capacity reserved. More costly than SnapStart. Increasing timeout and memory do not directly improve startup performance like SnapStart.

https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html "Lambda SnapStart for Java can improve startup performance for latency-sensitive applications by up to 10x at no extra cost, typically with no changes to your function code."

Lambda SnapStart it is. https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html#:~:text=RSS-,Lambda%20SnapStart,-for%20Java%20can

Lambda SnapStart for Java can improve startup performance for latency-sensitive applications by up to 10x at no extra cost, typically with no changes to your function code. https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

D is correct Lambda SnapStart for Java can improve startup performance for latency-sensitive applications by up to 10x at no extra cost, typically with no changes to your function code. The largest contributor to startup latency (often referred to as cold start time) is the time that Lambda spends initializing the function, which includes loading the function's code, starting the runtime, and initializing the function code. With SnapStart, Lambda initializes your function when you publish a function version. Lambda takes a Firecracker microVM snapshot of the memory and disk state of the initialized execution environment, encrypts the snapshot, and caches it for low-latency access. When you invoke the function version for the first time, and as the invocations scale up, Lambda resumes new execution environments from the cached snapshot instead of initializing them from scratch, improving startup latency.

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.

"SnapStart does not support provisioned concurrency, the arm64 architecture, Amazon Elastic File System (Amazon EFS), or ephemeral storage greater than 512 MB." The question says "The company wants to reduce cold starts" This means provisioned concurrency. I'm a little bit confused with D.

D https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

D is the answer Lambda SnapStart for Java can improve startup performance for latency-sensitive applications by up to 10x at no extra cost, typically with no changes to your function code. The largest contributor to startup latency (often referred to as cold start time) is the time that Lambda spends initializing the function, which includes loading the function's code, starting the runtime, and initializing the function code. https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

D is best!! A is not MOST cost effectly. lambda snapshot is new feature for lambda. https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

why not D It should work