Bird
0
0

You set a reserved concurrency of 2 for a Lambda function but notice throttling errors even with only 2 requests at once. What is the likely cause?

medium📝 Debug Q14 of 15
AWS - Lambda
You set a reserved concurrency of 2 for a Lambda function but notice throttling errors even with only 2 requests at once. What is the likely cause?
AThe reserved concurrency setting was not applied correctly
BThe account-level concurrency limit is lower than 2
CThe function timeout is set too high
DThe function's memory size is too small
Step-by-Step Solution
Solution:
  1. Step 1: Check reserved concurrency application

    If throttling occurs at 2 requests, reserved concurrency might not be set or applied properly.
  2. Step 2: Rule out other causes

    Memory size and timeout do not cause throttling; account limit lower than 2 is unlikely if 2 requests run.
  3. Final Answer:

    The reserved concurrency setting was not applied correctly -> Option A
  4. Quick Check:

    Throttling with low requests = misconfigured concurrency [OK]
Quick Trick: Check if reserved concurrency is actually set [OK]
Common Mistakes:
  • Blaming memory size for throttling
  • Ignoring concurrency setting errors
  • Assuming timeout causes throttling

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes