SAA-C03 Design Secure Architectures Practice Question
A company uses IAM permission boundaries to prevent developers from escalating privileges. The security team created a permission boundary that allows only read-only actions on most AWS services, but teams can still manage their own resources. A developer can create an IAM role with broad permissions, and the boundary does not appear to be restricting it. Which corrective action best aligns with how permission boundaries work?
⚠ Common exam trap
A common mix-up: candidates assume permission boundaries are automatically inherited or enforced by default, when in fact they must be explicitly applied to each role during creation, and SCPs are often confused as a substitute for permission boundaries.
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
✓
Ensure the role creation process sets the permission boundary on the new role, using the boundary’s ARN in the CreateRole call or role template.
Permission boundaries must be explicitly applied to a role during its creation (via the `CreateRole` API call or an infrastructure-as-code template). Without setting the boundary ARN, the role inherits no restriction, allowing the developer to create a role with broad permissions that bypasses the intended boundary. Option B correctly identifies that the role creation process must include the boundary ARN to enforce the limitation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Rely on an AWS-managed policy attached to the developer’s IAM user; permission boundaries only apply to users.
Why it's wrong here
Permission boundaries apply to roles and users, but relying on an attached AWS-managed policy does not enforce the boundary limit. Also, the issue is that boundaries are not being applied or enforced correctly, not missing general policy attachments.
When this WOULD be correct
If the question asked how to restrict a developer's own permissions (not roles they create), attaching an AWS-managed policy to the user would be correct.
- ✓
Ensure the role creation process sets the permission boundary on the new role, using the boundary’s ARN in the CreateRole call or role template.
Why this is correct
Permission boundaries are evaluated based on the boundary attached to the principal/role being created or used. If a developer creates roles without specifying the boundary, the boundary won’t restrict the resulting permissions. Enforcing boundary attachment via role templates or required parameters ensures every created role is constrained.
- ✗
Attach the permission boundary policy as an SCP in AWS Organizations so it automatically applies to all roles.
Why it's wrong here
SCPs work at the organization level and can restrict maximum permissions, but they are not the same mechanism as permission boundaries. The scenario explicitly mentions permission boundaries and that they do not appear to restrict roles, so the fix should ensure boundary attachment on the created IAM identity.
When this WOULD be correct
In a question where the goal is to enforce a maximum permission baseline across all accounts in an AWS Organization, and the requirement is to prevent any IAM entity from exceeding a defined set of actions, an SCP would be the correct answer.
- ✗
Grant the developer IAM permissions to add a “deny” statement to the boundary policy so the boundary blocks escalation.
Why it's wrong here
A permission boundary does not get modified by granting the creator special permissions arbitrarily. The primary issue is likely that the boundary is not associated with the created role, so escalation is not constrained. Allowing boundary edits would often weaken security.
When this WOULD be correct
In a scenario where a developer needs to implement additional restrictions on a role they manage, and the security team has delegated authority to modify a custom boundary policy for specific use cases, allowing the developer to add deny statements could be correct if explicitly authorized.
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.
✓Ensure the role creation process sets the permission boundary on the new role, using the boundary’s ARN in the CreateRole call or role template.Correct answer▾
Why this is correct
Permission boundaries are evaluated based on the boundary attached to the principal/role being created or used. If a developer creates roles without specifying the boundary, the boundary won’t restrict the resulting permissions. Enforcing boundary attachment via role templates or required parameters ensures every created role is constrained.
✗Rely on an AWS-managed policy attached to the developer’s IAM user; permission boundaries only apply to users.Wrong answer — click to see why▾
Why this is wrong here
Permission boundaries apply to IAM roles and users, not just users. The developer can create a role without a boundary, so attaching a policy to the user does not restrict the role's permissions.
★ When this WOULD be the correct answer
If the question asked how to restrict a developer's own permissions (not roles they create), attaching an AWS-managed policy to the user would be correct.
Why candidates choose this
Candidates may think permission boundaries are only for users, or that a user's attached policy limits all actions they perform, including role creation.
✗Attach the permission boundary policy as an SCP in AWS Organizations so it automatically applies to all roles.Wrong answer — click to see why▾
Why this is wrong here
SCPs apply to all accounts in an AWS Organization but do not replace or enforce IAM permission boundaries on individual roles; permission boundaries must be explicitly set on each role during creation.
★ When this WOULD be the correct answer
In a question where the goal is to enforce a maximum permission baseline across all accounts in an AWS Organization, and the requirement is to prevent any IAM entity from exceeding a defined set of actions, an SCP would be the correct answer.
Why candidates choose this
Candidates may confuse SCPs with permission boundaries because both can restrict permissions, but they operate at different levels (account vs. entity) and have different enforcement mechanisms.
✗Grant the developer IAM permissions to add a “deny” statement to the boundary policy so the boundary blocks escalation.Wrong answer — click to see why▾
Why this is wrong here
Permission boundaries cannot be modified by the user they restrict; only the boundary's creator (e.g., security team) can update it. Granting the developer permission to add a deny statement would violate the boundary's purpose and is not a valid corrective action.
★ When this WOULD be the correct answer
In a scenario where a developer needs to implement additional restrictions on a role they manage, and the security team has delegated authority to modify a custom boundary policy for specific use cases, allowing the developer to add deny statements could be correct if explicitly authorized.
Why candidates choose this
Candidates may think that adding a deny statement to the boundary policy would block privilege escalation, misunderstanding that permission boundaries are set by an admin and cannot be altered by the user they constrain.
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?”
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAA-C03 question from scratch — 302 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.