A city council IT committee wants chargeback-friendly AWS boundaries that match departments such as police, parks, and finance instead of one shared production account. Which account-structure approach aligns to that need?
Select an answer to reveal the explanation.
Short Explanation
If parks and police share one cash register drawer, the council will never know who spent what. Give departments account boundaries that match the org chart so chargeback has a clean line of sight.
Full Explanation
Account structure is a primary lever for cost visibility and blast-radius isolation. Aligning accounts (or tightly governed account groups) to departments supports chargeback when combined with tagging and consolidated billing. A single shared production account obscures ownership and complicates SCPs and quotas. Turning off consolidated billing removes organizational cost management rather than improving it.