A company wants to provide access to specific schema fields in a sandbox to various internal teams based on their functions. What is the primary…

Attribute-based access control (ABAC) in Adobe Experience Platform uses labels to categorize schema fields and other resources based on their sensitivity or organizational relevance. These labels are the primary attribute applied directly to objects. Administrators then create roles with specific permissions and define policies that link these roles and labels. This system allows for granular control, ensuring that users can only access the specific schema fields for which they have been granted permission via the labels applied to them.

B. "Access Profile" is not a standard ABAC component in AEP. Access is managed through roles assigned to product profiles in the Adobe Admin Console.

C. "Access Schema" is not a feature. Schemas are the objects to which access control labels are applied, not the control mechanism itself.

D. "Access Security" is a general term for the entire domain of security and is not a specific feature or attribute within AEP's ABAC framework.

1. Adobe Experience Platform Documentation. (2023). Attribute-based access control overview. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/overview.html. (See the "Attribute-based access control components" section, which lists "Labels" as a key component applied to objects like schema fields.)

2. Adobe Experience Platform Documentation. (2023). End-to-end attribute-based access control guide. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/access-control/abac/end-to-end-guide.html. (Step 2, "Add labels to your schema fields," explicitly demonstrates that labels are the attribute applied to schemas.)