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?
Select one answer.
Marked answer: C
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Chose C1
B. Single deployment group: Won’t support multiple Auto Scaling groups and ALBs unless they’re all in one group, which is not the case here. Cannot handle independent ALB/ASG pairs cleanly. Doesn’t scale well
Chose C1
I was about to vote B since the link from xdkonorek2 shows that one deployment can include up to 10 ELBs. Nevertheless the question says multiple instead of 10.
Chose C1
Option B not feasible as it assumes a single deployment group can manage deployments across multiple ALBs and Auto Scaling groups simultaneously, which is not supported.
