DOP-C02 Configuration Management and IaC Practice Question

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 deployment group was deleted or renamed after the pipeline was configured

  Why this is correct

  When a pipeline's deploy action references a CodeDeploy deployment group, CodeDeploy resolves that group by name and deployment group ID at execution time. If the group was deleted or renamed after pipeline configuration, the deploy action fails with a DeploymentGroupDoesNotExist or similar error when CodeDeploy attempts the deployment. The pipeline configuration itself stores the name, not a live reference, so the failure occurs at run time, not when the pipeline is edited. This is the classic cause when the error explicitly indicates the deployment group cannot be found.

• ✗

  The Auto Scaling group associated with the deployment group has insufficient capacity

  Why it's wrong here

  Insufficient ASG capacity would not cause a missing group error. During a CodeDeploy deployment to an Auto Scaling group, CodeDeploy checks the group's desired/min/max capacity and healthy instance count. If capacity is insufficient, the deployment fails with a capacity-related error like 'The deployment failed because the Auto Scaling group's minimum size was not met' or 'Insufficient capacity' — not a 'deployment group not found' error. The group still exists and is valid, so the failure mode is entirely different.

• ✗

  The CodePipeline service role does not have permission to call CodeDeploy

  Why it's wrong here

  A missing IAM permission on the CodePipeline service role would surface as an AccessDeniedException when CodePipeline calls CodeDeploy's API, such as during CreateDeployment or GetDeployment. The error would be an authorization failure at the IAM policy evaluation level, not a 'deployment group does not exist' message. The pipeline might show a permission error in CloudTrail, and the deploy action would fail before any deployment is even created.

• ✗

  The CodeDeploy application name in the pipeline is misspelled

  Why it's wrong here

  Misspelling the application name in the pipeline configuration would cause an 'ApplicationDoesNotExist' or 'ApplicationNotFoundException' error because CodeDeploy cannot find the application, not the deployment group. Since the application is the parent container for deployment groups, a misspelled application name prevents CodeDeploy from ever reaching the deployment group lookup. The specific error would indicate the missing application, not the missing deployment group.

Go deeper

Related to this question