A company is transitioning from a Role-Based Access Control (RBAC) model to an Attribute-Based Access Control (ABAC) model to manage their growing AWS environment. Which TWO benefits does ABAC provide over a traditional RBAC approach?
In an ABAC model, policies are written to allow access based on matching tags between the user and the resource. This means that as long as new resources are tagged correctly upon creation, users with matching tags gain access immediately without any manual changes to IAM policies.
Why this answer
Option A is correct because ABAC policies evaluate resource tags (for example, aws:ResourceTag/Project) at request time, so when a new resource is created with the matching tags it is automatically covered by the existing policy without any policy modification. Option C is correct because a single IAM role can carry one attribute-driven policy that grants different permissions depending on the principal's and resource's tags, replacing the many narrowly scoped roles a comparable RBAC design would require. Option B is incorrect because SCPs are an AWS Organizations feature that restrict permissions in any account regardless of whether RBAC or ABAC is used, so they are not an ABAC-only benefit.
Option D is incorrect because cross-account access still relies on IAM trust policies in the role's trust relationship to allow the principal to assume the role, and ABAC does not remove that requirement. Option E is incorrect because MFA enforcement is handled through IAM policy conditions such as aws:MultiFactorAuthPresent and is available in both RBAC and ABAC models, not a unique ABAC capability.
Exam trap
The trap is confusing ABAC with other AWS features like SCPs or MFA. Candidates might think ABAC provides MFA or eliminates trust policies, but those are separate mechanisms. Also, they might overlook that ABAC still requires proper tagging.