Easy ReviewDOP-C02
Configuration Management and IaC37

Organizations

Organize AWS accounts, share eligible billing discounts, and control access with policies and service delegation.

Organizations manages account membership and policy inheritance. These sections separate billing, identity limits, resource limits, and service administration so each control has a clear purpose.

Organizations basics

AWS Organizations manages a group of AWS accounts as one organization, with shared billing and central policies.

How it works

  1. A management accountThe account that manages the organization and pays its member-account charges. creates the organization and creates or invites member accountsAn account belonging to an organization other than its management account..
  2. Accounts are grouped into organizational unitsA container grouping AWS accounts or other OUs for common management and policies..
  3. Policies apply to groups of accounts, and all usage lands on one consolidated bill.

Exam cues

  • If the question says many accounts with one bill or central rules, think AWS Organizations.

Remember

  • One consolidated bill for all accounts.
  • Accounts stay separate, grouped in organizational units.

Trap: Organizations does not merge accounts. Each keeps its own resources and isolation; only billing and governance are central.

From the AWS docs (5)
  • AWS Organizations centrally manages many AWS accounts: create accounts, group them, apply governance policies and pay with a single payment method.
  • Organizations gives one consolidated bill for all member accounts, and usage across accounts can be viewed in Cost Explorer.
  • The management account manages the organization and pays its member-account charges.
  • An SCP limits the available permissions of principals in member accounts and never grants access.
  • SCPs require the organization all-features mode and the SCP policy type enabled.

Accounts, OUs, and consolidated billing

AWS Organizations groups accounts for central management and billing. An organizational unitA container grouping AWS accounts or other OUs for common management and policies. (OU) is a folder for accounts or other OUs; policies inherited through that folder hierarchy apply to its accounts.

How it works

  1. Start with the organization rootThe top-level container for an organization account and OU hierarchy., the top folder, and a management accountThe account that manages the organization and pays its member-account charges., which manages the organization and pays member charges. Each account has one parent and belongs to one organization. The organization root is different from an account’s root userThe account-owner identity with access governed by AWS account and organization controls., its account-owner identityThe user, role, or service making an AWS request..
  2. Group accounts into OUs and attach applicable policies at the root, OU, or account level. Nested OUs inherit their parents’ policies.
  3. Create a new account or invite an existing one. Created accounts receive OrganizationAccountAccessRole by default; invited accounts do not. Cross-account access needs an access role and caller permission to assume it.
  4. Choose the feature set. All features is the default and includes billing.
  5. Combine usage for eligible discounts. The management account controls Reserved InstanceAn AWS purchase whose eligible usage discount may be shared within an organization. and Savings Plans sharing; both the purchasing and receiving accounts must have sharing enabled. Consolidated billing has no added fee and produces one bill per Seller of RecordThe AWS entity responsible for issuing the applicable customer bill., the AWS entity issuing the bill.

When an account leaves, review roles that trust the former management account. They are not automatically deleted.

For activity alerts, configure a CloudTrail trailA CloudTrail configuration that records selected activity for an account or organization. and an EventBridge rule in us-east-1, with SNS as a notification target.

Exam cues

  • If the question says an invited account lacks the administrative access role, think create the role explicitly, because invitation does not create it.
  • If the question says discounts are not shared, think both accounts’ sharing settings, because one enabled side is insufficient.

Remember

  • All features is the default.
  • Billing combines charges and discounts, without granting resource access.
  • Organization activity monitoring uses us-east-1.

Trap: Moving an account does not automatically delete a role that trusts its former management account.

Policy inheritance follows the account path
12Organization roottop of policy pathWorkload OUinherited policiesMember accountaccount policies
  1. Root authorization policies apply down the organization hierarchy to member accounts.

  2. The member account inherits applicable OU policies in addition to policies attached directly to it.

