What are use cases for Attribute-Based Access Control (ABAC) in Adobe RT-CDP? (Select two.)

Question

Options

• ALimiting access to sensitive data fields based on user roles.
• BGranting access to specific datasets based on data attributes like region or type.
• CAutomating batch workflows for segment creation.
• DRestricting static segmentation capabilities.

• A
  74% (25)
• C
  18% (6)
• D
  9% (3)

Explanation

A and B are correct because ABAC in Adobe RT-CDP is designed specifically to control who can access what data based on attributes - both user attributes (like roles, departments) and data attributes (like region, sensitivity labels, or data type). This makes it ideal for limiting access to sensitive fields (A) and restricting dataset access by data characteristics (B).

C is wrong because automating batch workflows for segment creation is a data engineering/workflow orchestration concern, not an access control function - ABAC governs permissions, not pipeline execution.

D is wrong because ABAC doesn't restrict segmentation capabilities as a feature - it controls access to underlying data, not the tools themselves.

Memory tip: Think of ABAC as a "tag-based bouncer" - it checks labels on both the person (role, department) and the data (region, sensitivity) before granting entry. Any answer involving automation or feature toggling is outside the bouncer's job description.

No community discussion yet for this question.