Exam AWS-SysOps topic 1 question 723 discussion

THE ANSWER CAN'T BE C. The function occasionally fails due to throttling. Take note of the word: occasionally. Therefore the function runs. Setting the concurrency to 1 will make it throttle even more. If it's 0 then the function can't execute at all. The answer can't be B as well since increasing the timeout is in relation to how long the function is being executed. It has no effect on concurrent executions since the function will still execute until it finishes a certain timeframe. The answer should be D. Increasing the memory will increase the CPU power of the Lambda function and therefore will execute faster.

Answer is D https://docs.aws.amazon.com/lambda/latest/dg/best-practices.html Performance testing your Lambda function is a crucial part in ensuring you pick the optimum memory size configuration. Any increase in memory size triggers an equivalent increase in CPU available to your function.

Answer should be D

Lambda execution concurrency are shared for all Lambda functions. to fix the throttling, 1 way is to reserve the concurrency of the operation lambda function. Another way is to reduce the execution time. There is no option for reserve concurrency therefore D is selected.

Answer D. https://aws.amazon.com/blogs/aws/new-for-aws-lambda-functions-with-up-to-10-gb-of-memory-and-6-vcpus/

D. Increase the operational function memory. Seem correct

I'll go with D

This is a strangely worded question. The only variable is how many files are uploaded at the same time (or even the size of the files). Normally a function processes one file at a time, an invocation for each. For lots of files, concurrency limits are normally the issue. But there is no answer for that here. C is the opposite and is undesired. D. increasing memory might give some improvement but it is not likely to be a great improvement. A won't achieve anything. If the files are large and making the function slow to complete, then the timeout will apply (B). But invocation was successful and this is not throttling. Therefore the answer must be D, but I think the question is lame because in reality this would not make much of a difference, if any.

The answer should be D. Increasing the memory will increase the CPU power of the Lambda function and therefore will execute faster.

Before going thru the discussion, my answer was also D. Tricky one :)

Repeated Question

this question is repeated.

agreed with Tce and jpt2353. Answer is D. I dont know this problem is caused with concurrency or memory, but obviously, setting concurrency to 1 means that one of a specific lambda cannot run pararell.

Answer is C https://aws.amazon.com/premiumsupport/knowledge-center/lambda-troubleshoot-throttling/ Configure reserved concurrency Verify if you've configured reserved concurrency on your Lambda function. Check the setting using the Lambda console, or by calling the GetFunction API. Note: If a function is configured to have zero reserved concurrency, then the function is throttled because it can't process any events. Be sure to increase the value to a number greater than zero.

Answer is D https://aws.amazon.com/premiumsupport/knowledge-center/lambda-troubleshoot-throttling/ Check concurrency metrics Check for spikes in Duration metrics for your function. Concurrency depends on function duration. If your code is taking too long to execute, it might not have enough compute resources. Try increasing the function's memory setting.

Should be C . https://aws.amazon.com/premiumsupport/knowledge-center/lambda-troubleshoot-throttling/

Same question as 138. I think should be C. onfigure reserved concurrency Verify if you've configured reserved concurrency on your Lambda function. Check the setting using the Lambda console, or by calling the GetFunction API. Note: If a function is configured to have zero reserved concurrency, then the function is throttled because it can't process any events. Be sure to increase the value to a number greater than zero. https://aws.amazon.com/premiumsupport/knowledge-center/lambda-troubleshoot-throttling/