Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified DevOps Engineer - Professional · AWS
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The main requirement is: "To prevent this blockage, the development team wants to run the unit and integration tests on each pull request before it is merged." Option B doesn’t stop someone from merging a PR even if the tests fail — it's informational only unless you add more enforcement logic manually (which Option A includes by design). No Approval Integration: There is no mechanism in B to integrate CodeBuild results with CodeCommit's approval rules or to block the merge. That means a developer can still manually merge a PR before the tests complete or even if they fail. Manual Enforcement Needed: You'd need to custom build additional logic (e.g., using AWS Lambda or webhooks) to actually enforce that tests must pass before allowing a merge — which Option A handles automatically with approval rules.
shouldn't review be after build and test?
These days it would be C instead of B, it's very common to reuse the same pipeline but with conditions to skip certain steps depending on the branch. https://aws.amazon.com/blogs/devops/aws-codepipeline-adds-support-for-branch-based-development-and-monorepos/