DOP-C02 · Question #164
A company has microservices running in AWS Lambda that read data from Amazon DynamoDB. The Lambda code is manually deployed by developers after successful testing. The company now needs the tests…
The correct answer is C. Create an AWS CodePipeline configuration and set up the source code step to trigger when code. Explanation Option C is correct because AWS CodePipeline provides a fully managed CI/CD pipeline that can automatically trigger when code is committed, orchestrate testing via CodeBuild, deploy via CodeDeploy, and - critically - CodeDeploy supports Lambda traffic shifting…
Question
A company has microservices running in AWS Lambda that read data from Amazon DynamoDB. The Lambda code is manually deployed by developers after successful testing. The company now needs the tests and deployments be automated and run in the cloud. Additionally, traffic to the new versions of each microservice should be incrementally shifted over time after deployment. What solution meets all the requirements, ensuring the MOST developer velocity?
Options
- ACreate an AWS CodePipeline configuration and set up a post-commit hook to trigger the pipeline
- BCreate an AWS CodeBuild configuration that triggers when the test code is pushed. Use AWS
- CCreate an AWS CodePipeline configuration and set up the source code step to trigger when code
- DUse the AWS CLI to set up a post-commit hook that uploads the code to an Amazon S3 bucket
How the community answered
(23 responses)- A4% (1)
- B17% (4)
- C74% (17)
- D4% (1)
Explanation
Explanation
Option C is correct because AWS CodePipeline provides a fully managed CI/CD pipeline that can automatically trigger when code is committed, orchestrate testing via CodeBuild, deploy via CodeDeploy, and - critically - CodeDeploy supports Lambda traffic shifting strategies (canary, linear, all-at-once) that incrementally shift traffic to new Lambda versions over time, satisfying all requirements while maximizing developer velocity.
Why the distractors are wrong:
- Option A describes a post-commit hook triggering CodePipeline, which is a valid starting point, but this answer is incomplete - it doesn't address traffic shifting or the full automation pipeline needed
- Option B is incomplete as written (cut off), but relying solely on CodeBuild omits the deployment orchestration and traffic shifting capabilities that CodeDeploy provides within a pipeline
- Option D using the AWS CLI with an S3 bucket is a manual, error-prone approach that doesn't provide automated testing, continuous deployment, or incremental traffic shifting - the opposite of developer velocity
Memory Tip
Think "Pipeline = Full Journey" - CodePipeline orchestrates the entire workflow (Source → Build → Test → Deploy), and when combined with CodeDeploy's Lambda traffic shifting, it's the complete AWS-native answer. If a question mentions incremental traffic shifting for Lambda, always think CodeDeploy + CodePipeline.
Topics
Community Discussion
No community discussion yet for this question.