A SaaS web app has users distributed across multiple ALBs, each with its own Auto Scaling group and EC2 fleet. There is no build stage; commits to CodeCommit must trigger simultaneous deployments to all ALBs and Auto Scaling groups. Which architecture requires the LEAST configuration?

The most efficient solution is to use a single CodePipeline with a single CodeDeploy application and multiple deployment groups. This approach centralizes the pipeline logic, reducing management overhead. CodeDeploy deployment groups allow targeting specific EC2 instances or Auto Scaling groups, enabling simultaneous deployments to all ALBs and their associated fleets in parallel within one pipeline execution. Incorrect options: Creating unique CodeDeploy applications for each ALB-Auto Scaling group pair would lead to unnecessary duplication and increased management complexity. Using a single CodeDeploy application and a single deployment group would not allow for parallel deployments to distinct ALB-Auto Scaling group pairs. Creating a separate CodePipeline for each ALB-Auto Scaling group pair would result in significant configuration duplication and make managing deployments across the entire application much more cumbersome.