A newly consolidated metro government needs AWS accounts for security, logging, shared networking, sandboxes, and each department workload. Which structure should the architect evaluate first?
Select an answer to reveal the explanation.
Short Explanation
Metro consolidation needs separate wings—security office, evidence locker (logs), roads (network), sandbox labs, and each department’s floor—not one giant shared apartment. Multi-account Organizations is that floor plan. One shared account or staff Free Tier logins are how blast radius goes citywide.
Full Explanation
AWS multi-account strategy typically isolates security tooling, immutable logging, shared networking, experimentation sandboxes, and production workloads into separate accounts under AWS Organizations. That structure limits blast radius, clarifies ownership, and enables differentiated SCPs. Collapsing everything into one account, using personal Free Tier accounts for production, or relying only on name prefixes fails isolation and governance needs for a consolidated metro government.