Question 537 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.

Your company allows application teams to create IAM roles. Each team must be prevented from granting permissions beyond a defined per-role baseline, even if they attach overly permissive identity-based policies to the role. Which AWS feature best enforces this ceiling at the IAM role level?

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

Attach a permission boundary to every role that teams create so the boundary limits the role’s maximum effective permissions

Permission boundaries are an AWS IAM feature that sets the maximum permissions that an identity-based policy can grant to an IAM role. When a permission boundary is attached to a role, the effective permissions are the intersection of the boundary and the role's identity-based policy, ensuring that even if a team attaches an overly permissive policy, the role cannot exceed the boundary's defined limits. This directly enforces a per-role ceiling on permissions, making option B the correct choice.

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.

  • Use an Organizations service control policy (SCP) to cap the maximum permissions for role creation in each account

    Why it's wrong here

    SCPs limit what principals in a member account can do, but they are applied at the account/organization level. They are not the most direct control to enforce a per-role permissions ceiling defined by the baseline that applies to each role the teams create.

    When this WOULD be correct

    An exam question asks: 'How can an organization ensure that no IAM role in any account can exceed a certain set of permissions, regardless of the policies attached to the role?' In that case, an SCP at the root or OU level would enforce a maximum permission ceiling across all roles in the account.

  • Attach a permission boundary to every role that teams create so the boundary limits the role’s maximum effective permissions

    Why this is correct

    A permission boundary acts as a permissions ceiling for the role. Even if the team attaches an identity-based policy that grants broader permissions, the role’s effective permissions are only those allowed by both the identity policy and the permission boundary. This prevents privilege escalation by role policy changes while still allowing teams to manage which policies are attached, within the boundary.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Rely on KMS key policies to restrict permissions because IAM policies cannot override KMS restrictions

    Why it's wrong here

    KMS key policies primarily govern usage of specific KMS keys (for example, Encrypt/Decrypt) and do not provide a general, cross-service cap on what an IAM role can do.

    When this WOULD be correct

    A question asking how to restrict which AWS KMS keys a role can use for encryption/decryption, where you need to ensure that even if an IAM policy grants broad KMS access, the key policy overrides it to deny access.

  • Require multi-factor authentication (MFA) for all role creation requests and deny any request without MFA

    Why it's wrong here

    MFA strengthens authentication for the person creating the role, but it does not limit the permissions the role can actually exercise after it is created. Permission boundaries specifically enforce a maximum set of allowed actions for the role.

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.

Attach a permission boundary to every role that teams create so the boundary limits the role’s maximum effective permissionsCorrect answer

Why this is correct

A permission boundary acts as a permissions ceiling for the role. Even if the team attaches an identity-based policy that grants broader permissions, the role’s effective permissions are only those allowed by both the identity policy and the permission boundary. This prevents privilege escalation by role policy changes while still allowing teams to manage which policies are attached, within the boundary.

Use an Organizations service control policy (SCP) to cap the maximum permissions for role creation in each accountWrong answer — click to see why

Why this is wrong here

SCPs apply to all principals in an account and cannot be scoped to individual roles; they set an account-wide ceiling, not a per-role boundary. The question requires a per-role limit, which SCPs cannot provide.

★ When this WOULD be the correct answer

An exam question asks: 'How can an organization ensure that no IAM role in any account can exceed a certain set of permissions, regardless of the policies attached to the role?' In that case, an SCP at the root or OU level would enforce a maximum permission ceiling across all roles in the account.

Why candidates choose this

Candidates know SCPs can cap permissions, so they mistakenly think they can be applied per role, overlooking that SCPs are account-wide and cannot differentiate between roles within an account.

Rely on KMS key policies to restrict permissions because IAM policies cannot override KMS restrictionsWrong answer — click to see why

Why this is wrong here

KMS key policies control access to encryption keys, not IAM role permissions. They cannot enforce a ceiling on the maximum permissions an IAM role can have, which is the requirement in this question.

★ When this WOULD be the correct answer

A question asking how to restrict which AWS KMS keys a role can use for encryption/decryption, where you need to ensure that even if an IAM policy grants broad KMS access, the key policy overrides it to deny access.

Why candidates choose this

Candidates may confuse permission boundaries with resource-based policies like KMS key policies, thinking that a restrictive key policy can cap permissions, but key policies only apply to the specific key, not to the role's overall permissions.

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 permission boundaries, thinking SCPs can enforce per-role limits, but SCPs apply to all principals in an account and cannot be scoped to individual roles, whereas permission boundaries are specifically designed for that purpose.

Detailed technical explanation

How to think about this question

Permission boundaries work by using the AWS IAM policy evaluation logic where the effective permissions are the intersection of the identity-based policy and the boundary policy. For example, if a role has an identity-based policy granting 's3:*' but a permission boundary only allows 's3:GetObject', the effective permission is only 's3:GetObject'. This is distinct from SCPs, which operate at the account level and cannot be applied to individual roles, making permission boundaries the only IAM-native feature for per-role maximum permission ceilings.

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: Attach a permission boundary to every role that teams create so the boundary limits the role’s maximum effective permissions — Permission boundaries are an AWS IAM feature that sets the maximum permissions that an identity-based policy can grant to an IAM role. When a permission boundary is attached to a role, the effective permissions are the intersection of the boundary and the role's identity-based policy, ensuring that even if a team attaches an overly permissive policy, the role cannot exceed the boundary's defined limits. This directly enforces a per-role ceiling on permissions, making option B the correct choice.

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.