DOP-C02 Practice Question 51: CodePipeline Execution Mode Ordering
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 6 · question 1 of 10
A regulated company requires that every commit merged to the production branch be built and deployed through every stage of its CodePipeline pipeline, in the exact order the commits were merged. No execution may be skipped, even if a newer commit is merged while an older commit's execution is still running through the pipeline. The team already upgraded the pipeline to type V2 to gain access to the newer execution modes.
Which execution mode should the team set on the pipeline to meet this requirement?
Show answer and explanation
Answer:
QUEUED mode, available only on type V2 pipelines, processes executions strictly one at a time in the order they were queued. When an execution enters a stage, the stage locks so no other execution can enter until it finishes, and the next queued execution follows only after that. That guarantees every commit is built and deployed, in merge order, exactly what the compliance requirement asks for.
Option A describes SUPERSEDED, the actual default: a more recent execution can overtake and stop an older one still waiting at a locked stage, which is precisely the skipping the company wants to prevent.
Option C, PARALLEL, lets executions run simultaneously and independently, so a later commit's execution could finish and deploy before an earlier commit's execution does, breaking the required ordering; PARALLEL mode also does not support stage rollback.
Option D adds a manual gate but leaves the pipeline in SUPERSEDED mode, so a newer execution can still overtake and stop an older one before it ever reaches that approval action.
Reference: Set or change the pipeline execution mode