From the AWS docs (19)
  • An organization groups AWS accounts under one root, with organizational units that can contain accounts and other OUs.
  • An account belongs to only one organization and has one parent in that organization hierarchy.
  • Accounts inherit applicable organization policies from their parent OUs and root.
  • The management account manages the organization and pays its member-account charges.
  • Consolidated billing combines payment but does not give the management account access to other accounts resources.
  • Combined usage can qualify for volume pricing, Reserved Instance discounts, and Savings Plans discounts.
  • Discount sharing requires both the purchasing account and the benefit-receiving account to have sharing enabled.
  • The management account controls discount sharing preferences for organization accounts.
  • Consolidated billing produces one bill per Seller of Record and has no additional fee.
  • All features is the default feature set and includes consolidated billing and advanced organization management.
  • Accounts created in Organizations receive OrganizationAccountAccessRole by default.
  • Invited accounts do not automatically receive OrganizationAccountAccessRole; it can be created manually.
  • Using OrganizationAccountAccessRole requires the management-account caller to have permission to assume it.
  • Access roles trusting the old management account are not automatically removed when an account leaves.
  • Account migration preparation includes checking organization-dependent policies and deregistering delegated administrator permissions.
  • Organizations EventBridge monitoring is configured in US East (N. Virginia), us-east-1.
  • A CloudTrail trail and EventBridge rule can monitor Organizations API actions and route notifications to SNS.
  • The AWS account root user is the account identity created with access to all its services and resources, subject to applicable controls.
  • AWS Organizations tag policies standardize the tags on resources across the organization's accounts, including the case of tag keys and values.

Service control policies

A service control policy (SCP) is an organization-wide permissions limit for member-account identities. A principalThe user, role, or service making an AWS request. is the identity making a request, such as a user or role. Passing SCP evaluation only leaves an action eligible; access still needs the appropriate IAM or resource policyA permissions policy attached to a resource that governs who may access it..

How it works

  1. Enable all features and the SCP policy type. Attach policies to the rootThe top-level container for an organization account and OU hierarchy., OUs, or accounts.
  2. Follow the account’s path from the root. An action needs an Allow at every level, including the account. Any applicable explicit Deny wins.
  3. Choose a policy strategy. A deny listA policy strategy retaining broad eligibility while explicitly prohibiting selected actions. retains FullAWSAccess or another suitable allow policy and adds restrictions. An allow listA policy strategy explicitly permitting selected actions while excluding unlisted actions. replaces broad allows with selected actions. A child cannot restore what an ancestor excludes.
  4. Evaluate permissions inside that ceiling. Even AdministratorAccess cannot override an SCP restriction. Member-account root usersThe account-owner identity with access governed by AWS account and organization controls. and delegated administratorsA member account registered to administer a specific integrated service for the organization. remain subject to SCPs, apart from documented exceptions.
  5. Test restrictions on a limited set of accounts before widening their attachment.

For Config protection, denyA policy statement that blocks matching requests even when another applicable policy allows them. selected baseline changes: config:DeleteConfigurationRecorder, config:DeleteDeliveryChannel, config:PutConfigurationRecorder, config:PutDeliveryChannel, and config:StopConfigurationRecorder. A recorderThe Config component that captures resource configuration information. captures resource configurations; a delivery channelThe Config settings that direct recorded configuration data to its destinations. sends them to configured destinations. Conditions can preserve required administrative exceptions. Unrelated Config actions remain subject to their existing permissions.

Exam cues

  • If the question says an IAM administrator is denied by an SCP, think the entire policy path, because IAM cannot override the ceiling.
  • If the question says a deny-only SCP replaces FullAWSAccess, think missing Allow, because a Deny statement does not supply the required Allow.
  • If the question says protect baseline Config without blocking all administration, think selected action denies, because SCPs can restrict specific operations.

Remember

  • SCPs grant no permissions.
  • The management accountThe account that manages the organization and pays its member-account charges. and service-linked roles are exempt.
  • Member-account root users are restricted, with documented exceptions such as Enterprise Support enrollment and CloudFront trusted-signer functions.
  • An SCP does not restrict external principals simply because they access a resource in your member accountAn account belonging to an organization other than its management account..

Trap: A delegated administrator is still a member account. Delegation does not exempt it from SCPs.

Every level must permit the action
12Root SCPAllow requiredOU SCPAllow requiredAccount SCPAllow required
  1. The root and every parent OU must allow the action. An applicable explicit Deny blocks it.

  2. The account must also allow the action through its SCPs; IAM still needs to grant access.

