After a bad Lambda alias traffic shift for a municipal payments function, CloudWatch shows error spikes. How should operations roll back quickly using existing versioning?
Select an answer to reveal the explanation.
Short Explanation
Aliases are light switches for versions. Flip the alias back to last night's good bulb—or reverse the Beanstalk/CodeDeploy cut—and the bad release stops answering citizens. Deleting the function or silencing alarms is panic, not rollback.
Full Explanation
Application rollbacks use existing deployment versioning and traffic controls: Lambda aliases can retarget a prior version, and Beanstalk or CodeDeploy strategies can reverse a failed shift to the last successful revision. Changing unrelated settings or suppressing alarms does not restore correct code. Fast rollback is a required DVA-C02 deployment skill when a release harms production.