CLF-C02 Security and Compliance Practice Question
A company uses AWS Organizations to centrally manage multiple AWS accounts. The security team requires that no IAM users can be created in any member account. All access must use federated identities from the company's existing identity provider. The security team needs a single, centralized mechanism to enforce this restriction across all existing and future member accounts. Which AWS feature should the security team use to meet this requirement?
⚠ Common exam trap
Many candidates confuse SCPs with IAM policies, thinking IAM policies can centrally control all accounts, but SCPs are the only mechanism that can enforce restrictions across an entire AWS Organization, including preventing the creation of IAM users.
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
✓
AWS Organizations service control policies (SCPs)
AWS Organizations service control policies (SCPs) allow a central administrator to define maximum permissions for all accounts within an organization. By creating an SCP that explicitly denies the `iam:CreateUser` action, the security team can enforce that no IAM users can be created in any member account, including future accounts, because SCPs are inherited by all accounts in the organization. This provides a single, centralized mechanism that cannot be overridden by account-level IAM 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.
- ✗
AWS Identity and Access Management (IAM) policies
Why it's wrong here
IAM policies are attached to IAM users, groups, or roles within a single account. They cannot enforce restrictions across multiple accounts or prevent the root user from creating IAM users. They also do not apply automatically to new accounts added to the organization.
When this WOULD be correct
An IAM policy would be correct if the requirement was to restrict permissions for a specific federated user or role within a single account, such as denying access to a particular S3 bucket for a role assumed by federated users.
- ✓
AWS Organizations service control policies (SCPs)
Why this is correct
SCPs are a centralized policy mechanism within AWS Organizations that can deny the IAM:CreateUser action across all member accounts in an organization, OU, or specific account. SCPs apply to all principals, including the root user, and affect both existing and future accounts, making them the correct choice for enforcing this restriction.
- ✗
AWS Config managed rules with automatic remediation
Why it's wrong here
AWS Config rules can detect when an IAM user is created (non-compliant) and trigger automatic remediation actions, but they cannot prevent the creation in the first place. This is a detective and reactive solution, not a preventive one, and it requires per-account configuration.
When this WOULD be correct
A company needs to detect and automatically remediate non-compliant IAM user creation in existing accounts after the fact, and does not require a preventive control that applies to future accounts. AWS Config rules with auto-remediation would be correct for this detective and reactive compliance requirement.
- ✗
IAM Access Analyzer
Why it's wrong here
IAM Access Analyzer is used to analyze resource-based policies (e.g., S3 bucket policies, IAM roles) to identify resources shared with external principals. It does not have the ability to enforce restrictions on the creation of IAM users.
When this WOULD be correct
A company wants to identify unintended cross-account access to resources like S3 buckets or IAM roles. IAM Access Analyzer would be the correct choice to generate findings about external access.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The CLF-C02 exam frequently reuses these exact scenarios with slightly different constraints.
✓AWS Organizations service control policies (SCPs)Correct answer▾
Why this is correct
SCPs are a centralized policy mechanism within AWS Organizations that can deny the IAM:CreateUser action across all member accounts in an organization, OU, or specific account. SCPs apply to all principals, including the root user, and affect both existing and future accounts, making them the correct choice for enforcing this restriction.
✗AWS Identity and Access Management (IAM) policiesWrong answer — click to see why▾
Why this is wrong here
IAM policies are attached to IAM users, groups, or roles and can only restrict permissions within a single account. They cannot be applied centrally across all accounts in an AWS Organization, nor can they prevent the creation of IAM users in member accounts.
★ When this WOULD be the correct answer
An IAM policy would be correct if the requirement was to restrict permissions for a specific federated user or role within a single account, such as denying access to a particular S3 bucket for a role assumed by federated users.
Why candidates choose this
Candidates may think IAM policies can enforce restrictions across accounts because they are familiar with IAM for access control, but they overlook that IAM policies are account-specific and cannot be applied organization-wide like SCPs.
✗AWS Config managed rules with automatic remediationWrong answer — click to see why▾
Why this is wrong here
AWS Config managed rules with automatic remediation can detect and remediate non-compliant resources, but they cannot proactively prevent IAM user creation across all accounts. They operate reactively and require per-account setup, not a single centralized mechanism like SCPs.
★ When this WOULD be the correct answer
A company needs to detect and automatically remediate non-compliant IAM user creation in existing accounts after the fact, and does not require a preventive control that applies to future accounts. AWS Config rules with auto-remediation would be correct for this detective and reactive compliance requirement.
Why candidates choose this
Candidates may think that AWS Config's automatic remediation can enforce policies across accounts, but they overlook that it is reactive and not centralized like SCPs, which are designed for preventive governance across all accounts in an organization.
✗IAM Access AnalyzerWrong answer — click to see why▾
Why this is wrong here
IAM Access Analyzer helps identify resources shared with external entities, but it does not enforce restrictions on creating IAM users. It is an auditing tool, not a preventive control.
★ When this WOULD be the correct answer
A company wants to identify unintended cross-account access to resources like S3 buckets or IAM roles. IAM Access Analyzer would be the correct choice to generate findings about external access.
Why candidates choose this
Candidates may confuse IAM Access Analyzer with a policy enforcement tool because of the 'Access Analyzer' name, assuming it can analyze and block IAM user creation.
Analysis generated from the official CLF-C02blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
Courseiva writes every CLF-C02 question from scratch — 988 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 CLF-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 CLF-C02 exam.