From the AWS docs (17)
  • An action needs an SCP Allow at every level from the root through each OU to the target account.
  • An explicit SCP Deny at any point on the account path overrides allows at other levels.
  • Organizations attaches FullAWSAccess to the root, OUs, and accounts by default to allow actions through SCP evaluation.
  • Removing FullAWSAccess without another Allow at that level blocks actions for affected member principals.
  • A deny-list SCP strategy retains FullAWSAccess or another Allow policy and adds Deny restrictions.
  • An allow-list SCP strategy replaces broad allows with selected actions; lower levels cannot broaden an ancestor ceiling.
  • AdministratorAccess cannot override a missing SCP Allow or an explicit SCP Deny.
  • SCPs restrict member-account root users subject to the documented root-task exceptions.
  • SCPs do not restrict the management account, but delegated administrator member accounts remain subject to them.
  • SCPs do not restrict service-linked roles.
  • SCP exceptions include root-user Enterprise Support enrollment and CloudFront trusted-signer functionality.
  • SCPs on a resource-owning member account do not restrict principals in accounts outside that organization.
  • An SCP can deny config:DeleteConfigurationRecorder, config:DeleteDeliveryChannel, config:PutConfigurationRecorder, config:PutDeliveryChannel, and config:StopConfigurationRecorder.
  • SCP statements can deny selected actions with conditions, leaving other actions subject to their existing permissions.
  • AWS recommends testing SCP impact on a limited set of accounts before broad attachment at the root.
  • A principal is an identity that can make AWS requests, such as a user, role, or service.
  • A Config recorder captures resource configurations, and its delivery channel selects destinations for recorded data.

Resource control policies

A resource control policy (RCP) limits access to supported resources in member accountsAn account belonging to an organization other than its management account., including requests from outside the organization. Think of it as a ceiling attached to the resource owner’s account hierarchy.

How it works

  1. Enable all features and RCPs. Confirm that the resource’s service supports RCPs; documented examples include S3, KMS, STS, SQS, and Secrets Manager.
  2. RCPFullAWSAccess permits requests through RCP evaluation but grants no resource access.
  3. Attach RCPs where restrictions belong. A Deny anywhere on the resource account’s path wins over a resource policyA permissions policy attached to a resource that governs who may access it. Allow.
  4. Evaluate actual access with the relevant IAM and resource policies. A resource policy is a policy attached to a resource, such as an S3 bucket. It can grant access only within applicable organization limits.
  5. Test on a small scope before broader use. Management-account resources and calls made through service-linked roles are exempt; delegated administratorA member account registered to administer a specific integrated service for the organization. member-account resources remain covered.
Control What it limits Grants access?
SCP Member-account principalsThe user, role, or service making an AWS request. No
RCP Supported member-account resources, including outside access No
Resource policy Access to its attached resource Can grant access within applicable limits

Exam cues

  • If the question says outside principals must be blocked from member-account S3 data, think RCP or bucket policy, because the bucket owner’s SCP does not constrain those outside identities.
  • If the question says a bucket policy Allow conflicts with an RCP DenyA policy statement that blocks matching requests even when another applicable policy allows them., think denied, because the resource grant cannot override the ceiling.

Remember

  • RCPFullAWSAccess does not grant resource access.
  • Principal supports only *, and NotPrincipal is unsupported.
  • RCP coverage is service-specific; enabling RCPs does not restrict every AWS resource type.

Trap: An RCP passing a request does not grant it access. The required IAM or resource policy permissions must still exist.

External requests still meet resource limits
Member account12External calleroutside organizationRCP evaluationapplicable Deny winsS3 bucketresource permissions
  1. The requester is outside the organization, but the resource is in a member account.

  2. Access must pass the applicable RCP ceiling and the policies that grant access; an RCP Deny blocks it.

From the AWS docs (12)
  • An RCP limits available permissions on supported resources in organization member accounts without granting access.
  • An RCP on a member-account resource applies even when the requester belongs to an external account.
  • SCPs constrain member-account principals, so a resource owner SCP does not restrict an external-account requester.
  • RCPs require all-features mode and the RCP policy type enabled.
  • RCP-supported services include S3, KMS, STS, SQS, and Secrets Manager; coverage is service-specific.
  • RCPs can attach at the root, OU, or account and follow the resource-owning account hierarchy.
  • Resources in the management account are exempt from RCPs; resources in delegated administrator member accounts are not.
  • RCPs do not restrict calls made using service-linked roles.
  • RCPFullAWSAccess permits requests through RCP evaluation without granting resource access.
  • A Deny in any applicable RCP on the resource account path overrides a resource policy Allow.
  • RCP Principal supports only the wildcard *; NotPrincipal is unsupported.
  • AWS recommends testing RCP restrictions on individual accounts before applying them more broadly.

Trusted access and delegated administration

