Courseiva
Question 1,527 of 256
Configuration Management and IaChardMultiple ChoiceObjective-mapped

CloudFormation StackSets Self-Managed Permissions Error

A company uses AWS CloudFormation StackSets to deploy a VPC across multiple AWS accounts in AWS Organizations. The StackSet is created with self-managed permissions. The deployment fails in some accounts with the error: 'Insufficient IAM permissions to create resources'. What is the most likely cause of this failure?

Quick Answer

The answer is that the execution IAM role has not been created in the target accounts. When using CloudFormation StackSets with self-managed permissions, the administrator account does not automatically provision the required IAM roles in each target account; you must manually create an execution role in every target account that grants StackSets the necessary permissions to deploy resources. This is a critical distinction from service-managed permissions, where AWS Organizations handles role creation automatically. On the AWS Certified DevOps Engineer Professional DOP-C02 exam, this scenario tests your understanding of StackSets permission models and the common pitfall of assuming roles are pre-configured. A frequent trap is confusing the administrator role (used in the management account) with the execution role (needed in each target account). Memory tip: think “self-managed means you manage the roles yourself—no auto-provisioning in target accounts.”

⚠ Common exam trap

Many exam-takers confuse self-managed and service-managed permissions, assuming that StackSets automatically handle IAM roles in target accounts, when in fact self-managed requires manual role creation in each target account.

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

The execution IAM role is not created in the target accounts

With self-managed permissions in AWS CloudFormation StackSets, the administrator account does not automatically create the necessary IAM roles in target accounts. The execution IAM role must be manually created in each target account to grant StackSets the permissions required to create resources. The error 'Insufficient IAM permissions to create resources' directly indicates that this execution role is missing or lacks the required policies.

Answer analysis

Option-by-option breakdown

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

  • The StackSet does not support deploying to more than one account

    Why it's wrong here

    StackSets are designed for multi-account deployments.

  • The execution IAM role is not created in the target accounts

    Why this is correct

    Self-managed permissions require an execution role in each target account.

  • The administrator account does not have a service-linked role for StackSets

    Why it's wrong here

    Self-managed StackSets do not use service-linked roles.

  • The target accounts have reached their resource service quotas

    Why it's wrong here

    Service quota errors are different from IAM permission errors.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on DOP-C02

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company uses AWS CloudFormation to deploy a web application across multiple AWS accounts using StackSets. The DevOps team notices that stack instance updates are failing in some accounts with the error: 'Insufficient IAM permissions to perform the action'. The team has already verified that the StackSet IAM role has the necessary permissions. What is the most likely cause of this issue?

medium
  • A.The target accounts have reached the limit of 200 stacks per region.
  • B.The target accounts do not have the necessary trust policy to allow the StackSet IAM role to assume the execution role.
  • C.AWS Organizations has a service control policy (SCP) that denies the required action, but the StackSet IAM role has full admin permissions.
  • D.The StackSet name contains invalid characters that are not allowed in some accounts.

Why B: StackSets require a trust relationship between the StackSet IAM role (in the management account) and an execution role in each target account. Even if the StackSet IAM role has full permissions, the target accounts must have a trust policy that allows the StackSet IAM role to assume the execution role. Without this trust policy, the assumption fails, resulting in the 'Insufficient IAM permissions' error.

Last reviewed: Jun 24, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DOP-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 DOP-C02 exam.