Question 370 of 1,040
Design Secure ArchitectureseasyMultiple ChoiceObjective-mapped

SAA-C03 Design Secure Architectures Practice Question

This SAA-C03 practice question tests your understanding of design secure architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

You manage multiple AWS accounts under AWS Organizations. A compliance requirement states: no account is allowed to create new IAM access keys for IAM users. Local administrators may attempt to override permissions. Which mechanism should you use to enforce this guardrail across all accounts?

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

An Organizations service control policy (SCP) that explicitly denies CreateAccessKey

An SCP is the correct mechanism because it operates at the AWS Organizations root, OU, or account level to define a central guardrail that cannot be overridden by any IAM principal, including account administrators. By explicitly denying the `iam:CreateAccessKey` action, the SCP ensures that no IAM user in any account can create new access keys, fulfilling the compliance requirement across all accounts.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • An IAM permissions policy attached to a role that only your security team uses

    Why it's wrong here

    An IAM policy limits what the specific role can do, but it does not prevent other accounts or other principals from creating access keys.

    When this WOULD be correct

    This option would be correct in a scenario where the requirement is to restrict access key creation only for users who assume a specific role (e.g., a cross-account role used by security auditors), and the organization does not need to enforce the restriction on all users across all accounts.

  • An Organizations service control policy (SCP) that explicitly denies CreateAccessKey

    Why this is correct

    SCPs provide guardrails that apply to all principals in member accounts. By explicitly denying the IAM action at the organization level, you can prevent access key creation even if local IAM policies would otherwise allow it.

    Related concept

    Read the scenario before looking for a memorised answer.

  • A KMS key policy that blocks key creation and reuse

    Why it's wrong here

    KMS key policies control cryptographic key usage, not IAM access key creation. They do not enforce IAM action restrictions across accounts.

    When this WOULD be correct

    A question requiring encryption key management restrictions, such as 'You need to prevent users from disabling or deleting a specific KMS key used for S3 bucket encryption across multiple accounts.' In that case, a KMS key policy with explicit deny statements would be the correct mechanism.

  • A permission boundary on a single IAM role

    Why it's wrong here

    Permission boundaries apply to a specific role and do not automatically cover all principals across all accounts. They also do not override the need for organization-wide enforcement.

    When this WOULD be correct

    In a scenario where you need to restrict the maximum permissions for a specific IAM role (e.g., a developer role) without affecting other roles or users, a permission boundary would be the correct mechanism.

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 SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.

An Organizations service control policy (SCP) that explicitly denies CreateAccessKeyCorrect answer

Why this is correct

SCPs provide guardrails that apply to all principals in member accounts. By explicitly denying the IAM action at the organization level, you can prevent access key creation even if local IAM policies would otherwise allow it.

An IAM permissions policy attached to a role that only your security team usesWrong answer — click to see why

Why this is wrong here

An IAM permissions policy attached to a role used only by the security team cannot enforce a guardrail across all accounts because it only applies to principals assuming that role, not to all IAM users in every account. Local administrators in other accounts can still create access keys unless explicitly denied by a centralized policy like an SCP.

★ When this WOULD be the correct answer

This option would be correct in a scenario where the requirement is to restrict access key creation only for users who assume a specific role (e.g., a cross-account role used by security auditors), and the organization does not need to enforce the restriction on all users across all accounts.

Why candidates choose this

Candidates may think that attaching a deny policy to a security team role is a simple way to enforce restrictions, but they overlook that it only applies to that role's sessions, not to all IAM users in the organization.

A KMS key policy that blocks key creation and reuseWrong answer — click to see why

Why this is wrong here

KMS key policies control encryption key usage, not IAM user actions like creating access keys. They cannot enforce a guardrail against IAM operations across accounts.

★ When this WOULD be the correct answer

A question requiring encryption key management restrictions, such as 'You need to prevent users from disabling or deleting a specific KMS key used for S3 bucket encryption across multiple accounts.' In that case, a KMS key policy with explicit deny statements would be the correct mechanism.

Why candidates choose this

Candidates may confuse 'key' in KMS with 'access key' and think KMS policies can control access key creation, or they may mistakenly believe KMS policies can enforce IAM actions.

A permission boundary on a single IAM roleWrong answer — click to see why

Why this is wrong here

A permission boundary applies only to a single IAM role, not to all users and roles across multiple accounts, so it cannot enforce the guardrail organization-wide.

★ When this WOULD be the correct answer

In a scenario where you need to restrict the maximum permissions for a specific IAM role (e.g., a developer role) without affecting other roles or users, a permission boundary would be the correct mechanism.

Why candidates choose this

Candidates may confuse permission boundaries with service control policies, thinking they can be applied broadly, but permission boundaries are limited to individual IAM entities.

Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse SCPs with IAM permission boundaries or think that a restrictive IAM policy on a single role can enforce a global guardrail, but only SCPs provide organization-wide, unoverridable control over all principals.

Detailed technical explanation

How to think about this question

SCPs are evaluated before any IAM policies and act as a filter that denies actions even if an IAM policy grants them; they use a deny-by-default model where an explicit deny overrides any allow. In a multi-account environment, SCPs are the only mechanism that can enforce a blanket restriction across all accounts without requiring per-account configuration, and they cannot be bypassed by account administrators because they are applied at the organization level.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SAA-C03 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Design Secure Architectures — This question tests Design Secure Architectures — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: An Organizations service control policy (SCP) that explicitly denies CreateAccessKey — An SCP is the correct mechanism because it operates at the AWS Organizations root, OU, or account level to define a central guardrail that cannot be overridden by any IAM principal, including account administrators. By explicitly denying the `iam:CreateAccessKey` action, the SCP ensures that no IAM user in any account can create new access keys, fulfilling the compliance requirement across all accounts.

What should I do if I get this SAA-C03 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

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

Keep practising

More SAA-C03 practice questions

Last reviewed: Jun 11, 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 SAA-C03 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 SAA-C03 exam.