Trusted accessPermission for a supported AWS service to perform work across organization accounts. lets an AWS service work across organization accounts. Delegated administration lets a chosen member accountAn account belonging to an organization other than its management account. manage that service for the organization, reducing routine use of the management accountThe account that manages the organization and pays its member-account charges..

How it works

  1. Check the service’s Organizations integration. Trusted access and delegated administration are separate capabilities; support for one does not guarantee the other.
  2. Enable trusted access through the service’s own tools when available. This performs its initialization. The service can create service-linked roles, roles reserved for that service, in member accounts when needed.
  3. Register a supported member account as the service’s delegated administratorA member account registered to administer a specific integrated service for the organization.. It receives service-specific permissions plus read-only Organizations permissions, not general rights to change the organization hierarchy.
  4. Keep workloads in member accounts and use the management account for tasks that require it. Delegated administrator accounts remain subject to SCPs.
  5. Disable integrations through the service when possible so cleanup can run. Turning off the Organizations switch does not guarantee deletion of historical configuration or data.
Integration Service-specific delegation Purpose
StackSets Yes Deploy infrastructure across organization accounts
Config Yes Manage organization configuration and compliance
CloudTrail Yes Manage organization trailsA CloudTrail configuration that records selected activity for an account or organization.
GuardDuty, Security Hub CSPM, Backup Yes Manage the respective service across accounts
RAM No Share supported resources with accounts and OUs
Control Tower, Directory Service No Use their supported trusted-access integrations

Other documented delegation examples include Detective, Inspector, Macie, Firewall Manager, IAM Access Analyzer, Systems Manager, IAM Identity Center, and Service Catalog.

Enable RAM sharing from RAM itself so its service-linked roleAn IAM role linked to an AWS service so that the service can act on your behalf. is created. Normal organization shares avoid invitation exchanges, but consuming administrators must still grant their principalsThe user, role, or service making an AWS request. IAM access.

An organization trail covers the management and member accounts, automatically adds new members, and cannot be changed by ordinary member-account users. Service-managed StackSets create deployment roles and can automatically deploy stacksA collection of AWS resources deployed and managed together by CloudFormation., collections of CloudFormation-managed resources, to new accounts entering a target OUA container grouping AWS accounts or other OUs for common management and policies.. They skip the management account.

Exam cues

  • If the question says manage a supported security service from a member account, think trusted access plus delegated administration, because delegation is service-specific.
  • If the question says RAM sharing fails after only enabling Organizations trusted access, think enable sharing through RAM, because that setup creates the required role.
  • If the question says deploy a baseline whenever accounts enter an OU, think automatic service-managed StackSets, because they track the target’s account membership.
  • If the question says members must not disable central audit logging, think organization trail, because ordinary members cannot modify it.

Remember

  • Delegated service administration includes read-only Organizations access.
  • Trusted services create service-linked roles when needed.
  • RAM, Control Tower, and Directory Service have trusted access without service-specific delegated administration through this integration.

Trap: Enabling trusted access is not the same as completing a service’s initialization. RAM explicitly requires its own sharing setup.

Delegate service administration to a member
12Organizationsenable service trustDelegated adminmember accountGuardDutyorganization management
  1. After trusted access is enabled, register a supported member account for service-specific administration.

  2. That account manages the service for organization accounts while remaining subject to member-account SCPs.

From the AWS docs (21)
  • Trusted access lets a supported AWS service perform organization-wide tasks on behalf of the organization.
  • A trusted service creates service-linked roles in member accounts when needed, not necessarily in every account immediately.
  • AWS recommends enabling and disabling trusted access through the integrated service tools when available so initialization and cleanup occur.
  • A delegated administrator is a member account registered to administer a particular supported AWS service for the organization.
  • Before registering a delegated administrator, confirm service support and enable trusted access for that service.
  • Service delegation grants service-specific administrative permissions and read-only Organizations permissions; it does not grant general organization mutation rights.
  • AWS recommends keeping workloads in member accounts and reserving management-account use for tasks that require it.
  • StackSets, Config, CloudTrail, GuardDuty, Security Hub CSPM, and Backup support service-specific delegated administrators.
  • Detective, Inspector, Macie, Firewall Manager, IAM Access Analyzer, Systems Manager, IAM Identity Center, and Service Catalog support delegated administration.
  • RAM, Control Tower, and Directory Service support trusted access but not a service-specific delegated administrator through the Organizations integration.
  • Delegated administrator member accounts remain subject to SCPs.
  • RAM organization sharing must be enabled through RAM to create AWSServiceRoleForResourceAccessManager; enabling trusted access only through Organizations does not create it.
  • After normal organization sharing is enabled, RAM shares to accounts, OUs, or the organization do not require resource-share invitations.
  • Administrators in consuming accounts must grant their principals IAM access to resources shared through RAM.
  • A management account or CloudTrail delegated administrator can create an organization trail covering management and member accounts.
  • Ordinary member-account users cannot modify, delete, or stop organization trails.
  • New organization members are automatically added to an organization trail for logging.
  • Service-managed StackSets use trusted access and create deployment IAM roles on behalf of the user.
  • Service-managed StackSets target organization accounts or OUs and do not deploy to the management account.
  • StackSet automatic deployments can deploy to new accounts added to a targeted organization or OU.
  • Disabling trusted access through Organizations does not guarantee removal of historical service data or configuration.

