hardmulti selectObjective-mapped

A platform team lets project administrators create IAM roles for workloads in their own AWS accounts, but every role must stay inside a fixed security baseline. The organization also wants to block all member accounts from using AWS Regions outside us-east-1 and us-west-2. Which three controls should be used? Select three.

Question 1hardmulti select
Full question →

A platform team lets project administrators create IAM roles for workloads in their own AWS accounts, but every role must stay inside a fixed security baseline. The organization also wants to block all member accounts from using AWS Regions outside us-east-1 and us-west-2. Which three controls should be used? Select three.

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

Best answer

Attach a permissions boundary to each role created through the delegation process.

A permissions boundary caps the maximum permissions a created role can ever receive, even if an administrator later attaches broader policies. This is the right mechanism for a fixed security baseline on delegated role creation.

B

Best answer

Require iam:PermissionsBoundary in the role creation policy so every new role must include the approved boundary.

The creation policy should enforce that the boundary is present at creation time. This prevents a delegated admin from simply omitting the boundary and creating a role that exceeds the approved limit.

C

Best answer

Use an SCP to deny actions in all AWS Regions except us-east-1 and us-west-2.

An SCP is the correct organizational guardrail for region restrictions across member accounts. It applies broadly and consistently, which is ideal for blocking unapproved Regions regardless of the local IAM configuration.

D

Distractor review

Grant AdministratorAccess to the project administrators and rely on later audits for enforcement.

AdministratorAccess defeats the purpose of a baseline and does not prevent over-privileged role creation. Audits are detective, not preventive, and cannot enforce the required control at creation time.

E

Distractor review

Use an AWS Config rule alone to stop role creation if the permissions are too broad.

AWS Config is useful for detection and compliance reporting, but by itself it does not prevent the creation of an over-permissioned role. The scenario requires preventive controls at the IAM and organization levels.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

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?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Attach a permissions boundary to each role created through the delegation process. — This scenario needs both delegation control and org-wide guardrails. A permissions boundary sets the upper limit for any created role, and the delegated creation policy must require that boundary so it cannot be skipped. Separately, an SCP is the right way to block the member accounts from using unapproved Regions. Together, these controls prevent privilege creep while still allowing controlled self-service. Why others are wrong: AdministratorAccess is the opposite of least privilege and does not enforce a boundary. AWS Config can report or trigger remediation, but it does not stop role creation in the moment. The correct answer uses preventive controls: a permissions boundary, an IAM creation condition, and an SCP for regional guardrails.

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.