Question 595 of 1,546
Security and CompliancehardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to add a condition in the IAM role’s trust policy that checks for the instance tag using the `aws:ResourceTag` condition key. This works because the trust policy defines who can assume the role, and by including a condition like `"StringEquals": {"aws:ResourceTag/Environment": "Production"}`, you restrict role assumption solely to EC2 instances bearing that specific tag. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this scenario tests your understanding of IAM trust policies versus identity-based policies—a common trap is assuming tags are automatically inherited by the session, but they must be explicitly evaluated in the trust policy. Remember that SCPs apply at the account level, not to individual instances, and instance profiles themselves cannot enforce tag checks. A helpful memory tip: “Trust policies tag-check the resource, not the requester”—the condition key `aws:ResourceTag` evaluates the EC2 instance’s tags, not the user’s.

SOA-C02 Security and Compliance Practice Question

This SOA-C02 practice question tests your understanding of security and compliance. 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 company uses IAM roles to grant EC2 instances access to S3 buckets. After a recent security audit, the SysOps administrator must ensure that only instances with a specific tag (Environment=Production) can assume the role. How can this be achieved?

Question 1hardmultiple choice
Full question →

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 a condition in the role's trust policy that checks for the instance's tag using the aws:ResourceTag condition key.

Option D is correct because IAM role trust policies can use the aws:ResourceTag condition key to restrict which EC2 instances (based on their tags) can assume the role. Option A is wrong because tags are not automatically included in the session; the trust policy must explicitly check tags. Option B is wrong because SCPs apply to accounts, not instances. Option C is wrong because instance profiles cannot be modified to check tags.

Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.

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 a new IAM role for each instance and attach the tag.

    Why it's wrong here

    This is not scalable and does not enforce the tag requirement.

  • Use a service control policy (SCP) to deny the ec2:AssumeRole action for instances without the required tag.

    Why it's wrong here

    SCPs apply to accounts, not to EC2 instances.

  • Modify the instance profile to include the tag requirement.

    Why it's wrong here

    Instance profiles do not support tag-based conditions.

  • Add a condition in the role's trust policy that checks for the instance's tag using the aws:ResourceTag condition key.

    Why this is correct

    The trust policy can evaluate the instance's tags at the time of AssumeRole.

    Related concept

    Standard ACLs match source addresses.

Common exam traps

Common exam trap: ACLs stop at the first match

ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.

Detailed technical explanation

How to think about this question

ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.

KKey Concepts to Remember

  • Standard ACLs match source addresses.
  • Extended ACLs can match source, destination, protocol and ports.
  • The first matching ACL entry is used.
  • There is usually an implicit deny at the end.

TExam Day Tips

  • Check inbound versus outbound direction.
  • Read the ACL from top to bottom.
  • Look for a broader permit or deny above the intended line.

Key takeaway

ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.

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.

Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SOA-C02 ACL questions on filtering logic and placement.

Related practice questions

Related SOA-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SOA-C02 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 SOA-C02 question test?

Security and Compliance — This question tests Security and Compliance — Standard ACLs match source addresses..

What is the correct answer to this question?

The correct answer is: Add a condition in the role's trust policy that checks for the instance's tag using the aws:ResourceTag condition key. — Option D is correct because IAM role trust policies can use the aws:ResourceTag condition key to restrict which EC2 instances (based on their tags) can assume the role. Option A is wrong because tags are not automatically included in the session; the trust policy must explicitly check tags. Option B is wrong because SCPs apply to accounts, not instances. Option C is wrong because instance profiles cannot be modified to check tags.

What should I do if I get this SOA-C02 question wrong?

Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SOA-C02 ACL questions on filtering logic and placement.

What is the key concept behind this question?

Standard ACLs match source addresses.

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 20, 2026

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.

Loading comments…

Sign in to join the discussion.

This SOA-C02 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 SOA-C02 exam.