A company uses AWS Organizations and requires creating an Amazon SNS topic in every member account for integration with a third-party alerting system. The solutions architect used a CloudFormation template and plans to deploy it with CloudFormation StackSets. Trusted access for CloudFormation StackSets in Organizations has been enabled. What steps should the solutions architect take to deploy the StackSet across all AWS accounts?

The correct approach is to create the stack set in the Organizations management account, as this account has the necessary permissions to deploy resources across the entire organization. Using service-managed permissions allows CloudFormation StackSets to create the necessary IAM roles in target accounts automatically, simplifying deployment. Setting deployment options to deploy to the organization ensures the stack set targets all member accounts. Enabling automatic deployment ensures that new accounts added to the organization will automatically receive the SNS topic. Incorrect options: Creating a stack set in member accounts is not feasible for deploying across the entire organization. Drift detection is not directly related to the initial deployment strategy. Using self-service permissions requires manual setup of IAM roles in each target account, which is inefficient for an organization-wide deployment. Creating stacks (singular) instead of a stack set is not the correct mechanism for deploying to multiple accounts simultaneously. Drift detection is a separate feature from initial deployment.