SAP-C02 Practice Question: Design Solutions for Organizational Complexity
A company has a central IT team that manages AWS Organizations. The development team needs to create and manage their own AWS accounts for new projects. What is the BEST way to automate account creation while maintaining governance?
⚠ Common exam trap
Test-takers frequently confuse CloudFormation StackSets with account creation, but StackSets only operate on existing accounts, not create new ones.
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
✓
Create an AWS Service Catalog product that uses AWS Organizations APIs to create a new account, applies a baseline CloudFormation template, and moves the account to the correct OU.
It uses AWS Service Catalog to provide a self-service portal for the development team, while the central IT team retains governance by embedding AWS Organizations API calls to create accounts, apply a baseline CloudFormation template for security and compliance, and automatically move the account to the correct Organizational Unit (OU). This approach enforces guardrails without granting direct management account access.
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 AWS Service Catalog product that uses AWS Organizations APIs to create a new account, applies a baseline CloudFormation template, and moves the account to the correct OU.
Why this is correct
An AWS Service Catalog product wrapping AWS Organizations APIs creates accounts programmatically, applies a baseline CloudFormation template, and places each account in the correct OU. This gives the development team self-service while the central team retains governance through the portfolio.
- ✗
Use AWS CloudFormation StackSets to create accounts in bulk.
Why it's wrong here
CloudFormation StackSets deploy resources into existing accounts; they cannot create new accounts within AWS Organizations. It tempts because StackSets excel at bulk, consistent provisioning across many accounts, which fits rolling out baseline configuration after accounts already exist.
- ✗
Use the AWS Organizations console to manually create accounts and assign them to the appropriate OU.
Why it's wrong here
Manual console creation cannot be automated and gives the development team no self-service path, contradicting the automation requirement. It appeals because the console is the familiar starting point for a handful of accounts, which suits occasional, centrally controlled provisioning rather than repeatable delegated creation.
- ✗
Give the development team the credentials to the management account and let them create accounts directly.
Why it's wrong here
Handing out management account credentials grants unrestricted access to every account and the organisation itself, eliminating the governance boundary. It appeals because direct console access feels like the fastest route to account creation, which suits a single-operator sandbox rather than a governed multi-account organisation.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAP-C02 question from scratch — 984 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-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 SAP-C02 exam.