Exam AWS Certified Solutions Architect - Professional topic 1 question 529 discussion

BD https://lumigo.io/blog/aws-lambda-timeout-best-practices/ A: While this will improve the situation, it may not be enough. B: Memory – The amount of memory available to the function during execution. Choose an amount between 128 MB and 3,008 MB in 64 MB increments. Lambda allocates CPU power linearly in proportion to the amount of memory configured. At 1,792 MB, a function has the equivalent of 1 full vCPU (one vCPU-second of credits per second). All calls made to AWS Lambda must complete execution within 900 seconds. The default timeout is 3 seconds, but you can set the timeout to any value between 1 and 900 seconds. C: The problem is not with the DB. D: AWS API Gateway has a max timeout of 29 seconds for all integration types, which includes Lambda as well. It means that any API call coming through API Gateway cannot exceed 29 seconds. It makes sense for most of the APIs except for few high computational ones. E: Increase the memory not CPU.

You cannot config container being reused or not

A. https://aws.amazon.com/blogs/compute/container-reuse-in-lambda/ (Remember, you can’t depend on a container being reused, since it’s Lambda’s prerogative to create a new one instead.) B. Increase Memory is good option. (https://lumigo.io/learn/aws-lambda-timeout-best-practices/) C. No DynamoDB D. Sounds good to have less load on Lambda. Caching always gives things faster and better, lesser computation for Lambda. (https://lumigo.io/learn/aws-lambda-timeout-best-practices/) E. Not possible. Increase Memory to Increase CPU.

A and B are right - as they help optimize and improve Lambda performance.

Before even looking answers I decided to go with B,D . It is most appropriate.

B & D are the answers

A B is correct!

https://lumigo.io/blog/aws-lambda-timeout-best-practices/ A: While this will improve the situation, it may not be enough. B: Memory – The amount of memory available to the function during execution. Choose an amount between 128 MB and 3,008 MB in 64 MB increments. Lambda allocates CPU power linearly in proportion to the amount of memory configured. At 1,792 MB, a function has the equivalent of 1 full vCPU (one vCPU-second of credits per second). All calls made to AWS

I'll go with B,D

it's B,D

A B looks correct. This question is asking to reduce execution time. D will only help if caching is applicable, not always.

will go with BD

B and D is correct

B is correct

I go with BD

Answer is B and D. A- incorrect because there is no configuration in Lambda to reuse the same sandbox/contain B- is correct because when memory size increases, the total time decreases. It means AWS keeps its promise and gives proportional CPU to your function. C:- there is no need to use ElasticCache as the problem is not related to caching data from DB. D- This makes sense as it will increase performance and put less load on Lambda function. E- You need to increase memory and not CPU.

B AND D ... BUT ANOTHER EXAMPLE OF SHI** AMAZON TYPE QUESTION PERSECUTING US !!! .. A WOULD BE CORRECT https://docs.aws.amazon.com/lambda/latest/dg/best-practices.html BUT IT MENTIONS containers NOT WHAT IS SPECIFIED IN THE LINK ... SO A AND D FOR ME