A company has developed an AWS Lambda function that handles orders received through an API. The company is using AWS CodeDeploy to deploy the Lambda function as the final stage of a CI/CD pipeline. A DevOps engineer has noticed there are intermittent failures of the ordering API for a few seconds after deployment. After some investigation, the DevOps engineer believes the failures are due to database changes not having fully propagated before the Lambda function is invoked. How should the DevOps engineer overcome this?
Select one answer.
Marked answer: A
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Chose A5
In my research, there are only TWO CodeDeploy AppSpec ifecycle event hooks for Lambda deployment: BeforeAllowTraffic # Use to run tasks before traffic is shifted to the deployed Lambda function version. AfterAllowTraffic # Use to run tasks after all traffic is shifted to the deployed Lambda function version. A: (YES) Don't redirect traffic untill ready B: (NO) Block traffic until ready C: (NO) Event hook N/A for Lambda D: (NO) Event hook N/A for Lambda
Chose A1
I think A
Chose A3
D can be correct if there is a wait to database to be ready so I will go with A
