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 master account. Use service-managed permissions. Set deployment options to deploy to the organization. Enable CloudFormation StackSets automatic deployment.
Create stacks in the Organizations master account. Use service-managed permissions. Set deployment options to deploy to the organization. Enable CloudFormation StackSets drift detection.
Explanations:
While this option suggests creating a stack set in member accounts, the correct approach involves creating it in the master account. It also incorrectly mentions drift detection, which is not necessary for initial deployment.
This option discusses creating stacks instead of stack sets and uses self-service permissions, which do not allow for organization-wide deployment. Automatic deployment is also not applicable here since the correct method is service-managed permissions.
This option correctly specifies creating a stack set in the Organizations master account, using service-managed permissions, and deploying to the organization. Enabling automatic deployment ensures that the stacks are created in all member accounts seamlessly.
This option incorrectly mentions creating stacks instead of stack sets and does not focus on deploying to member accounts from the master account. Drift detection is also not required for the initial deployment of resources.