DOP-C02 · Question #458
A company uses a trunk-based development branching strategy. The company has two AWS CodePipeline pipelines that are integrated with a Git provider. The pull_request pipeline has a branch filter…
The correct answer is B. Configure the pull_request pipeline to use PARALLEL mode. Configure the main_branch pipeline. In CodePipeline's execution mode, PARALLEL mode for pull_request pipelines ensures that multiple feature branches can be tested simultaneously for quick feedback. QUEUED mode for main_branch ensures deployments run sequentially -- each must finish before the next begins…
Question
A company uses a trunk-based development branching strategy. The company has two AWS CodePipeline pipelines that are integrated with a Git provider. The pull_request pipeline has a branch filter that matches the feature branches. The main_branch pipeline has a branch filter that matches the main branch. When pull requests are merged into the main branch, the pull requests are deployed by using the main_branch pipeline. The company's developers need test results for all submitted pull requests as quickly as possible from the pull_request pipeline. The company wants to ensure that the main_branch pipeline's test results finish and that each deployment is complete before the next pipeline execution. Which solution will meet these requirements?
Options
- AConfigure the pull_request pipeline to use SUPERSEDED mode. Configure the main_branch
- BConfigure the pull_request pipeline to use PARALLEL mode. Configure the main_branch pipeline
- CConfigure the pull_request pipeline to use PARALLEL mode. Configure the main_branch pipeline
- DConfigure the pull_request pipeline to use QUEUED mode. Configure the main_branch pipeline to
How the community answered
(34 responses)- A3% (1)
- B85% (29)
- C3% (1)
- D9% (3)
Explanation
In CodePipeline's execution mode, PARALLEL mode for pull_request pipelines ensures that multiple feature branches can be tested simultaneously for quick feedback. QUEUED mode for main_branch ensures deployments run sequentially -- each must finish before the next begins, preventing overlap. This configuration aligns with AWS CodePipeline best practices for trunk-based development and concurrent test pipelines.
Topics
Community Discussion
No community discussion yet for this question.