DOP-C02 SDLC Automation Practice Question
A team uses AWS CodePipeline with multiple parallel actions in a stage. They notice that when one action fails, the entire stage fails and no further actions are attempted. They want the pipeline to continue with the remaining actions even if one fails, and then report the failure at the end. Which feature should they use?
⚠ Common exam trap
Many candidates confuse the action-level 'On failure' setting with the stage-level failure behavior, or assume that a custom solution like Lambda is required when a native configuration option exists.
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
✓
Configure each action with 'On failure' set to 'CONTINUE'.
AWS CodePipeline allows you to set the 'On failure' property for each action to 'CONTINUE', which instructs the pipeline to proceed with subsequent actions even if that specific action fails. This ensures that all parallel actions in the stage are attempted, and the overall stage status reflects any failures at the end, rather than aborting immediately.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure each action with a 'RunOrder' of 1 and set 'On failure' to 'ABORT'.
Why it's wrong here
ABORT is an action-level failure mode that terminates the entire pipeline execution as soon as the action fails. For parallel actions with RunOrder=1, this means other in-flight actions are cancelled mid-execution, their results are discarded, and the stage does not proceed to later stages. This is the opposite of wanting to tolerate independent failures in parallel branches.
- ✓
Configure each action with 'On failure' set to 'CONTINUE'.
Why this is correct
Setting On failure to CONTINUE on each action is the native CodePipeline mechanism for making a parallel branch's failure non-blocking. When an action configured with CONTINUE fails, it is marked as failed but the pipeline proceeds to other actions and then to subsequent stages as long as they succeed. This allows a non-critical action (e.g., a test or scan) to fail without aborting the rest of the release process.
- ✗
Set the stage's 'On failure' to 'ROLLBACK'.
Why it's wrong here
The stage-level On failure setting, including ROLLBACK, controls what happens to the entire stage when its execution fails, not individual action failures. ROLLBACK triggers a deployment rollback to the last known good revision and stops the pipeline; it never causes continued execution of other actions within the failed run. It is designed for a safety-catch behavior, not for tolerating isolated failures.
- ✗
Use a custom Lambda function to catch failures and resume the pipeline.
Why it's wrong here
There is no public CodePipeline API to resume a failed action directly, and a Lambda interceptor cannot magically flip the action's status to Succeeded. Such a custom solution would require tracking executions, waiting for results, and invoking StartPipelineExecution again, introducing race conditions and re-running successful steps. AWS's intended configuration is simply the action's On failure property, so custom Lambda code is both unnecessary and not a supported pattern for this requirement.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DOP-C02 question from scratch — 1,298 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DOP-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 DOP-C02 exam.