Account migrations and policy controls

AWS Organizations feature settings, account transfers, and policies affect how accounts are managed. The feature set determines whether authorization policies are available, while policy conditions can restrict requests across member accountsAn account belonging to an organization other than its management account..

How it works

  1. To use authorization policies in a billing-only organization, enable all features. In the standard migration, invited members approve; accounts created in Organizations do not. Each member needs AWSServiceRoleForOrganizations; a missing role can require a recreation invitation.
  2. To move an account, accept an invitation from the destination management accountThe account that manages the organization and pays its member-account charges.. A source SCP denying organizations:LeaveOrganization blocks the direct transfer. To remove an account to become standalone, it needs a support plan, verified contact information, and a current payment method.
  3. AWS Config can record Organizations account, organization, OUA container grouping AWS accounts or other OUs for common management and policies., policy, and resource policyA permissions policy attached to a resource that governs who may access it. resource types.
  4. When RCPs are enabled, RCPFullAWSAccess is attached to the rootThe top-level container for an organization account and OU hierarchy., each OU, and each account. It cannot be detached. Custom RCPs use Deny; Allow is reserved for the managed policy.
  5. In an RCP, aws:PrincipalOrgID identifies the requesting principalThe user, role, or service making an AWS request.’s organization. Account for AWS service principalsThe identity an AWS service uses when it makes a request directly. with an aws:PrincipalIsAWSService exception; aws:SourceOrgID can restrict service requests to those originating from resources in a trusted organization.
  6. A Region-deny SCP can use aws:RequestedRegion with NotAction exceptions for global services. The condition checks the endpointThe service address and Region that an API request calls. called, not every cross-Region effect. An SCP can also denyA policy statement that blocks matching requests even when another applicable policy allows them. requests signed with EC2 role credentials when ec2:RoleDelivery is below 2.0, requiring IMDSv2 credentials across member accounts.

Exam cues

  • If the question says billing-only mode needs SCPs, think all-features migration, because billing-only mode does not support authorization policies.
  • If the question says an account transfer is blocked, think organizations:LeaveOrganization, because a source SCP can deny that action.
  • If the question says an organization-only RCP breaks service delivery, think a service-principal exception, because the restriction must account for AWS service principals.
  • If the question says a Region deny breaks IAM, think NotAction exceptions, because global service endpoints can be outside the permitted workload Regions.
  • If the question says block requests using IMDSv1 role credentials across member accounts, think an SCP denying ec2:RoleDelivery below 2.0, because that requires IMDSv2 credentials.

Remember

  • All-features migration is one-way.
  • Direct transfers have been available since November 2025 without an intermediate standalone phase.
  • RCPFullAWSAccess cannot be detached; custom RCPs use Deny.

Trap: A direct account transfer does not require the account to become standalone first, but a source SCP denying organizations:LeaveOrganization can still block it.

