DVA-C02 Deployment Practice Question
A company uses AWS CodePipeline with a manual approval step before deployment. The developer wants to ensure that if a pipeline execution is waiting for approval and new code is pushed, the awaiting execution is canceled and a new one starts with the latest code. Which pipeline execution mode should be configured?
⚠ Common exam trap
Watch out — candidates often confuse Superseded with Queued, assuming that queuing is the default or safest option, but they miss that Superseded is specifically designed to replace pending executions with the latest code push.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Superseded
The Superseded execution mode is correct because it automatically cancels any currently running or waiting pipeline execution when a new one is triggered, ensuring that only the latest code proceeds through the pipeline. This is ideal for scenarios with manual approval steps where stale executions should not block or delay the deployment of the most recent commit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Queued
Why it's wrong here
In Queued mode, if a new source change is detected while a pipeline execution is already in progress, the new execution will be placed in a queue. It will only begin processing once the currently running execution has successfully completed or failed. This mode ensures sequential processing of changes but does not cancel any existing execution, meaning the manual approval for the initial execution would still be pending and relevant until that execution finishes.
- ✓
Superseded
Why this is correct
The Superseded execution mode is designed to prioritize the latest changes by canceling any currently running pipeline execution when a new source revision is detected. This ensures that the manual approval step, if present, will always apply to the most recent code changes, preventing the deployment of outdated versions. A new pipeline execution is then immediately initiated with the latest code, requiring a fresh approval for the most current state.
- ✗
Parallel
Why it's wrong here
In Parallel execution mode, AWS CodePipeline allows multiple pipeline executions to run concurrently, each triggered by a new source change. If a new change arrives while an execution is awaiting manual approval, a new, separate execution will start without canceling the previous one. This could lead to multiple pending approvals for different code versions or potentially deploying an older version if its approval is granted after a newer version has already started processing.
- ✗
Single
Why it's wrong here
'Single' is not a recognized or configurable execution mode within AWS CodePipeline. Pipeline execution modes are limited to 'Queued', 'Superseded', and 'Parallel', which define how the pipeline handles new source revisions when an execution is already active. Therefore, selecting 'Single' as an execution mode is not a valid option for managing pipeline behavior.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DVA-C02 question from scratch — 724 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DVA-C02
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A developer uses AWS CodePipeline with a manual approval step before deployment. The developer wants to ensure that if a new commit is pushed while a pipeline execution is waiting for approval, the waiting execution is canceled and a new one starts with the latest commit. Which pipeline execution mode should be configured?
easy- A.Queued
- ✓ B.Superseded
- C.Parallel
- D.Single
Why B: The Superseded execution mode is designed to automatically cancel any in-progress pipeline execution when a new commit is pushed, and start a new execution with the latest source changes. This ensures that the manual approval step does not block newer commits, as the waiting execution is replaced by the one triggered by the latest commit. In contrast, other modes either queue or run executions in parallel, which would not cancel the waiting approval step.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DVA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DVA-C02 exam.