DOP-C02 SDLC Automation 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.

• ✗

  Specify multiple email addresses in the 'ApproverEmail' field of the approval action.

  Why it's wrong here

  The approval action in CodePipeline accepts an optional 'ApproverEmail' configuration value, but that field is a plain string that resolves to exactly one email address; there is no comma-delimited or array interpretation. Even if you paste multiple addresses, CodePipeline will treat the entire string as a single invalid recipient, so notifications would not reach additional approvers. To notify multiple people, you must create an SNS topic with multiple email subscriptions and reference its ARN in the action's 'SNSTopicArn' field.

• ✗

  Set the 'Approvers' field in the approval action to a comma-separated list of IAM user ARNs.

  Why it's wrong here

  The CodePipeline manual approval action has no 'Approvers' field in its action configuration; the recognized configuration keys are 'ActionMode', 'SNSTopicArn', 'CustomData', 'ApproverEmail', and optionally 'Webhook'. Supplying a comma-separated list of IAM user ARNs would either be ignored or cause a validation error because the pipeline expects a valid action structure. Approvals are performed by any IAM principal who has permission to call 'PutApprovalResult', not by enumerating ARNs in the action definition.

• ✗

  Add multiple IAM users to the pipeline's service role.

  Why it's wrong here

  The pipeline's service role is an IAM role that CodePipeline assumes to interact with source, build, and deployment resources; adding IAM users to that role (either in its trust policy or attached policies) changes the pipeline's permissions, not the recipients of approval notifications. Even if those users gain administrative permissions on the pipeline, they are not automatically notified when a manual approval action is waiting. Notification delivery is handled separately by the SNS topic configured in the approval action, so this action does not solve the multi-recipient requirement.

• ✓

  Create an Amazon SNS topic with multiple subscribers, and configure the approval action to use that SNS topic ARN.

  Why this is correct

  This is the correct approach because CodePipeline's manual approval action has an 'SNSTopicArn' configuration field that, when set, causes the pipeline to publish an approval notification to the specified SNS topic. Each email address (or other endpoint) subscribed to that topic receives the notification, and any of those subscribers—assuming they have the necessary IAM permissions—can review and approve or reject the action via the AWS console, CLI, or API. This design cleanly supports multiple approvers and also allows you to use other SNS protocols such as SMS or Lambda for custom notification flows.

Go deeper

Related to this question