What is the primary purpose of Attribute-Based Access Control (ABAC) in Adobe RT-CDP?

Question

Options

• ARestricting data access based on user roles.
• BAssigning data access based on specific attributes of the data.
• CAutomating identity resolution processes.
• DEnabling batch processing for customer profiles.

• A
  13% (7)
• B
  76% (42)
• C
  4% (2)
• D
  7% (4)

Explanation

ABAC (Attribute-Based Access Control) grants or restricts access to data based on attributes - labels or tags applied to the data itself (e.g., "contains PII," "region: EU," "sensitivity: high") - which is exactly what option B describes. In Adobe RT-CDP, this lets organizations enforce fine-grained data governance by controlling who can see or use specific data fields based on those labels, not just their role.

Why the distractors are wrong:

• A describes Role-Based Access Control (RBAC), a related but distinct concept - roles define who someone is, while attributes define what the data is.
• C (identity resolution) is an entirely separate capability in RT-CDP that stitches together identity fragments across devices and channels.
• D (batch processing) refers to data ingestion/processing methodology, unrelated to access control.

Memory tip: Think of ABAC as "access based on data's Adjectives" - you tag data with descriptive labels (sensitive, restricted, GDPR-scoped), then policies use those adjectives to allow or deny access, regardless of job title.

No community discussion yet for this question.