hardmultiple choiceObjective-mapped

Exhibit

{
  "current_state": {
    "approved_boundary": "arn:aws:iam::111122223333:policy/ApprovedAppBoundary",
    "developer_role_policy": ["iam:CreateRole", "iam:PutRolePolicy", "iam:AttachRolePolicy"],
    "incident": "A new role was created without a permissions boundary and attached an overly permissive policy"
  },
  "desired_state": "All future roles must be created with ApprovedAppBoundary"
}

Based on the exhibit, a development team in member accounts can create IAM roles, but one team created a role without the required permissions boundary. Security wants to ensure that no future role in the organization can exceed the approved boundary, even if a developer has broad IAM permissions. What is the best control to add?

Question 1hardmultiple choice
Full question →

Based on the exhibit, a development team in member accounts can create IAM roles, but one team created a role without the required permissions boundary. Security wants to ensure that no future role in the organization can exceed the approved boundary, even if a developer has broad IAM permissions. What is the best control to add?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Add a permission boundary to the developer role that points to ApprovedAppBoundary.

That only constrains the developer role itself; it does not force new roles to use the approved boundary.

B

Best answer

Add an SCP that denies iam:CreateRole and iam:PutRolePermissionsBoundary unless the request specifies the ApprovedAppBoundary ARN.

An SCP can enforce organization-wide guardrails so roles cannot be created without the required boundary.

C

Distractor review

Use an S3 bucket policy to block policy documents that grant AdministratorAccess.

S3 bucket policies do not control IAM role creation or IAM policy attachment.

D

Distractor review

Require team members to use STS session policies when they create new roles.

Session policies only limit temporary sessions and do not force a permissions boundary on newly created roles.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Add an SCP that denies iam:CreateRole and iam:PutRolePermissionsBoundary unless the request specifies the ApprovedAppBoundary ARN. — The organization needs a preventive guardrail, not just a restriction on an existing role. A service control policy is the correct place to enforce that no one can create roles unless the ApprovedAppBoundary is attached or explicitly requested through the boundary condition. This blocks noncompliant IAM role creation across accounts, even when a developer otherwise has broad IAM permissions in the member account. A boundary on the developer role constrains what that role can do, but it does not guarantee that roles created by the developer will themselves have boundaries. S3 bucket policies are unrelated to IAM role creation. STS session policies only apply to temporary credentials and do not provide a durable organization-wide prevention control for role creation.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.