SAA-C03 Design Secure Architectures Practice Question
This SAA-C03 practice question tests your understanding of design secure architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: iAM permissions boundaries set the maximum permissions an IAM entity can have.. 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.
Exhibit
Current IAM policy attached to arn:aws:iam::123456789012:role/AppProvisioner:
- iam:CreateRole
- iam:AttachRolePolicy
- iam:PutRolePolicy
- iam:PassRole
Observed issue:
Developers created arn:aws:iam::123456789012:role/BatchJobRole and attached broad S3 and KMS permissions.
Audit note: "Need delegated role creation with a hard upper bound on permissions."
Based on the exhibit, the platform team wants developers to create application roles for Lambda and ECS, but no developer-created role may ever exceed the approved permission set. Which change best meets this requirement?
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.
Current IAM policy attached to arn:aws:iam::123456789012:role/AppProvisioner:
- iam:CreateRole
- iam:AttachRolePolicy
- iam:PutRolePolicy
- iam:PassRole
Observed issue:
Developers created arn:aws:iam::123456789012:role/BatchJobRole and attached broad S3 and KMS permissions.
Audit note: "Need delegated role creation with a hard upper bound on permissions."
A
Remove all IAM permissions from AppProvisioner and require a central security team to create every role manually.
Why wrong: This would certainly reduce risk, but it removes the delegated administration model the team explicitly needs. It is operationally expensive and slows delivery unnecessarily.
B
Attach a permissions boundary strategy to the delegated workflow and require every created role to include that boundary using the iam:PermissionsBoundary condition.
A permissions boundary creates an upper limit on what any developer-created role can ever do, even if someone later attaches broader policies. Requiring the boundary during role creation prevents privilege escalation while still allowing delegated self-service for approved application roles. This is the standard AWS pattern when teams need to create roles but must remain inside a strict security envelope.
C
Allow developers to keep creating roles, but add a CloudTrail rule that alerts security after a privileged policy is attached.
Why wrong: Alerting after the fact detects bad changes, but it does not prevent a powerful role from being created or used. The requirement is preventive least privilege, not detective monitoring alone.
D
Move the delegated IAM workflow into a separate VPC and restrict it with security groups and network ACLs.
Why wrong: IAM authorization is not controlled by VPC networking constructs. Security groups and network ACLs do not restrict IAM actions such as role creation or policy attachment.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Attach a permissions boundary strategy to the delegated workflow and require every created role to include that boundary using the iam:PermissionsBoundary condition.
Option B is correct because it uses an IAM permissions boundary attached to the delegated role creation workflow, combined with the `iam:PermissionsBoundary` condition key to enforce that every developer-created role must include that boundary. This ensures no role can exceed the approved permission set, as the boundary acts as a maximum limit on permissions, even if the role's policy grants more. The delegated workflow (e.g., AWS Service Catalog or IAM Role creation via Lambda) can create roles, but the boundary prevents any escalation beyond the predefined scope.
Key principle: IAM permissions boundaries set the maximum permissions an IAM entity can have.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Remove all IAM permissions from AppProvisioner and require a central security team to create every role manually.
Why it's wrong here
This would certainly reduce risk, but it removes the delegated administration model the team explicitly needs. It is operationally expensive and slows delivery unnecessarily.
✓
Attach a permissions boundary strategy to the delegated workflow and require every created role to include that boundary using the iam:PermissionsBoundary condition.
Why this is correct
A permissions boundary creates an upper limit on what any developer-created role can ever do, even if someone later attaches broader policies. Requiring the boundary during role creation prevents privilege escalation while still allowing delegated self-service for approved application roles. This is the standard AWS pattern when teams need to create roles but must remain inside a strict security envelope.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
IAM permissions boundaries set the maximum permissions an IAM entity can have.
✗
Allow developers to keep creating roles, but add a CloudTrail rule that alerts security after a privileged policy is attached.
Why it's wrong here
Alerting after the fact detects bad changes, but it does not prevent a powerful role from being created or used. The requirement is preventive least privilege, not detective monitoring alone.
✗
Move the delegated IAM workflow into a separate VPC and restrict it with security groups and network ACLs.
Why it's wrong here
IAM authorization is not controlled by VPC networking constructs. Security groups and network ACLs do not restrict IAM actions such as role creation or policy attachment.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse reactive monitoring (like CloudTrail alerts) with preventive controls, or mistakenly think network isolation (VPC/security groups) can restrict IAM permissions, when only IAM boundaries or service control policies (SCPs) can cap permissions at the identity level.
Detailed technical explanation
How to think about this question
An IAM permissions boundary is a managed policy that sets the maximum permissions a role or user can have; when attached to a role, the effective permissions are the intersection of the identity-based policy and the boundary. The `iam:PermissionsBoundary` condition key in an IAM policy can enforce that any role created via a delegated workflow (e.g., using `iam:CreateRole`) must include a specific boundary ARN, ensuring compliance even if the creator has broad `iam:PassRole` permissions. In practice, this is often implemented with AWS Service Catalog or a custom Lambda function that validates the boundary before calling the IAM API, preventing privilege escalation through role creation.
KKey Concepts to Remember
IAM permissions boundaries set the maximum permissions an IAM entity can have.
Effective permissions are the intersection of identity-based policies and the permissions boundary.
Permissions boundaries are applied to the role itself, not just the creator.
The `iam:PermissionsBoundary` condition can enforce boundary attachment during role creation.
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
IAM permissions boundaries set the maximum permissions an IAM entity can have.
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 iAM permissions boundaries set the maximum permissions an IAM entity can have., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design Secure Architectures — This question tests Design Secure Architectures — IAM permissions boundaries set the maximum permissions an IAM entity can have..
What is the correct answer to this question?
The correct answer is: Attach a permissions boundary strategy to the delegated workflow and require every created role to include that boundary using the iam:PermissionsBoundary condition. — Option B is correct because it uses an IAM permissions boundary attached to the delegated role creation workflow, combined with the `iam:PermissionsBoundary` condition key to enforce that every developer-created role must include that boundary. This ensures no role can exceed the approved permission set, as the boundary acts as a maximum limit on permissions, even if the role's policy grants more. The delegated workflow (e.g., AWS Service Catalog or IAM Role creation via Lambda) can create roles, but the boundary prevents any escalation beyond the predefined scope.
What should I do if I get this SAA-C03 question wrong?
Review iAM permissions boundaries set the maximum permissions an IAM entity can have., 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?
IAM permissions boundaries set the maximum permissions an IAM entity can have.
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 →
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.
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.
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.
Sign in to join the discussion.