A multi-county water authority wants a landing-zone style baseline with a dedicated logging account, a security tooling account, and separate workload accounts. Which approach fits Associate-level multi-account security strategy?
Select an answer to reveal the explanation.
Short Explanation
Picture a water district campus: one building for cameras (logging), one for security tools, and separate buildings for treatment plants (workloads). Control Tower plus Organizations lays that campus out with guardrails. Stuffing everything into one account or inventing an SAP-sized rewrite misses the Associate target.
Full Explanation
Associate-depth multi-account strategy uses AWS Organizations, often with AWS Control Tower, to provision a baseline of accounts (for example log archive, security tooling, and workload accounts) with preventive and detective guardrails. Collapsing all functions into one account increases blast radius. Omitting Organizations removes centralized governance. Professional multi-account transformation essays belong to SAP-C02 depth, not this item’s Associate landing-zone selection.