- A
Attach a customer-managed IAM policy to the developers and let them create roles freely.
Why wrong: This grants permissions directly to the developers, but it does not cap the maximum permissions of roles they create.
- B
Use an IAM permission boundary on the developer principals and require created roles to include the boundary.
A permission boundary sets the upper limit for permissions that an IAM principal or created role can receive. By combining developer role creation permissions with a required boundary, security can allow self-service role creation while preventing privilege escalation. Even if developers attach broader identity policies later, the effective permissions cannot exceed the boundary. This is the right control when you need delegated administration with a hard ceiling on privileges.
- C
Create a service-linked role for ECS and let developers reuse it for all workloads.
Why wrong: Service-linked roles are managed by AWS for specific service integrations, not for custom developer delegation models.
- D
Add an S3 bucket policy that only allows tagged roles to be created.
Why wrong: Bucket policies apply to S3 access, not to IAM role creation or the permission limits of newly created roles.
Quick Answer
The answer is to use an IAM permission boundary on the developer principals and require created roles to include the boundary. This is correct because a permission boundary defines the maximum permissions that an identity-based policy can grant, acting as a hard ceiling on what any role created by the developers can do. By attaching the boundary to the developers' IAM user or role and enforcing that every new role they create includes that same boundary, the platform team guarantees that no role can ever exceed the predefined permission set, and developers cannot escalate their own privileges later. On the SAA-C03 exam, this scenario tests your understanding of how permission boundaries differ from service control policies (SCPs) and how they prevent privilege escalation in delegated administration. A common trap is confusing permission boundaries with resource-based policies or assuming a developer with an attached boundary can simply attach a broader policy to bypass it—the boundary blocks that. Memory tip: think of the boundary as a "maximum cap" that no policy can exceed, like a speed governor on a car.
SAA-C03 Design Secure Architectures Practice Question
This SAA-C03 practice question tests your understanding of design secure architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.
A platform team wants application developers to create IAM roles for their ECS tasks, but security must guarantee that no role created by those developers can ever exceed a predefined permission set. The developers also should not be able to attach broader permissions to themselves later. What should the team implement?
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
Use an IAM permission boundary on the developer principals and require created roles to include the boundary.
Option B is correct because IAM permission boundaries allow the platform team to define a maximum set of permissions that any role created by the developers can have. By attaching a permission boundary to the developers' IAM user or role, and requiring that any new role they create includes that boundary, the developers cannot grant permissions beyond the boundary—even if they attach a broader policy. This ensures that no role can ever exceed the predefined permission set, and developers cannot escalate their own privileges later.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Attach a customer-managed IAM policy to the developers and let them create roles freely.
Why it's wrong here
This grants permissions directly to the developers, but it does not cap the maximum permissions of roles they create.
- ✓
Use an IAM permission boundary on the developer principals and require created roles to include the boundary.
Why this is correct
A permission boundary sets the upper limit for permissions that an IAM principal or created role can receive. By combining developer role creation permissions with a required boundary, security can allow self-service role creation while preventing privilege escalation. Even if developers attach broader identity policies later, the effective permissions cannot exceed the boundary. This is the right control when you need delegated administration with a hard ceiling on privileges.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Create a service-linked role for ECS and let developers reuse it for all workloads.
Why it's wrong here
Service-linked roles are managed by AWS for specific service integrations, not for custom developer delegation models.
- ✗
Add an S3 bucket policy that only allows tagged roles to be created.
Why it's wrong here
Bucket policies apply to S3 access, not to IAM role creation or the permission limits of newly created roles.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse IAM permission boundaries with simple policy attachments, thinking that attaching a restrictive policy to the developer's user account is sufficient to control the roles they create, but permission boundaries are the only mechanism that limits the effective permissions of roles created by delegated users.
Detailed technical explanation
How to think about this question
IAM permission boundaries work by setting a maximum permissions envelope for an IAM entity (user or role). When a developer creates a role, they must attach a permissions boundary policy that defines the maximum permissions the role can have; any policy attached to the role is evaluated against the boundary, and only permissions within the boundary are effective. This mechanism is enforced at the AWS API level—the `iam:CreateRole` and `iam:PutRolePermissionsBoundary` actions must be allowed, and the boundary policy is evaluated during role creation and subsequent policy attachment. A real-world scenario is a multi-account environment where a central security team uses permission boundaries to delegate role creation to application teams while ensuring no role can access sensitive services like IAM or KMS.
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.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design Secure Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Secure Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
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.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Secure Architectures — This question tests Design Secure Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use an IAM permission boundary on the developer principals and require created roles to include the boundary. — Option B is correct because IAM permission boundaries allow the platform team to define a maximum set of permissions that any role created by the developers can have. By attaching a permission boundary to the developers' IAM user or role, and requiring that any new role they create includes that boundary, the developers cannot grant permissions beyond the boundary—even if they attach a broader policy. This ensures that no role can ever exceed the predefined permission set, and developers cannot escalate their own privileges later.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Same concept, more angles
1 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A platform team lets application teams create IAM roles in member accounts through Infrastructure as Code. Security says every new role must stay within a centrally approved permission ceiling, even if someone later attaches broader managed policies or inline policies. Which control should be used to enforce that maximum permission set?
hard- A.Use an AWS Organizations service control policy to grant the role all needed permissions directly.
- ✓ B.Attach a permissions boundary to each role so the role can never exceed the approved ceiling.
- C.Use a resource-based policy on Amazon S3 to restrict the permissions that IAM roles can receive.
- D.Require temporary STS session policies whenever the role is assumed.
Why B: A permissions boundary is an AWS IAM feature that sets the maximum permissions an IAM role can have. When attached to a role, any policy that grants permissions beyond the boundary is effectively ignored, ensuring the role cannot exceed the approved permission ceiling even if broader managed or inline policies are later attached. This directly enforces the security requirement without restricting the application teams' ability to create roles via Infrastructure as Code.
Last reviewed: Jun 11, 2026
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.