How to Roll Back an AWS Lambda Function with Minimal User Impact?
Short answer
B Change the application to use an alias that points to the current version. Deploy the new version of the code. Update the alias to direct 10% of users to the newly deployed version. If too many errors are encountered, send 100% of traffic to the previous version.
Question
Key Takeaways
This question tests knowledge of Lambda alias traffic shifting to achieve canary deployments, where the key is minimizing user impact by limiting exposure to a new version rather than exposing all users at once.
To roll back an AWS Lambda function with minimal impact on users, use Lambda aliases with weighted traffic routing (canary deployment). This allows a small percentage of traffic to test the new version before full rollout.
Common mistake: Many candidates choose Option A because it describes a valid rollback mechanism using aliases and versions, but it fails the 'minimal impact' requirement since 100% of users are immediately routed to the new version before any errors are detected.
Expert Analysis
The correct answer is Option B because it leverages AWS Lambda alias traffic shifting to implement a canary deployment strategy. By directing only 10% of traffic to the newly deployed version, the developer can monitor for errors while limiting the blast radius. If issues are found, the alias can be instantly reconfigured to send 100% of traffic back to the previous version, impacting only the small subset of users who were routed to the new version.
Why Option A is incorrect: While Option A describes a functional rollback using aliases and versions, it updates the alias to point 100% of traffic to the new version immediately. This means all users are exposed to potential errors until the developer notices and reverts the alias, which violates the "minimal impact" requirement.
Why Option C is incorrect: Option C suggests deploying directly to $LATEST and switching the ARN in the application. This is operationally slow, requires application changes, and does not use Lambda's built-in versioning and aliasing features for safe deployments.
Why Option D is incorrect: Option D is overly complex and unnecessary. Creating multiple aliases and a "router" alias adds administrative overhead without providing additional benefit over the simpler approach in Option B. Lambda aliases natively support weighted traffic routing without needing a separate router alias.
Community consensus strongly supports Option B, with commenters noting that Option A exposes 100% of users to risk, while Option B's canary approach limits impact to only 10% of traffic.
Official Reference
https://docs.aws.amazon.com/lambda/latest/dg/configuring-alias-routing.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When an AWS exam question emphasizes 'minimal impact' or 'least disruption,' look for answers involving gradual rollouts, canary deployments, or traffic shifting. Avoid options that expose all users to a change simultaneously, even if the rollback mechanism itself is valid.
Community Votes
80% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 10 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 10
-
tomchandler077 👍 5Option B is the best choice for achieving the objective with minimal impact on users. It uses a canary deployment strategy, which allows for testing the new version on a smaller scale before a full rollout. This method provides a balance between risk management and operational simplicity, ensuring that any potential negative impacts of the new deployment are contained and easily reversible.
-
wh1t4k3r 👍 2 Answered BFor people voting A: you have no idea what is the traffic load to the application. Using the method described on A will affect 100% of all users all at once until you are able to rollback. B divertes 10% of traffic only than can be easly switched back and would impact only 10% of users
-
KennethNg923 👍 1 Answered BB Update the alias to direct 10% of users to the newly deployed version -> minimal impact
-
preachr 👍 1 Answered Bhttps://docs.aws.amazon.com/lambda/latest/dg/configuring-alias-routing.html
-
rdiaz 👍 3 Answered BMinimal impact
Show 5 more comments
-
catoteja 👍 2B looks better
-
siheom 👍 2SHOULD BE A
-
Alagong 👍 2 Answered AVOTE A
-
blow96 👍 1A is correct
-
piipo 👍 1 Answered BB is best
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DVA-C02 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DVA-C02 Practice Test →