A municipal holding structure needs agency accounts grouped into Organizational Units plus one rolled-up payer invoice. Which AWS capability set addresses both needs?
Select an answer to reveal the explanation.
Short Explanation
Need neat agency folders and one combined invoice? That is AWS Organizations. Use OUs for structure and consolidated billing for the rollup.
Full Explanation
A municipal holding structure that needs agency accounts grouped into Organizational Units plus one rolled-up payer invoice should use AWS Organizations, which supports OUs for account structure and consolidated billing for a single payer rollup. Organizations is the multi-account governance backbone: OUs nest accounts for policy application, while consolidated billing produces the combined invoice leadership wants.
Amazon S3 versioning protects object history but does not organize accounts or invoices. Amazon EC2 Auto Scaling adjusts capacity rather than multi-account billing structure. AWS Glue crawlers catalog datasets rather than create Organizational Units. Storage, scaling, and ETL features are not multi-account org services.
Exam caveat: Organizations = accounts, OUs, SCPs, consolidated billing. Control Tower builds on Organizations for landing zones. Do not pick random data services when the stem says OUs and payer invoice.
Operational check: create OUs for PublicSafety, Parks, and Corporate, move accounts into OUs, attach SCPs carefully, confirm consolidated billing is active, test that a member account charge appears on the payer invoice, and document account vending so new agencies land in the correct OU automatically.