nerdexam
Amazon

DOP-C02 · Question #429

A company uses an organization in AWS Organizations to manage multiple AWS accounts. The company's internal auditors have administrative access to a single audit account within the organization. A…

The correct answer is B. Create an AWS CloudFormation stack set to deploy an IAM role that trusts the audit account and. To provide auditors with read-only access to all AWS accounts in an organization, including future ones, deploy a read-only IAM role that trusts the audit account using AWS CloudFormation Stack Sets.

Submitted by kevin_r· Mar 6, 2026Configuration Management and Infrastructure as Code

Question

A company uses an organization in AWS Organizations to manage multiple AWS accounts. The company's internal auditors have administrative access to a single audit account within the organization. A DevOps engineer needs to provide a solution to give the auditors read-only access to all accounts within the organization, including new accounts created in the future. Which solution will meet these requirements?

Options

  • AEnable AWS IAM Identity Center for the organization. Create a read-only access permission set.
  • BCreate an AWS CloudFormation stack set to deploy an IAM role that trusts the audit account and
  • CCreate an SCP that provides read-only access for users in the audit account. Apply the policy to
  • DEnable AWS Config in the organization management account. Create an AWS managed rule to

How the community answered

(22 responses)
  • A
    9% (2)
  • B
    55% (12)
  • C
    14% (3)
  • D
    23% (5)

Why each option

To provide auditors with read-only access to all AWS accounts in an organization, including future ones, deploy a read-only IAM role that trusts the audit account using AWS CloudFormation Stack Sets.

AEnable AWS IAM Identity Center for the organization. Create a read-only access permission set.

AWS IAM Identity Center manages centralized access for users and groups, but the problem implies auditors need to assume a role from an existing administrative AWS account, which is better handled by cross-account roles and Stack Sets for provisioning. Identity Center involves a different identity and access management flow.

BCreate an AWS CloudFormation stack set to deploy an IAM role that trusts the audit account andCorrect

AWS CloudFormation Stack Sets are designed to deploy AWS resources, such as IAM roles, consistently across multiple accounts and Organizational Units (OUs) within an AWS Organization. By defining an IAM role with read-only permissions and a trust policy that allows the dedicated audit account to assume it, Stack Sets ensure this role is present in all target accounts, including new ones added to the OU, enabling comprehensive read-only access with minimal management.

CCreate an SCP that provides read-only access for users in the audit account. Apply the policy to

Service Control Policies (SCPs) are guardrails that define maximum permissions and restrict actions within an organization; they do not grant explicit permissions. An IAM policy attached to a role is required to grant read-only access.

DEnable AWS Config in the organization management account. Create an AWS managed rule to

AWS Config monitors resource compliance and configuration, but it is not a tool for provisioning or granting access to resources across an organization.

Concept tested: Cross-account access provisioning in AWS Organizations

Source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-working-with-orgs.html

Topics

#AWS Organizations#IAM Cross-Account Access#CloudFormation StackSets#Multi-Account Deployment

Community Discussion

No community discussion yet for this question.

Full DOP-C02 Practice