Exam AWS Certified Solutions Architect - Professional SAP-C02 topic 1 question 491 discussion

While option B improves startup performance, it is generally more expensive than SnapStart because it keeps environments warm continuously.

Option D is right This solution provides a good balance between performance and code organization. By moving the code that generates unique IDs into the handlers, you keep the initialization code out of the way, but still make it accessible when needed. The pre-snapshot hook allows you to run some initialization code before the Lambda function is executed, which can be useful for tasks like generating unique IDs. Publishing a version of each Lambda function and activating SnapStart ensures that the functions are running with the latest code and optimizations.

For those who think option C is correct: as dzidis commented, "SnapStart does NOT support PROVISIONED CONCURRENCY" https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

https://aws.amazon.com/blogs/compute/reducing-java-cold-starts-on-aws-lambda-functions-with-snapstart/

D is correct and as dzidis referred to AWS document, you can't use both provisioned concurrency and SnapStart for the same function version. Therefore, C can't be a correct option. Refer to this section of document for more details: https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html#snapstart-concurrency

You can't use both SnapStart and provisioned concurrency on the same function version. Therefore cannot be C. https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html

D Combining provisioned concurrency with SnapStart is redundant While provisioned concurrency reduces cold start latency, it is more costly compared to SnapStart because it keeps a set number of instances warm and ready to handle requests, even when not in use.

It is C

Provisioned concurrency – This is the number of pre-initialized execution environments allocated to your function. These execution environments are ready to respond immediately to incoming function requests. Provisioned concurrency is useful for reducing cold start latencies for functions. Configuring provisioned concurrency incurs additional charges to your AWS account.

"Lambda SnapStart for Java can improve startup performance for latency-sensitive applications by up to 10x at no extra cost". Answer C.

Leverages both versioning and provisioned concurrency. Also Lambda SnapStart for improved startup performance.