From the AWS docs (18)
  • Consolidated-billing-only mode does not support authorization policies or trusted service integrations.
  • In the standard migration to all features, every invited member must approve; accounts created in Organizations do not need migration approval.
  • All-features mode requires AWSServiceRoleForOrganizations in every member account; a missing role can require a recreation invitation.
  • Once all features is enabled, the organization cannot return to consolidated-billing-only mode.
  • An existing account can move directly between organizations by accepting an invitation from the destination management account.
  • Direct account transfers without an intermediate standalone phase were introduced in November 2025.
  • Direct transfer requires organizations:LeaveOrganization, and a source SCP denying that action blocks the transfer.
  • AWS Config supports recording AWS::Organizations::Account, Organization, OrganizationalUnit, Policy, and ResourcePolicy resource types.
  • To remove a member account from an organization, the account needs the information to stand alone: a support plan, verified contact information and a current payment method.
  • Enabling RCPs attaches RCPFullAWSAccess to the root, every OU, and every account; it cannot be detached.
  • Custom RCPs use Deny; Allow is reserved for the managed RCPFullAWSAccess policy.
  • aws:PrincipalOrgID identifies the requesting principal organization and avoids enumerating its accounts.
  • An RCP using principal-organization restrictions must account for AWS service principals, for example with aws:PrincipalIsAWSService exceptions.
  • aws:SourceOrgID can restrict service-principal access to requests originating from resources in a trusted organization.
  • A Region-deny SCP can use aws:RequestedRegion with NotAction exceptions for global services such as IAM.
  • Some global services use endpoints outside permitted workload Regions, so a Region deny needs appropriate service exceptions.
  • aws:RequestedRegion controls the endpoint called, not all cross-Region effects of that operation.
  • A policy can deny requests signed with EC2 role credentials when ec2:RoleDelivery is below 2.0, which forces credentials to come from IMDSv2; in an SCP this applies across member accounts.

Flashcards

tap to flip
Answer

·

All 37 cards as a list

A company with 30 AWS accounts wants one bill and central policies for all of them. Which service fits?

AWS Organizations, which gives consolidated billing and governance policies across accounts.

What billing feature does AWS Organizations provide?

Consolidated billing: one bill and one payment method for all member accounts.

Does AWS Organizations merge many accounts into one account?

No. Each account stays separate; Organizations groups and governs them and combines their bills.

A company wants to combine charges from multiple AWS accounts. How does AWS Organizations handle billing?

The management account pays member account charges through consolidated billing.

What does an AWS Organizations service control policy grant?

Nothing. An SCP sets the permission ceiling for member-account principals. IAM or resource policies must supply access within that ceiling, and SCPs require all-features mode.

Does AWS Organizations consolidated billing grant access to another member account resources?

No. It combines charges and eligible discounts. Cross-account administration still requires an access role and permission to assume it.

How does AWS Organizations organize accounts and apply inherited policies?

Accounts sit under the organization root or an OU. OUs can be nested, and applicable policies follow the parent path to each account.

A team invites an existing account to AWS Organizations but cannot find OrganizationAccountAccessRole. Why?

Organizations creates that role by default for newly created accounts, not invited accounts. Create it manually if needed, and authorize callers to assume it.

An account leaves AWS Organizations, but a role still trusts its old management account. Is that role removed automatically?

No. Remove or change the old access role deliberately; leaving the organization does not automatically delete it.

How can an AWS Organizations administrator receive an alert when an OU is created or an account attempts to leave?

Configure a CloudTrail trail and EventBridge rule in us-east-1, with SNS as a notification target.

Cost allocation reports break because teams tag resources as CostCenter, costcenter and cost-center. Which AWS Organizations feature enforces one standard?

Tag policies.

How are SCP permissions evaluated through nested AWS Organizations OUs?

The action needs an Allow at every level from root through the OUs to the account. An explicit Deny anywhere on that path wins.

An AWS Organizations administrator removes FullAWSAccess from the root and leaves only a deny-only SCP there. What happens?

Affected member principals lose the Allow at the root, blocking their actions. Keep FullAWSAccess for a deny-list strategy or replace it with suitable explicit allows.

A member-account administrator has AdministratorAccess but an operation is blocked by an AWS Organizations SCP. Can IAM override it?

No. The SCP ceiling still applies. Inspect every level on the account path for a missing Allow or explicit Deny.

Can an SCP restrict the root user, users, or roles in the AWS Organizations management account?

No. The management account is outside SCP restrictions. Delegated administrator member accounts remain restricted.

Which AWS Organizations principals and tasks are exempt from SCP restrictions?

The management account and service-linked roles are exempt. Some root-only tasks, including Enterprise Support enrollment and CloudFront trusted-signer functionality, are also exceptions. Member root users are otherwise restricted.

An AWS Organizations team must preserve baseline Config recording while leaving unrelated Config administration available. What SCP approach fits?

Deny the recorder/channel modification, deletion, and stop actions that must be protected, with any required administrative exceptions. Avoid denying all Config actions.

