- A
Add permissions for sts:TagSession to the IAM role so the CI pipeline is allowed to pass the Project session tag during AssumeRole.
Session tags are not automatically granted; the role needs sts:TagSession permission to allow passing tags into the session.
- B
Remove the ABAC condition using aws:PrincipalTag/Project so the policy ignores session tags.
Why wrong: Removing the condition would broaden access and violates the ABAC design that restricts actions to the correct project.
- C
Move the aws:PrincipalTag/Project condition into the trust policy so it applies during the AssumeRole call.
Why wrong: Even if conditions exist in the trust policy, the session tags must be allowed and provided. The failure indicates the tag was not populated.
- D
Add kms:Decrypt permission to the CI role because missing tags are typically caused by KMS authorization failures.
Why wrong: The observed symptom is that the session tag is missing, not that KMS decryption is denied. These are unrelated controls.
Quick Answer
The answer is to add permissions for sts:TagSession to the IAM role. This is correct because when you call STS AssumeRole with session tags, the calling principal must have explicit permission on the `sts:TagSession` action; without it, the tags are silently dropped even though the AssumeRole call itself succeeds. This means the ABAC condition on `aws:PrincipalTag/Project` never sees the tag, causing AccessDenied on downstream resources. On the SAA-C03 exam, this tests your understanding of how STS session tags interact with IAM permissions—a common trap is assuming that passing tags in the API call is enough. Remember: passing a session tag is a separate permission from assuming the role. A helpful memory tip is "Tag it to pass it"—you must be allowed to tag the session before the tag will stick.
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: session tags are temporary attributes passed during an STS AssumeRole call.. 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.
Your CI system assumes an IAM role RoleForDeploy using STS AssumeRole and includes a session tag called Project=blue. The role’s permissions policy uses an ABAC condition like aws:PrincipalTag/Project to allow access only to resources tagged with the same project.
AssumeRole succeeds, but deployments fail with AccessDenied. CloudTrail shows the role was assumed, yet the effective session does not contain the Project tag.
Which change most directly fixes this issue?
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
Add permissions for sts:TagSession to the IAM role so the CI pipeline is allowed to pass the Project session tag during AssumeRole.
Option A is correct because when an IAM role is assumed with STS AssumeRole and session tags are included, the calling principal must have explicit permission to pass those tags via the `sts:TagSession` action. Without this permission, the session tags are silently dropped, even though the AssumeRole call succeeds. Adding `sts:TagSession` to the role's permissions allows the CI pipeline to pass the `Project=blue` tag, making the ABAC condition on `aws:PrincipalTag/Project` evaluate correctly and granting access to tagged resources.
Key principle: Session tags are temporary attributes passed during an STS AssumeRole call.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Add permissions for sts:TagSession to the IAM role so the CI pipeline is allowed to pass the Project session tag during AssumeRole.
Why this is correct
Session tags are not automatically granted; the role needs sts:TagSession permission to allow passing tags into the session.
Related concept
Session tags are temporary attributes passed during an STS AssumeRole call.
- ✗
Remove the ABAC condition using aws:PrincipalTag/Project so the policy ignores session tags.
Why it's wrong here
Removing the condition would broaden access and violates the ABAC design that restricts actions to the correct project.
- ✗
Move the aws:PrincipalTag/Project condition into the trust policy so it applies during the AssumeRole call.
Why it's wrong here
Even if conditions exist in the trust policy, the session tags must be allowed and provided. The failure indicates the tag was not populated.
- ✗
Add kms:Decrypt permission to the CI role because missing tags are typically caused by KMS authorization failures.
Why it's wrong here
The observed symptom is that the session tag is missing, not that KMS decryption is denied. These are unrelated controls.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume session tags are automatically applied when passed in the AssumeRole call, but AWS requires explicit `sts:TagSession` permission for the tags to take effect, which is a subtle but critical detail tested in ABAC scenarios.
Detailed technical explanation
How to think about this question
When using STS AssumeRole with session tags, the `sts:TagSession` permission must be granted to the role being assumed (or to the user/role calling AssumeRole) to allow the tags to be included in the resulting session. Without it, the tags are silently ignored, and the session principal tags remain empty. This is a common pitfall in ABAC implementations where tags are passed during role assumption but the required permission is overlooked, leading to AccessDenied errors despite successful role assumption.
KKey Concepts to Remember
- Session tags are temporary attributes passed during an STS AssumeRole call.
- The `sts:TagSession` permission is required for a role to accept session tags.
- ABAC policies use `aws:PrincipalTag` to evaluate session tags for access control.
- Without `sts:TagSession`, passed session tags are ignored, leading to `AccessDenied` if ABAC is in use.
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
Session tags are temporary attributes passed during an STS AssumeRole call.
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 session tags are temporary attributes passed during an STS AssumeRole call., 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 — Session tags are temporary attributes passed during an STS AssumeRole call..
What is the correct answer to this question?
The correct answer is: Add permissions for sts:TagSession to the IAM role so the CI pipeline is allowed to pass the Project session tag during AssumeRole. — Option A is correct because when an IAM role is assumed with STS AssumeRole and session tags are included, the calling principal must have explicit permission to pass those tags via the `sts:TagSession` action. Without this permission, the session tags are silently dropped, even though the AssumeRole call succeeds. Adding `sts:TagSession` to the role's permissions allows the CI pipeline to pass the `Project=blue` tag, making the ABAC condition on `aws:PrincipalTag/Project` evaluate correctly and granting access to tagged resources.
What should I do if I get this SAA-C03 question wrong?
Review session tags are temporary attributes passed during an STS AssumeRole call., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Session tags are temporary attributes passed during an STS AssumeRole call.
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. Your CI system assumes an IAM role RoleForDeploy using STS AssumeRole and includes a session tag called Project=blue. The role’s permissions policy uses an ABAC condition like aws:PrincipalTag/Project to allow access only to resources tagged with the same project. AssumeRole succeeds, but deployments fail with AccessDenied. CloudTrail shows the role was assumed, yet the effective session does not contain the Project tag. Which change most directly fixes this issue?
medium- ✓ A.Add permissions for sts:TagSession to the IAM role so the CI pipeline is allowed to pass the Project session tag during AssumeRole.
- B.Remove the ABAC condition using aws:PrincipalTag/Project so the policy ignores session tags.
- C.Move the aws:PrincipalTag/Project condition into the trust policy so it applies during the AssumeRole call.
- D.Add kms:Decrypt permission to the CI role because missing tags are typically caused by KMS authorization failures.
Why A: Option A is correct because when using AWS Security Token Service (STS) AssumeRole with session tags, the calling entity must have explicit permission to pass those tags via the `sts:TagSession` action. Without this permission, the AssumeRole call succeeds but the session tags are silently dropped, causing the ABAC condition `aws:PrincipalTag/Project` to evaluate to false and deny access to resources. Adding `sts:TagSession` to the role's permissions policy allows the CI pipeline to include the `Project=blue` tag in the assumed role session.
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.