DVA-C02 · Question #281
A developer is updating the production version of an AWS Lambda function to fix a defect. The developer has tested the updated code in a test environment. The developer wants to slowly roll out the up
The correct answer is D. Update the Lambda code and create a new version of the Lambda function. Create a Lambda. Lambda weighted aliases allow routing a configurable percentage of traffic to a new function version, enabling canary or gradual rollout deployments in production.
Question
A developer is updating the production version of an AWS Lambda function to fix a defect. The developer has tested the updated code in a test environment. The developer wants to slowly roll out the updates to a small subset of production users before rolling out the changes to all users. Only 10% of the users should be initially exposed to the new code in production. Which solution will meet these requirements?
Options
- AUpdate the Lambda code and create a new version of the Lambda function. Create a Lambda
- BCreate a new Lambda function that uses the updated code. Create a Lambda alias for the
- CUpdate the Lambda code and create a new version of the Lambda function. Create a Lambda
- DUpdate the Lambda code and create a new version of the Lambda function. Create a Lambda
How the community answered
(22 responses)- A5% (1)
- B9% (2)
- C14% (3)
- D73% (16)
Why each option
Lambda weighted aliases allow routing a configurable percentage of traffic to a new function version, enabling canary or gradual rollout deployments in production.
Creating a new alias that points only to the new version would route 100% of traffic to it immediately, not the required 10% subset.
Creating an entirely new Lambda function and alias introduces a separate resource with a different ARN, which would require updating the API Gateway integration and does not enable weighted traffic splitting on the original function.
An alias pointing solely to the new version with no weighted routing configuration still sends all invocations to the new code, bypassing the 10% gradual rollout requirement.
By publishing a new Lambda version and configuring a Lambda alias with a routing configuration that assigns 10% of traffic to the new version and 90% to the stable version, the developer achieves a controlled canary deployment. The alias ARN stays constant, so no API Gateway or client configuration changes are needed, and traffic can be shifted incrementally after validation.
Concept tested: Lambda alias weighted routing for canary deployments
Source: https://docs.aws.amazon.com/lambda/latest/dg/configuration-aliases.html#configuring-alias-routing
Community Discussion
No community discussion yet for this question.