- 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.
Fix Dropped Session Tags: Add sts:TagSession Permission
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.
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 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.
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.
- ✓
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
Read the scenario before looking for a memorised answer.
- ✗
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.
When this WOULD be correct
If the question described that the ABAC condition is incorrectly blocking legitimate access due to a mismatch in tag values or syntax, and the goal is to simplify access control without tags, then removing the condition would be correct.
- ✗
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.
When this WOULD be correct
If the question were about restricting which IAM users or roles can assume a role based on a project tag attached to the caller (e.g., only users with Project=blue can assume the role), then placing the condition in the trust policy would be correct.
- ✗
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.
When this WOULD be correct
This option would be correct if the deployment failed due to an AccessDenied error when trying to decrypt a KMS-encrypted resource, and the role lacked kms:Decrypt permission for the specific key.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Add permissions for sts:TagSession to the IAM role so the CI pipeline is allowed to pass the Project session tag during AssumeRole.Correct answer▾
Why this is correct
Session tags are not automatically granted; the role needs sts:TagSession permission to allow passing tags into the session.
✗Remove the ABAC condition using aws:PrincipalTag/Project so the policy ignores session tags.Wrong answer — click to see why▾
Why this is wrong here
Removing the ABAC condition would bypass the intended security model, but the root cause is that the session tag is missing because the CI pipeline lacks permission to pass it, not because the condition is misconfigured.
★ When this WOULD be the correct answer
If the question described that the ABAC condition is incorrectly blocking legitimate access due to a mismatch in tag values or syntax, and the goal is to simplify access control without tags, then removing the condition would be correct.
Why candidates choose this
Candidates may think the condition is causing the failure and removing it is a quick fix, without understanding that the session tag is missing due to missing sts:TagSession permission.
✗Move the aws:PrincipalTag/Project condition into the trust policy so it applies during the AssumeRole call.Wrong answer — click to see why▾
Why this is wrong here
The trust policy controls who can assume the role, not what tags are passed. Moving the condition there would not fix the missing session tag; it would only restrict which principals can assume the role based on their own tags.
★ When this WOULD be the correct answer
If the question were about restricting which IAM users or roles can assume a role based on a project tag attached to the caller (e.g., only users with Project=blue can assume the role), then placing the condition in the trust policy would be correct.
Why candidates choose this
Candidates may confuse the trust policy (who can assume) with the permissions policy (what the assumed role can do), thinking that moving the condition to the trust policy would enforce tag propagation.
✗Add kms:Decrypt permission to the CI role because missing tags are typically caused by KMS authorization failures.Wrong answer — click to see why▾
Why this is wrong here
The issue is that session tags are not being passed during AssumeRole, not a KMS authorization failure. KMS permissions are irrelevant to missing session tags.
★ When this WOULD be the correct answer
This option would be correct if the deployment failed due to an AccessDenied error when trying to decrypt a KMS-encrypted resource, and the role lacked kms:Decrypt permission for the specific key.
Why candidates choose this
Candidates may confuse general AccessDenied errors with KMS issues, or assume that missing tags are a symptom of KMS failures, but the question explicitly states the session lacks the tag.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates assume `AssumeRole` with session tags always succeeds in applying the tags, but AWS silently drops tags if the caller lacks `sts:TagSession` permission, leading to a confusing AccessDenied on downstream actions.
Detailed technical explanation
How to think about this question
Under the hood, when you call `AssumeRole` with session tags, the IAM service checks the role's trust policy and the caller's permissions. If the caller lacks `sts:TagSession`, the API still returns a success response but the tags are not applied to the resulting session—this is a silent failure that often confuses developers. In real-world scenarios, this commonly occurs when CI/CD pipelines use `AssumeRole` with tags for ABAC, and the fix is to ensure the role's trust policy allows `sts:TagSession` (or the caller has `iam:PassRole` with `iam:PassedToService` conditions).
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 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.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
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: 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 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.
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. 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 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.
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.