easymultiple choiceObjective-mapped

A team wants to delegate IAM management to developers, but must ensure developers can never grant themselves permissions beyond a specific limit. Which AWS mechanism best matches this requirement?

Question 1easymultiple choice
Full question →

A team wants to delegate IAM management to developers, but must ensure developers can never grant themselves permissions beyond a specific limit. Which AWS mechanism best matches this requirement?

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

Use an IAM permission boundary on roles/users that developers create, so the developers’ effective permissions are capped by the boundary policy.

Permission boundaries constrain the maximum permissions that an identity can receive. Even if developers attach an identity policy that allows broader actions, the effective permissions are limited to the intersection of the identity policy and the boundary.

B

Distractor review

Rely only on their IAM managed policies and instruct developers to self-check against internal guidelines.

Guidelines and self-checks are not enforceable controls. Developers could accidentally (or intentionally) attach policies that exceed the intended maximum permissions.

C

Distractor review

Use a service control policy (SCP) that applies only to the developers’ IAM users in the account.

SCPs are evaluated at the organization/account level and constrain allowed API actions for principal types across affected accounts/OUs. They are not the most direct tool for capping an individual principal’s maximum effective permissions in the way permission boundaries do (and SCPs are not designed for per-identity “maximum permission” limits).

D

Distractor review

Use a KMS key policy to restrict IAM actions, because IAM actions can be controlled with KMS.

KMS key policies govern cryptographic key usage (for example, Encrypt/Decrypt) and do not control whether a principal is authorized to grant or perform IAM permissions. KMS does not function as an IAM permissions cap mechanism.

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: Use an IAM permission boundary on roles/users that developers create, so the developers’ effective permissions are capped by the boundary policy. — IAM permission boundaries are specifically designed for delegated IAM administration with guardrails. When a boundary is set on roles/users, AWS computes the effective permissions as the intersection of (a) the identity-based policy the developers attach and (b) the permissions allowed by the boundary. This ensures developers cannot escalate beyond the approved maximum, matching the requirement. Why others are wrong: Option B is not enforceable and cannot reliably prevent privilege escalation. Option C describes SCP usage, which is typically broader and account/OU-oriented rather than a per-principal maximum cap. Option D misuses KMS key policies, which relate to cryptographic operations, not IAM authorization boundaries for identity policies.

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.