- A
Create an IAM user for each developer and keep the existing broad permissions, rotating keys every 90 days.
Why wrong: Long-lived IAM user access contradicts temporary credentials requirements. Rotating keys reduces exposure but does not prevent repeated leakage or enforce least privilege at scale.
- B
Use an IAM role that developers assume for deployments; attach least-privilege policies for ECS and Auto Scaling; and attach a permission boundary that does not allow iam:* actions, so additional inline or managed policies cannot grant IAM permissions.
Assuming a role provides temporary credentials and removes long-lived keys. Least-privilege policies limit allowed actions, and a permission boundary caps the role's effective permissions so IAM actions cannot be gained through later policy changes.
- C
Attach a policy that allows ecs:* and autoscaling:* and rely on developers to self-review that no IAM statements are added to their roles.
Why wrong: Self-review is not an enforceable control. Without a permission boundary or explicit deny, developers could add iam:* permissions and violate the security requirement.
- D
Create a single shared IAM role with full administrator permissions so developers can troubleshoot faster when deployments fail.
Why wrong: Administrator permissions violate least-privilege and allow IAM changes. A shared role also makes accountability weaker and increases blast radius of mistakes.
Quick Answer
The answer is to use an IAM role with a permission boundary that denies iam:* actions, combined with least-privilege ECS and Auto Scaling policies. This design directly prevents privilege escalation because the permission boundary acts as a hard ceiling on what the role can do—even if a developer tries to attach a new, more permissive policy, the boundary blocks any IAM changes, ensuring they cannot modify IAM resources. On the SAA-C03 exam, this scenario tests your understanding of how permission boundaries differ from service control policies (SCPs) and why they are the correct tool to limit maximum permissions for a role, especially when developers must use temporary credentials via STS AssumeRole. A common trap is choosing a solution that only uses a deny policy for IAM actions, which can be overridden by a later allow; a permission boundary, however, is evaluated first and cannot be bypassed. Memory tip: think of a permission boundary as a “glass ceiling” for IAM—developers can build up to it, but they can never break through to change IAM itself.
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. A key principle to apply: iAM roles provide temporary security credentials when assumed.. 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 retail company lets developers deploy ECS services but they must never be able to modify IAM. The team currently uses an IAM user per developer with an admin-like policy, and several access keys have been leaked. You are asked to redesign access so that: (1) developers authenticate with temporary credentials, (2) they can create/update ECS services and related autoscaling resources, and (3) IAM changes are impossible even if a developer tries to attach new policies.
Which design best meets all requirements?
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.
Clue:
"never"Why it matters: Absolute qualifier. True only if the statement has zero exceptions — be cautious of options that seem obvious but break down in edge cases.
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 role that developers assume for deployments; attach least-privilege policies for ECS and Auto Scaling; and attach a permission boundary that does not allow iam:* actions, so additional inline or managed policies cannot grant IAM permissions.
Option B is correct because it uses an IAM role with temporary credentials (via AWS STS AssumeRole), satisfying the requirement to avoid long-lived access keys. The least-privilege policies for ECS and Auto Scaling grant only the necessary permissions, while the permission boundary explicitly denies iam:* actions, preventing developers from escalating privileges by attaching new policies. This combination ensures developers can deploy ECS services but cannot modify IAM in any way.
Key principle: IAM roles provide temporary security credentials when assumed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create an IAM user for each developer and keep the existing broad permissions, rotating keys every 90 days.
Why it's wrong here
Long-lived IAM user access contradicts temporary credentials requirements. Rotating keys reduces exposure but does not prevent repeated leakage or enforce least privilege at scale.
- ✓
Use an IAM role that developers assume for deployments; attach least-privilege policies for ECS and Auto Scaling; and attach a permission boundary that does not allow iam:* actions, so additional inline or managed policies cannot grant IAM permissions.
Why this is correct
Assuming a role provides temporary credentials and removes long-lived keys. Least-privilege policies limit allowed actions, and a permission boundary caps the role's effective permissions so IAM actions cannot be gained through later policy changes.
Clue confirmation
The clue words "best", "never" in the question point toward this answer.
Related concept
IAM roles provide temporary security credentials when assumed.
- ✗
Attach a policy that allows ecs:* and autoscaling:* and rely on developers to self-review that no IAM statements are added to their roles.
Why it's wrong here
Self-review is not an enforceable control. Without a permission boundary or explicit deny, developers could add iam:* permissions and violate the security requirement.
- ✗
Create a single shared IAM role with full administrator permissions so developers can troubleshoot faster when deployments fail.
Why it's wrong here
Administrator permissions violate least-privilege and allow IAM changes. A shared role also makes accountability weaker and increases blast radius of mistakes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think a permission boundary is only for limiting resource access, but it is specifically designed to prevent privilege escalation by restricting IAM actions, which is the key to meeting the 'IAM changes impossible' requirement.
Detailed technical explanation
How to think about this question
Permission boundaries are an advanced IAM feature that sets the maximum permissions a principal can have; even if a developer attaches a policy granting iam:* actions, the boundary overrides it, effectively preventing privilege escalation. AWS STS (Security Token Service) issues temporary credentials with a configurable expiration (default 1 hour, max 12 hours for role sessions), eliminating the risk of leaked long-lived keys. In practice, combining a permission boundary with a trust policy that requires MFA (aws:MultiFactorAuthPresent condition) further hardens the deployment pipeline against credential theft.
KKey Concepts to Remember
- IAM roles provide temporary security credentials when assumed.
- Least privilege grants only the necessary permissions for a task.
- Permission boundaries set the maximum permissions an IAM entity can have.
- Permission boundaries prevent privilege escalation via policy modification.
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 roles provide temporary security credentials when assumed.
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 roles provide temporary security credentials when assumed., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
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 — IAM roles provide temporary security credentials when assumed..
What is the correct answer to this question?
The correct answer is: Use an IAM role that developers assume for deployments; attach least-privilege policies for ECS and Auto Scaling; and attach a permission boundary that does not allow iam:* actions, so additional inline or managed policies cannot grant IAM permissions. — Option B is correct because it uses an IAM role with temporary credentials (via AWS STS AssumeRole), satisfying the requirement to avoid long-lived access keys. The least-privilege policies for ECS and Auto Scaling grant only the necessary permissions, while the permission boundary explicitly denies iam:* actions, preventing developers from escalating privileges by attaching new policies. This combination ensures developers can deploy ECS services but cannot modify IAM in any way.
What should I do if I get this SAA-C03 question wrong?
Review iAM roles provide temporary security credentials when assumed., 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", "never". 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 roles provide temporary security credentials when assumed.
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 retail company lets developers deploy ECS services but they must never be able to modify IAM. The team currently uses an IAM user per developer with an admin-like policy, and several access keys have been leaked. You are asked to redesign access so that: (1) developers authenticate with temporary credentials, (2) they can create/update ECS services and related autoscaling resources, and (3) IAM changes are impossible even if a developer tries to attach new policies. Which design best meets all requirements?
medium- A.Create an IAM user for each developer and keep the existing broad permissions, rotating keys every 90 days.
- ✓ B.Use an IAM role that developers assume for deployments; attach least-privilege policies for ECS and Auto Scaling; and attach a permission boundary that does not allow iam:* actions, so additional inline or managed policies cannot grant IAM permissions.
- C.Attach a policy that allows ecs:* and autoscaling:* and rely on developers to self-review that no IAM statements are added to their roles.
- D.Create a single shared IAM role with full administrator permissions so developers can troubleshoot faster when deployments fail.
Why B: Option B is correct because it uses an IAM role with temporary credentials (via AWS STS AssumeRole), satisfying the requirement that developers never have long-term access keys. The least-privilege policies restrict actions to ECS and Auto Scaling only, and the permission boundary explicitly denies iam:* actions, preventing developers from escalating privileges by attaching new policies to their role. This combination ensures developers can deploy ECS services but cannot modify IAM in any way.
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
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.