An administrator of a multinational corporation is configuring attribute-based access control (ABAC) within Adobe RTCDP for the purpose of…

Attribute-Based Access Control (ABAC) in Adobe Experience Platform operates on a two-step principle. First, you must define and apply labels to specific schema fields (attributes) that you want to control, such as "geographical locations" and "departments." Second, you create an access control policy that incorporates these labels and assigns permissions to user roles. This policy dictates that users in a specific role can only access data where the labeled attributes match the policy's criteria.

B. Including all attributes in every policy is unnecessary and inefficient. Policies should only contain the specific labeled attributes required for control.

C. Labels are applied to schema fields (data), not directly to user roles. Roles are granted permissions through policies that reference these labels.

1. Adobe Experience Platform Documentation. (2023). Attribute-based access control overview. Adobe Experience League. See the "End-to-end workflow" diagram and description, which outlines the process: "Label your schema fields," "Create a role," and "Create an access policy."

2. Adobe Experience Platform Documentation. (2023). Attribute-based access control end-to-end guide. Adobe Experience League. See "Step 2: Label your schema fields" and "Step 4: Create an access policy."