Courseiva
Security and Compliance →hardMultiple Select

SOA-C02 Practice Question: Using AWS Organizations and wants to delegate administration of a specific member account…

A company is using AWS Organizations and wants to delegate administration of a specific member account to a user in the management account. Which TWO steps are required?

⚠ Common exam trap

Candidates often confuse service control policies (SCPs) with IAM policies, thinking SCPs can grant permissions to delegate administration, when in fact SCPs only filter permissions and cannot grant access; the correct mechanism is always an IAM role with a trust policy.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Grant the user in the management account permissions to assume the role in the member account.

To delegate administration of a member account to a user in the management account, you must create an IAM role in the member account with a trust policy that allows the management account (or a specific user/role in it) to assume that role. Then, the user in the management account must be granted permissions (e.g., via an IAM policy) to call sts:AssumeRole on that role. This cross-account access pattern is the standard AWS mechanism for delegating administrative access without sharing long-term credentials.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Create an IAM user in the member account with the same name as the management account user.

    Why it's wrong here

    This approach creates a separate IAM user with its own long-term credentials, which must be independently managed through password rotation and MFA. That duplicate user becomes a distinct security principal, so it does not inherit the management account user's policies or permissions, and it introduces a standing credential that increases the risk of compromise. AWS recommends cross-account roles instead of duplicating users, because roles provide temporary, scoped credentials without creating additional long-lived identities that need separate lifecycle management.

  • ✓

    Grant the user in the management account permissions to assume the role in the member account.

    Why this is correct

    To delegate access, an IAM policy must be attached to the management account user that explicitly allows the sts:AssumeRole action against the member account role's Amazon Resource Name (ARN). When the user assumes the role, AWS STS returns temporary security credentials that are automatically scoped to the role's permissions policy. This permission is the identity-based side of the trust relationship, and it is necessary because a trust policy alone cannot grant the user the right to call the role.

  • ✗

    Enable AWS Single Sign-On (SSO) for the member account.

    Why it's wrong here

    AWS Single Sign-On (now IAM Identity Center) is a service for federating users and centrally assigning permission sets across multiple accounts, but it does not work automatically just by enabling it in a member account. Enabling SSO does not create an IAM role that the management account user can assume, nor does it alter the existing IAM trust relationships. For this scenario, a simple cross-account IAM role is the minimal, direct solution; SSO would require additional configuration of applications, permission sets, and user assignments, making it an overcomplicated and unnecessary alternative.

  • ✗

    Create a service control policy (SCP) that allows the member account to be administered.

    Why it's wrong here

    Service control policies (SCPs) are a feature of AWS Organizations that impose guardrails by restricting the maximum permissions that principals in an account can have—they can never grant a permission that an IAM policy does not already allow. An SCP that 'allows' administration merely means it does not block the action, but the user still lacks the necessary identity-based permission and the target role does not exist. Therefore, this option incorrectly assumes SCPs can act as a mechanism for delegation, when in fact they are exclusively a preventative control that applies to all principals in affected accounts.

  • ✓

    Create an IAM role in the member account with a trust policy that allows the management account to assume it.

    Why this is correct

    Creating a role in the member account with a trust policy that names the management account (or a specific principal within it) as a trusted entity is the correct cross-account delegation mechanism. The trust policy authenticates the requester's account and allows the principal to assume the role, while the role's permission policy determines the authorized actions. This is the foundational step, and it must be paired with a corresponding sts:AssumeRole permission on the user side; together they form a complete trust relationship for secure, temporary access.

About these practice questions

One of 1,169 original SOA-C02 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar SOA-C02 questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

This SOA-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SOA-C02 exam.