An AWS Organizations OU allow-list excludes an action, but the account-level SCP allows it. Is that sufficient?

No. A lower-level allow cannot broaden an ancestor ceiling. The action needs an Allow at every level and no applicable explicit Deny.

An S3 bucket in an AWS Organizations member account grants access to an external account. Does the bucket-owner SCP restrict that requester?

No. It limits member-account principals. Use an applicable RCP or a restrictive bucket policy to control external access to that bucket.

How do RCPs and SCPs differ in AWS Organizations?

RCPs limit supported member-account resources, including access by outside requesters. SCPs limit member-account principals. Neither grants access; management-account resources and service-linked-role calls are outside RCP restrictions.

An AWS Organizations team must centrally block outside principals from member-account resources. Can it rely on an SCP alone?

No. Use RCP restrictions for supported resources, alongside the policies that grant access. An SCP does not limit an external principal merely because the resource is in your organization.

An AWS Organizations RCP denies S3 reads, but the bucket policy grants them. Which policy wins?

The applicable RCP Deny wins. Resource-policy access must fit within the RCP ceiling.

A team must administer a supported service across AWS Organizations without routinely using the management account. What should it configure?

Enable trusted access and register a service-specific delegated administrator member account. Use the service tools for setup when available.

Do all AWS Organizations services with trusted access support delegated administrators?

No. StackSets, Config, CloudTrail, and GuardDuty support delegation, while RAM, Control Tower, and Directory Service do not support service-specific delegated administration through this integration.

An AWS Organizations administrator enables RAM trusted access only in Organizations, but organization sharing fails. What setup is missing?

Enable organization sharing through RAM so AWSServiceRoleForResourceAccessManager is created. The Organizations switch alone does not create that role.

A team needs a CloudTrail trail for current and future AWS Organizations member accounts that members cannot disable. What fits?

Create an organization trail from the management account or a CloudTrail delegated administrator. New members are added automatically, and ordinary member users cannot modify or stop it.

An AWS Organizations team must deploy a common CloudFormation baseline to accounts entering a workload OU. What integration fits?

Use a service-managed StackSet with trusted access and automatic deployments to that OU. CloudFormation creates the deployment roles and skips the management account.

Does registering an AWS service delegated administrator let that account change the entire AWS Organizations structure?

No. Service-specific delegation grants that service administration plus read-only Organizations permissions. It does not itself grant organization mutation rights, and SCPs still apply to the member account.

Does disabling an AWS Organizations trusted-access switch guarantee the service deletes its historical configuration?

No. Cleanup depends on the service. Use its own tools to disable integration when available and check its documented cleanup behavior.

A consolidated-billing-only AWS organization needs SCPs. What migration must it complete?

Enable all features. In the standard migration, invited accounts must approve. Created accounts do not need approval, but missing AWSServiceRoleForOrganizations roles must be restored. The completed migration is one-way.

Must an AWS member account become standalone before joining another organization?

No. Since November 2025, direct transfer uses a destination invitation and acceptance. The moving account still needs organizations:LeaveOrganization, and a source SCP can block it.

Can AWS Config record the structure and policies of AWS Organizations?

Yes. Supported resource types include AWS::Organizations::Account, Organization, OrganizationalUnit, Policy, and ResourcePolicy.

What must a member account of an AWS organization have before it can be removed to become a standalone account?

A support plan, verified contact information and a current payment method.

Can an AWS Organizations administrator detach RCPFullAWSAccess to build an RCP allow list?

No. The managed policy cannot be detached. Custom RCPs use Deny; only the managed RCPFullAWSAccess policy supports Allow.

An AWS Organizations team applies an RCP using aws:PrincipalOrgID and breaks CloudTrail log delivery. What exception may be missing?

Account for AWS service principals with an aws:PrincipalIsAWSService condition. A service principal is not an IAM principal belonging to your organization; aws:SourceOrgID can constrain the service request origin.

An AWS Organizations Region-deny SCP breaks IAM calls. How should the policy be corrected?

Use appropriate NotAction exceptions for required global services. aws:RequestedRegion evaluates the endpoint Region; global endpoints may sit outside permitted workload Regions.

An organization must block use of instance role credentials obtained through IMDSv1 in every account. What fits?

An SCP that denies requests when ec2:RoleDelivery is below 2.0, so only IMDSv2 credentials work.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!