Which mechanism defines explicit user permissions at the resource level?

Which mechanism defines explicit user permissions at the resource level?

• A. Security ACL
• B. Password Change Requests
• C. Default Membership
• D. IAM Program

Answer: (A)

Explicit control of what users can do with a specific resource is defined by an access control list. An ACL attaches to the resource and lists each user or group alongside the exact actions they’re permitted to perform (such as read, write, delete, or execute). This provides fine-grained, resource-level permissions that are easy to audit because you can see the rights granted to each principal right on that item. Other options don’t provide this per-resource granularity: password change requests relate to credential management rather than access rights on a resource; default membership sets baseline access for new users but isn’t about explicit rights on a particular resource; an IAM program is the overarching framework for managing identities and access across the organization, not the mechanism that defines explicit permissions at the resource level.

Explicit control of what users can do with a specific resource is defined by an access control list. An ACL attaches to the resource and lists each user or group alongside the exact actions they’re permitted to perform (such as read, write, delete, or execute). This provides fine-grained, resource-level permissions that are easy to audit because you can see the rights granted to each principal right on that item.

Other options don’t provide this per-resource granularity: password change requests relate to credential management rather than access rights on a resource; default membership sets baseline access for new users but isn’t about explicit rights on a particular resource; an IAM program is the overarching framework for managing identities and access across the organization, not the mechanism that defines explicit permissions at the resource level.