What should the solutions architect do to deploy the CloudFormation StackSets in all AWS accounts?
Create a stack set in the Organizations member accounts. Use service-managed permissions. Set deployment options to deploy to an organization. Use CloudFormation StackSets drift detection.
Create stacks in the Organizations member accounts. Use self-service permissions. Set deployment options to deploy to an organization. Enable the CloudFormation StackSets automatic deployment.
Create a stack set in the Organizations management account. Use service-managed permissions. Set deployment options to deploy to the organization. Enable CloudFormation StackSets automatic deployment.
Create stacks in the Organizations management account. Use service-managed permissions. Set deployment options to deploy to the organization. Enable CloudFormation StackSets drift detection.
Explanations:
While the option mentions creating a stack set in member accounts, it should be done in the management account instead. Service-managed permissions are appropriate, but drift detection is not necessary for deployment.
This option incorrectly suggests creating stacks instead of a stack set. Using self-service permissions is not appropriate for cross-account deployments. Automatic deployment is not valid without a stack set.
This option correctly states to create a stack set in the management account using service-managed permissions, with deployment options set to the organization, and enables automatic deployment for all member accounts.
This option incorrectly suggests creating stacks instead of a stack set in the management account. Service-managed permissions are correct, but drift detection is not necessary for the deployment process.
If I had to guess, I’d say the answer is:
Create a stack set in the Organizations management account. Use service-managed permissions. Set deployment options to deploy to the organization. Enable CloudFormation StackSets automatic deployment.