Which architecture will meet these requirements with the LEAST amount of configuration?

A DevOps engineer is architecting a continuous development strategy for a company’s software as a service (SaaS) web application running on AWS. For application and security reasons users subscribing to this application are distributed across multiple. Application Load Balancers (ALBs) each of which has a dedicated Auto Scaling group and fleet of Amazon EC2 instances The application does not require a build stage and when it is committed to AWS CodeCommit, the application must trigger a simultaneous deployment to all ALBs Auto Scaling groups and EC2 fleets.

Which architecture will meet these requirements with the LEAST amount of configuration?
A . Create a single AWS CodePipeline pipeline that deploys the application in parallel using unique AWS CodeDeploy applications and deployment groups created for each ALB-Auto Scaling group pair.
B . Create a single AWS CodePipeline pipeline that deploys the application using a single AWS CodeDeploy application and single deployment group.
C . Create a single AWS CodePipeline pipeline that deploys the application in parallel using a single AWS CodeDeploy application and unique deployment group for each ALB-Auto Scaling group pair.
D . Create an AWS CodePipeline pipeline for each ALB-Auto Scaling group pair that deploys the application using an AWS CodeDeploy application and deployment group created for the same ALB-Auto Scaling group pair.

View Answer

Answer: A

Explanation:

In option B, using a single CodeDeploy application and single deployment group wouldn’t allow for simultaneous deployments to all the ALB – Auto Scaling group pairs, since it would be pointing to only one set of resources.

Option C is similar to option A but it utilizes a single CodeDeploy application. It is generally a good practice to separate concerns and resources for different environments/segments of your application which will be serviced by different ALBs, hence utilizing separate CodeDeploy applications would be a cleaner approach.

Option D, creating an individual pipeline for each pair, would require much more setup and management overhead compared to a single pipeline that manages deployments in parallel, which contradicts the requirement of the "LEAST amount of configuration".

So option A would be the most effective approach as it utilizes a single CodePipeline for orchestrating the entire deployment, but differentiates between different ALB-Auto Scaling group pairs with unique CodeDeploy applications and deployment groups, facilitating parallel deployment with minimized configuration.