A company has an application that uses an Amazon API Gateway API to invoke an AWS Lambda function. The application is latency sensitive. A developer needs to configure the Lambda function to reduce th

Question

Options

• APublish a new version of the Lambda function. Configure provisioned concurrency. Set the
• BIncrease the Lambda function's memory to the maximum amount. Increase the Lambda function's
• CIncrease the reserved concurrency of the Lambda function to a number that matches the current
• DUse Service Quotas to request an increase in the Lambda function's concurrency limit for the

• A
  82% (28)
• B
  6% (2)
• C
  3% (1)
• D
  9% (3)

Explanation

Provisioned concurrency is the AWS feature specifically designed to eliminate cold starts by pre-initializing a set number of execution environments, keeping them "warm" and ready to handle requests with consistent low latency. Option A is correct because publishing a version and configuring provisioned concurrency directly addresses the cold start problem for latency-sensitive applications.

Option B is wrong because increasing memory speeds up function execution and reduces warm invocation duration, but does nothing to prevent cold starts - the initialization overhead still occurs on the first invocation.

Option C is wrong because reserved concurrency limits the maximum concurrent executions for a function (to protect other functions from being throttled), but it does not pre-warm any execution environments or reduce cold start time.

Option D is wrong because raising the concurrency quota simply allows more simultaneous invocations; it has no effect on initialization latency - more concurrent cold starts are still cold starts.

Memory tip: Think "Provisioned = Pre-warmed, Reserved = Restricted." If a question mentions cold starts or consistent latency, the answer almost always involves provisioned concurrency, not reserved.

No community discussion yet for this question.