Organizations, Control Tower and delegated administrators: SCS-C03 study notes and practice questions
What to know about Organizations, Control Tower and delegated administrators for the SCS-C03 exam, from the Security Foundations and Governance domain (14% of the exam guide), then 1 free question to test it. Part of the SCS-C03 study guide.
These questions describe a company with several accounts, an audit team that needs central logs, and a rule such as “the security team must see every account” or “new accounts must be secure from the first minute.” You choose the account structure that enforces the rule with the least manual work.
What decides the answer
The management account owns and pays for the organization. Keep workloads and everyday users out of it. Service control policies (SCPs) and resource control policies (RCPs) do not restrict it, so protect it with its own controls.
Organizational units (OUs) group accounts by purpose, such as Security, Infrastructure, Workloads and Sandbox. Attach a control to an OU and every account under it inherits the control, including accounts created later.
All features must be enabled for SCPs, RCPs and Control Tower. An organization that only has consolidated billing cannot use these controls.
Trusted access lets an AWS service, such as GuardDuty, Security Hub CSPM or AWS Config, act across the organization. Enable it from the management account before you designate an administrator for that service.
Delegated administrators are member accounts, usually a security tooling account, that run organization-wide security services. This keeps daily security work out of the management account.
Control Tower builds a landing zone. It creates a Security OU with a log archive account, which holds centralized logs, and an audit account, which security staff use to reach every account. It applies controls, which older material calls guardrails. Preventive controls use SCPs and other organization policies, detective controls use AWS Config rules, and proactive controls use CloudFormation hooks to check resources before they are created.
Account Factory creates new accounts that already meet the baseline you chose, so a team cannot start from an unsecured account.
How to choose
Scenario wording
Pick
Every new account gets the same baseline with little manual work
Control Tower with Account Factory
Logs from every account that no workload account can alter
Log archive account in the Control Tower landing zone
The security team runs GuardDuty and Security Hub CSPM for all accounts
Delegated administrator account with trusted access enabled
A control must reach accounts added later
Attach it to an OU, or enable a Control Tower control on the OU
Protect the management account from misuse
Keep workloads out of it and protect its root user; no SCP applies to it
Common traps
Running workloads in the management account, then expecting SCPs to protect them. No SCP or RCP limits the management account, which is why it should stay small.
Attaching controls to single accounts when an OU would cover future accounts automatically.
Choosing a billing-only organization when the requirement needs SCPs, RCPs or Control Tower.
Administering org-wide security from a member account’s own admin role rather than a delegated administrator that the organization manages.
Building a landing zone by hand when the requirement asks for the least operational overhead. Control Tower is the managed answer.
Read the delegated administrators guide and the Control Tower overview before the exam. The first explains which services accept a delegated administrator, and the second explains controls, the landing zone and the accounts it creates.
A healthcare company is building its AWS organization from scratch. The security team wants the log archive and audit accounts to exist before any workload account, and wants threat detection turned on automatically in each new account, managed from the audit account.
Each workload account must join its production OU only after its baseline logging and detection are confirmed. When a project ends, its account moves to a Suspended OU that blocks new resources.
Put these steps in the order the team should do them, first step first.
Put these 5 steps in order.
AA. Create each new workload account in an onboarding OU, and confirm that the organization trail and the GuardDuty detector are active in it.
BB. Enable all features in AWS Organizations, and then create a Security OU that holds the log archive and audit accounts.
CC. Move the account of each ended project into a Suspended OU whose SCP denies the creation of new resources.
DD. Designate the audit account as the delegated administrator for GuardDuty and Security Hub CSPM, with auto-enable turned on for new accounts.
EE. Move each workload account from the onboarding OU into its production OU once its baseline logging and detection are confirmed.
Show the answer and explanation
Correct order: B, D, A, E, C
B. Enable all features in AWS Organizations, and then create a Security OU that holds the log archive and audit accounts. First: all features must be enabled before SCPs and delegated administrators can be used, and the audit account must exist before anything can be delegated to it. The log archive account also exists before any workload.
D. Designate the audit account as the delegated administrator for GuardDuty and Security Hub CSPM, with auto-enable turned on for new accounts. Second: delegation needs all features and the audit account from the first step. Auto-enable must be on before workload accounts are created, so that detection starts in each of them without a manual step.
A. Create each new workload account in an onboarding OU, and confirm that the organization trail and the GuardDuty detector are active in it. Third: the account is created only after delegated administration and auto-enable are in place, so detection starts in it automatically. The onboarding OU holds it until the baseline is confirmed.
E. Move each workload account from the onboarding OU into its production OU once its baseline logging and detection are confirmed. Fourth: a workload joins its production OU only after its baseline is confirmed in the onboarding OU. Moving it earlier would put an unverified account into production.
C. Move the account of each ended project into a Suspended OU whose SCP denies the creation of new resources. Fifth: an account moves to the Suspended OU only when its project ends, after it has served as a workload. The SCP keeps the account in the organization without letting it run anything new.
Explanation
The organization needs all features and the security accounts first, then delegated administration with auto-enable so that detection starts in each new account. Workload accounts are created and checked in an onboarding OU, moved to production once the baseline is confirmed, and moved to a Suspended OU when their project ends. Each step depends on the one before it.
Want more on Organizations, Control Tower and delegated administrators? The 5 full-length practice sets have 5 more Organizations, Control Tower and delegated administrators questions, 325 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets →
Study Organizations, Control Tower and delegated administrators