Q10 — AWS DOP-C02 Ch.3

Question 10 of 100 | ← Chapter 3

A DevOps engineer is designing a deployment strategy for a SaaS web application running on AWS. For application and security reasons, customers subscribing to the application are distributed across multiple Application Load Balancers (ALBs), each associated with a dedicated Auto Scaling group and Amazon EC2 instance fleet. The application does not require a build stage; when committed to AWS CodeCommit, the application pipeline triggers a synchronous deployment to the corresponding ALB, Auto Scaling group, and EC2 instance fleet. Which architecture satisfies these requirements with the least configuration?

• A. Create a single AWS CodePipeline that uses unique AWS CodeDeploy applications and deployment groups—each created for every ALB–Auto Scaling group pair—to deploy the application in parallel.
• B. Create a single AWS CodePipeline that uses a single AWS CodeDeploy application and a single deployment group to deploy the application.
• C. Create a single AWS CodePipeline that uses a single AWS CodeDeploy application and unique deployment groups—one for each ALB–Auto Scaling group pair—to deploy the application in parallel. ✓
• D. Create separate AWS CodePipelines for each ALB–Auto Scaling group pair, using an AWS CodeDeploy application and deployment group created for that same ALB–Auto Scaling group pair to deploy the application.

Correct Answer: C. Create a single AWS CodePipeline that uses a single AWS CodeDeploy application and unique deployment groups—one for each ALB–Auto Scaling group pair—to deploy the application in parallel.

Explanation

AWS CodeDeploy allows a single application to be associated with multiple deployment groups, where each deployment group can target a distinct ALB–Auto Scaling group pair (per AWS documentation). CodePipeline supports configuring multiple parallel actions in the deploy stage, each pointing to a different deployment group of the same CodeDeploy application. Option C uses a single pipeline and a single CodeDeploy application, leveraging distinct deployment groups for parallel deployments—meeting the requirement for minimal configuration. Option A requires multiple applications; Option B cannot differentiate target environments; Option D introduces redundant pipeline configurations.