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. 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.
Exhibit
Shared role policy in Account A:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": ["s3:PutObject", "kms:Decrypt"],
"Resource": [
"arn:aws:s3:::artifact-bucket/*",
"arn:aws:kms:us-east-1:111122223333:key/KEY-AAAA"
]
}
]
}
AssumeRole call from the pipeline:
- Role ARN: arn:aws:iam::111122223333:role/SharedDeployRole
- Session name: build-7412
- No session policy currently supplied
Based on the exhibit, a CI pipeline assumes a shared deployment role in Account A. The role can access several artifact prefixes, but this pipeline must only upload to teamA/prod/ and decrypt using a single KMS key for this execution. Changing the shared role would affect other pipelines. Which approach should the pipeline use?
Shared role policy in Account A:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": ["s3:PutObject", "kms:Decrypt"],
"Resource": [
"arn:aws:s3:::artifact-bucket/*",
"arn:aws:kms:us-east-1:111122223333:key/KEY-AAAA"
]
}
]
}
AssumeRole call from the pipeline:
- Role ARN: arn:aws:iam::111122223333:role/SharedDeployRole
- Session name: build-7412
- No session policy currently supplied
A
Attach a permission boundary to the pipeline's assumed session so the temporary credentials cannot exceed the shared role permissions.
Why wrong: Permission boundaries are attached to IAM users or roles, not to an STS session after the role has already been assumed. They set the maximum permissions for that principal, but they do not provide a per-execution narrowing mechanism for one AssumeRole call while leaving the shared role unchanged for other pipelines.
B
Pass an inline session policy in the AssumeRole request that further restricts the temporary credentials to teamA/prod/ and the approved KMS key.
STS session policies are designed to further restrict the permissions of temporary credentials issued by AssumeRole. In this case, the shared role can remain reusable for other pipelines, while this one execution is narrowed to the exact S3 prefix and KMS key required. The effective permissions become the intersection of the role permissions and the session policy, which preserves least privilege without changing the shared role itself.
C
Add an SCP to Account A that forces all roles to use the same S3 prefix and key whenever they are assumed.
Why wrong: Service control policies act as account-level guardrails, not per-session controls. They cannot tailor permissions for one pipeline execution and would be too broad for a shared-role scenario where different pipelines need different prefixes and keys. SCPs also do not replace identity or session policies for fine-grained runtime restriction.
D
Change the role trust policy to allow only the teamA/prod/ prefix and the key ARN because trust policies can scope S3 object paths directly.
Why wrong: Trust policies control which principals are allowed to assume the role; they do not scope the S3 object paths or KMS key resources that the resulting temporary credentials may access. Resource-level restrictions belong in identity policies, resource policies, or session policies. The scenario specifically asks for a per-execution restriction without modifying the shared role, which makes a session policy the correct control.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Pass an inline session policy in the AssumeRole request that further restricts the temporary credentials to teamA/prod/ and the approved KMS key.
Option B is correct because an inline session policy passed in the AssumeRole request allows you to further restrict the temporary credentials' permissions without modifying the shared role itself. This ensures the pipeline can only upload to teamA/prod/ and decrypt using the specified KMS key, while other pipelines using the same role remain unaffected.
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 permission boundary to the pipeline's assumed session so the temporary credentials cannot exceed the shared role permissions.
Why it's wrong here
Permission boundaries are attached to IAM users or roles, not to an STS session after the role has already been assumed. They set the maximum permissions for that principal, but they do not provide a per-execution narrowing mechanism for one AssumeRole call while leaving the shared role unchanged for other pipelines.
✓
Pass an inline session policy in the AssumeRole request that further restricts the temporary credentials to teamA/prod/ and the approved KMS key.
Why this is correct
STS session policies are designed to further restrict the permissions of temporary credentials issued by AssumeRole. In this case, the shared role can remain reusable for other pipelines, while this one execution is narrowed to the exact S3 prefix and KMS key required. The effective permissions become the intersection of the role permissions and the session policy, which preserves least privilege without changing the shared role itself.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add an SCP to Account A that forces all roles to use the same S3 prefix and key whenever they are assumed.
Why it's wrong here
Service control policies act as account-level guardrails, not per-session controls. They cannot tailor permissions for one pipeline execution and would be too broad for a shared-role scenario where different pipelines need different prefixes and keys. SCPs also do not replace identity or session policies for fine-grained runtime restriction.
✗
Change the role trust policy to allow only the teamA/prod/ prefix and the key ARN because trust policies can scope S3 object paths directly.
Why it's wrong here
Trust policies control which principals are allowed to assume the role; they do not scope the S3 object paths or KMS key resources that the resulting temporary credentials may access. Resource-level restrictions belong in identity policies, resource policies, or session policies. The scenario specifically asks for a per-execution restriction without modifying the shared role, which makes a session policy the correct control.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse permission boundaries (which set a maximum limit) with session policies (which further restrict a specific session), or mistakenly think trust policies can scope resource-level permissions like S3 prefixes or KMS keys.
Trap categories for this question
Scenario analysis trap
Service control policies act as account-level guardrails, not per-session controls. They cannot tailor permissions for one pipeline execution and would be too broad for a shared-role scenario where different pipelines need different prefixes and keys. SCPs also do not replace identity or session policies for fine-grained runtime restriction.
Detailed technical explanation
How to think about this question
When you call AssumeRole with an inline session policy, AWS evaluates the intersection of the role's permissions and the session policy, effectively granting only the overlapping permissions. This is implemented via IAM policy evaluation logic where a deny in either policy overrides an allow. In practice, this allows you to use a shared role with broad permissions while enforcing fine-grained access for specific workloads, such as CI/CD pipelines, without modifying the role itself.
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 — 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: Pass an inline session policy in the AssumeRole request that further restricts the temporary credentials to teamA/prod/ and the approved KMS key. — Option B is correct because an inline session policy passed in the AssumeRole request allows you to further restrict the temporary credentials' permissions without modifying the shared role itself. This ensures the pipeline can only upload to teamA/prod/ and decrypt using the specified KMS key, while other pipelines using the same role remain unaffected.
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 →
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.