Question 533 of 1,040
Design Secure ArchitecturesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to add an explicit IAM Deny for both `iam:PutRolePermissionsBoundary` and `iam:DeleteRolePermissionsBoundary` on the affected roles. This is correct because an explicit Deny overrides any Allow in AWS IAM policy evaluation logic, making the permission boundary immutable once set—even if the operator holds the corresponding Allow permissions. On the SAA-C03 exam, this scenario tests your understanding of the IAM policy evaluation hierarchy, where explicit Denies always take precedence. A common trap is assuming that simply removing the operator’s Allow permissions is sufficient, but that fails if the operator later regains those permissions through a different policy or group membership. To prevent removal of IAM permission boundaries, always enforce an explicit Deny as a safety net. Memory tip: think “Deny beats Allow every time”—when you need to lock down a boundary, use an explicit Deny to make it bulletproof.

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. A key principle to apply: explicit Deny statements always override Allow statements in IAM policy evaluation.. 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 organization uses IAM permission boundaries to prevent privilege escalation. A deployment role was created with a permission boundary. After an incident, you discover that an operator was later able to remove or change the permission boundary (the operator has iam:PutRolePermissionsBoundary permissions). You need to ensure operators cannot remove or change the permission boundary after it is set. What is the best security control to add?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

Question 1mediummultiple choice
Full question →

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

Add an explicit IAM Deny for operators on both iam:PutRolePermissionsBoundary and iam:DeleteRolePermissionsBoundary for all affected roles.

Option B is correct because adding an explicit IAM Deny for both `iam:PutRolePermissionsBoundary` and `iam:DeleteRolePermissionsBoundary` on the affected roles prevents operators from removing or changing the permission boundary, even if they have the corresponding Allow permissions. This is a classic use of an explicit Deny, which overrides any Allow in AWS IAM policy evaluation logic, ensuring the boundary remains immutable after deployment.

Key principle: Explicit Deny statements always override Allow statements in IAM policy evaluation.

Answer analysis

Option-by-option breakdown

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

  • Grant operators iam:PutRolePermissionsBoundary so they can reapply the boundary if needed.

    Why it's wrong here

    Allowing iam:PutRolePermissionsBoundary gives operators the ability to modify the permission boundary, which directly contradicts the goal of preventing boundary removal or changes.

  • Add an explicit IAM Deny for operators on both iam:PutRolePermissionsBoundary and iam:DeleteRolePermissionsBoundary for all affected roles.

    Why this is correct

    An explicit Deny prevents permission boundary updates or removal, even if the operator has allow permissions elsewhere. This directly protects the permission boundary integrity and maintains the privilege-limiting guardrail.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Explicit Deny statements always override Allow statements in IAM policy evaluation.

  • Rely only on the role’s trust policy so operators cannot assume the role.

    Why it's wrong here

    The trust policy controls who can assume the role. It does not prevent operators from changing the role’s permission boundary, which can enable privilege escalation for future role usage.

  • Attach a more permissive permission boundary so the roles remain functional after changes.

    Why it's wrong here

    Making the boundary more permissive undermines the purpose of the control and does not stop operators from removing or changing the boundary.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often assume that simply not granting the `iam:PutRolePermissionsBoundary` permission is sufficient, but they overlook that an operator with broader IAM privileges (e.g., `iam:PassRole` or `iam:CreatePolicyVersion`) could still modify the boundary unless an explicit Deny is added.

Detailed technical explanation

How to think about this question

Under the hood, AWS IAM evaluates policies in the order: explicit Deny, then Allow, with an implicit Deny as default. An explicit Deny on `iam:PutRolePermissionsBoundary` and `iam:DeleteRolePermissionsBoundary` ensures that even if the operator has an Allow from a managed policy or inline policy, the Deny takes precedence. In a real-world scenario, this is critical for compliance frameworks like SOC 2 or PCI DSS, where permission boundaries must be immutable to prevent lateral movement and privilege escalation by compromised operators.

KKey Concepts to Remember

  • Explicit Deny statements always override Allow statements in IAM policy evaluation.
  • IAM permission boundaries define the maximum permissions an IAM entity can have.
  • The `iam:PutRolePermissionsBoundary` action allows setting or changing a role's permission boundary.
  • The `iam:DeleteRolePermissionsBoundary` action allows removing a role's permission boundary.

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

Explicit Deny statements always override Allow statements in IAM policy evaluation.

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.

Review explicit Deny statements always override Allow statements in IAM policy evaluation., then practise related SAA-C03 questions on the same topic to reinforce the concept.

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 — Explicit Deny statements always override Allow statements in IAM policy evaluation..

What is the correct answer to this question?

The correct answer is: Add an explicit IAM Deny for operators on both iam:PutRolePermissionsBoundary and iam:DeleteRolePermissionsBoundary for all affected roles. — Option B is correct because adding an explicit IAM Deny for both `iam:PutRolePermissionsBoundary` and `iam:DeleteRolePermissionsBoundary` on the affected roles prevents operators from removing or changing the permission boundary, even if they have the corresponding Allow permissions. This is a classic use of an explicit Deny, which overrides any Allow in AWS IAM policy evaluation logic, ensuring the boundary remains immutable after deployment.

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

Review explicit Deny statements always override Allow statements in IAM policy evaluation., then practise related SAA-C03 questions on the same topic to reinforce the concept.

Are there clue words in this question I should notice?

Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

What is the key concept behind this question?

Explicit Deny statements always override Allow statements in IAM policy evaluation.

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.