A global company with a centralized IT team manages AWS resources across 50 accounts using AWS Control Tower. The team wants to deploy a new VPC with a specific CIDR block in each account in the same AWS Region. The VPC must have identical configuration across accounts. Which approach is the MOST efficient and meets the requirement?
Control Tower account factory with StackSets automates deployment of identical resources across accounts.
Why this answer
AWS Control Tower's Account Factory combined with AWS CloudFormation StackSets enables automated, centralized deployment of identical VPC configurations across all 50 accounts in the same Region. StackSets allow you to deploy a CloudFormation template to multiple accounts and Regions from a single administrator account, ensuring consistency without manual intervention.
Exam trap
The trap here is confusing AWS Resource Access Manager (RAM) for creating separate VPCs in each account versus sharing a single VPC, and misunderstanding that SCPs only control permissions, not resource creation.
How to eliminate wrong answers
Option A is wrong because manually triggering CloudFormation templates in each account is inefficient, error-prone, and does not scale to 50 accounts, violating the 'most efficient' requirement. Option B is wrong because sharing a VPC via AWS Resource Access Manager (RAM) does not create a separate VPC in each account; it shares a single VPC, which does not meet the requirement of deploying a VPC in each account. Option D is wrong because AWS Organizations Service Control Policies (SCPs) are used to restrict permissions, not to create resources like VPCs; SCPs cannot deploy infrastructure.