This website uses cookies to ensure you get the best experience.
Learn more.
An existing deployment pipeline must shift a small fraction of Lambda alias traffic to a new version and roll back on elevated errors. Which choices support this release? Select 2 answers.
Published
- Configure appropriate CloudWatch alarms and automatic rollback behavior in the deployment.
- Send all traffic to the new version immediately while calling the deployment canary.
- Disable alarms because a version number proves the code works.
- Overwrite the old release artifact before observing new-version behavior.
- Use a supported canary deployment configuration for the Lambda alias versions.
Comments — 0
Sign in to comment