A company has 50 AWS accounts and wants to create an identical Amazon VPC in each account. Any changes the company makes to the VPCs in the future must be implemented on every VPC. What is the MOST op

Question

Options

• ACreate an AWS CloudFormation template that defines the VPC. Sign in to the AWS Management
• BCreate a shell script that configures the VPC using the AWS CLI. Provide a list of accounts to the
• CCreate an AWS Lambda function that configures the VPStore the account information in Amazon
• DCreate an AWS CloudFormation template that defines the VPC. Create an AWS CloudFormation

• A
  2% (1)
• B
  8% (4)
• C
  6% (3)
• D
  83% (40)

Explanation

Option D is correct because it uses AWS CloudFormation StackSets, which allows a single CloudFormation template to be deployed across multiple AWS accounts (and regions) from one central operation - and future updates to the StackSet automatically propagate to all 50 accounts simultaneously, making it the most operationally efficient approach.

Why the distractors fail:

• A uses a CloudFormation template but requires manually signing into each account to deploy it - that's 50 manual deployments and 50 manual updates every time something changes.
• B relies on a custom shell script with the AWS CLI, which is fragile, harder to maintain, lacks drift detection, and has no native multi-account orchestration.
• C involves a custom Lambda function - while automated, this is a DIY solution with no state management, no rollback capability, and more operational overhead than a managed service purpose-built for this.

Memory tip: Think of StackSets as "CloudFormation with a multiplier" - one template, one update, many accounts. Anytime an exam question involves deploying or updating infrastructure consistently across multiple accounts, StackSets is almost always the answer.

No community discussion yet for this question.