Q: 12
A company is using AWS Organizations with nested OUs to manage AWS accounts. The company has
a custom compliance monitoring service for the accounts. The monitoring service runs as an AWS
Lambda function and is invoked by Amazon EventBridge Scheduler.
The company needs to deploy the monitoring service in all existing and future accounts in the
organization. The company must avoid using the organization's management account when the
management account is not required.
Which solution will meet these requirements?
Options
Discussion
C vs B here, but B nails the "all existing and future accounts" via StackSet org integration and delegated admin, which is what AWS suggests. C’s tempting since SSM Automation is powerful, but it’s missing the auto-deploy to future accounts piece. Pretty sure B is the one, unless I missed a detail. Agree?
B
Its B, C is tempting since Systems Manager can work org-wide if set up right but B actually hits all future accounts and uses delegated admin like AWS recommends.
Its B since StackSets with a delegated admin will push to all current and future org accounts automatically. You only need to use management account for initial setup, after that the delegated admin manages everything. This matches what AWS recommends for org-wide deployments and avoids overusing the management account. Pretty sure that's what the question is after, but open if anyone sees it differently.
B , this is straight out of the official AWS docs and I've seen similar in practice exams. Review the CloudFormation StackSets section and maybe do some hands-on labs for deploying org-wide resources.
Wouldn’t C miss new accounts since StackSets auto-deploy with B but not C?
B tbh
B
B
C or D had something like this in a mock, went with C.
Be respectful. No spam.