DOP-C02 Practice Question 77: ABAC Principal Resource Tag Matching
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 8 · question 7 of 10
A platform team onboards a new project team roughly every week. Each project gets its own set of EC2 instances, and every engineer assigned to a project must be able to start, stop, and reboot only that project's instances, never another project's. The security team refuses to hand-maintain a growing list of resource ARNs in IAM policies as projects come and go, and wants one static policy that scales automatically as new projects and engineers are added.
Which design satisfies this?
Show answer and explanation
Answer:
This is attribute-based access control: a single policy grants the EC2 start, stop, and reboot actions whenever the calling principal's project tag matches the target instance's project tag, using aws:PrincipalTag/project and aws:ResourceTag/project in a Condition element. The policy itself never changes; onboarding a new project is just tagging its instances and its engineers' roles consistently, which is exactly the "one static policy that scales" requirement.
Option A is the resource-ARN-listing approach the security team explicitly rejected; a new managed policy (or an edit to an existing one) is required for every new project, and every engineer addition still needs an attachment.
Option C grants broad, account-wide EC2 permissions with no isolation between projects at all; any engineer in the group could act on any instance, not just their own project's.
Option D describes permissions boundaries backwards: a boundary only caps the maximum permissions a role's own policies can grant, it does not itself grant per-project access, and this design still needs a per-project policy to name the actual instances, which is the unscalable approach being avoided.
Reference: IAM tutorial: Define permissions to access AWS resources based on tags