DOP-C02 SDLC Automation Practice Question
Exhibit
Refer to the exhibit.
{
"source": [
{
"provider": "S3",
"bucket": "my-source-bucket",
"object_key": "source.zip",
"region": "us-east-1"
}
],
"stages": [
{
"name": "Build",
"actions": [
{
"name": "Build",
"provider": "CodeBuild",
"project": "my-project",
"region": "us-east-1"
}
]
},
{
"name": "Deploy",
"actions": [
{
"name": "Deploy",
"provider": "CodeDeploy",
"application": "my-app",
"deployment_group": "my-group",
"region": "us-west-2"
}
]
}
]
}A DevOps engineer is reviewing the CodePipeline structure above. The pipeline fails during the Deploy stage with an error: 'The deployment group could not be found.' What is the most likely cause?
⚠ Common exam trap
Many candidates confuse the error message 'deployment group could not be found' with the deployment group not existing at all (Option C), rather than recognizing it as a region mismatch issue where the deployment group exists but in a different region than the pipeline.
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
✓
The pipeline is configured as a single-region pipeline, but the Deploy action is in a different region.
The error 'The deployment group could not be found' indicates that CodePipeline is attempting to invoke a CodeDeploy deployment in a region where the specified deployment group does not exist. If the pipeline is configured as a single-region pipeline (e.g., in us-east-1) but the Deploy action references a deployment group in a different region (e.g., us-west-2), CodePipeline will fail because it cannot resolve the deployment group across regions in a single-region pipeline configuration. Cross-region actions require explicit cross-region action configuration in the pipeline structure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The pipeline is configured as a single-region pipeline, but the Deploy action is in a different region.
Why this is correct
In CodePipeline, every pipeline is bound to a single region. If a Deploy action references a CodeDeploy application in another region, it is treated as a cross-region action and must be explicitly configured with the Region property. Without that, the pipeline attempts to execute the action in us-east-1, where no deployment group exists, producing the 'Deployment group not found' error. The fix is to add the cross-region configuration or move the Deploy action to the same region.
- ✗
The source artifact is not accessible from us-west-2.
Why it's wrong here
CodePipeline stores all artifacts in the pipeline's artifact bucket, which resides in the pipeline's region (us-east-1), and transfers them to actions as needed. The Deploy action does not directly fetch artifacts from a bucket in us-west-2; the service passes the artifact contents to the CodeDeploy handler. An inaccessible artifact would cause an S3 access or artifact-not-found error during the action execution, not a deployment group lookup failure. Therefore, artifact accessibility is not the cause of this specific error.
- ✗
The CodeDeploy application does not exist in us-west-2.
Why it's wrong here
The error message explicitly states that the deployment group is not found, not that the application is missing. If the CodeDeploy application itself did not exist in us-west-2, the failure would occur earlier when trying to reference the application, typically with an 'Application does not exist' error. The deeper problem is that the pipeline is looking in the wrong region: because the action is not configured as cross-region, CodePipeline is searching us-east-1, where the application and deployment group are simply absent. This option incorrectly identifies the resource as missing rather than the region mismatch as the root cause.
- ✗
The CodeBuild project is not configured to output artifacts.
Why it's wrong here
If the CodeBuild project were not configured to output artifacts, the pipeline would fail at the Build stage with an error such as 'Artifact does not exist' or 'No output artifact configured'. The reported failure occurs at the Deploy stage with a deployment group error, which means the build successfully produced and passed the artifact to the Deploy action. The issue is entirely within the environment of the CodeDeploy action, specifically a region mismatch, not a missing output from the build project.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every DOP-C02 question from scratch — 251 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.