Question #572
A developer is managing an AWS Lambda function that requires frequent updates. The developer needs to ensure that if a new version introduces issues, they can immediately revert traffic to the previous version with minimal effort. Which approach provides the LEAST operational overhead?
Use AWS Elastic Beanstalk to manage application versions and environments.
Use a function alias pointing to different versions.
Store each version in Amazon EFS and update the function configuration manually.
Implement AWS CloudFormation to roll back infrastructure changes.
Explanation
Answer B is correct because Lambda aliases act as pointers to specific function versions. By updating the alias to point to a new version, developers can quickly revert to a previous version by re-pointing the alias if issues arise. This approach requires minimal effort and avoids complex rollback processes.
Other options:
- A: Elastic Beanstalk adds unnecessary complexity for Lambda-centric workflows.
- C: Manual EFS updates are error-prone and time-consuming.
- D: CloudFormation rollbacks are slower and may affect unrelated resources.
Key Points:
1. Lambda aliases enable instant traffic switching between versions.
2. Aliases decouple deployment from version management.
3. Operational overhead is lowest with native Lambda versioning features.
Answer
The correct answer is: B