What is the main goal of role-based access control (RBAC) in Adobe RT-CDP?

Question

Options

• ATo automate profile updates.
• BTo assign specific data access permissions based on user roles.
• CTo enforce deterministic identity resolution.
• DTo create static audience segments.

• A
  4% (2)
• B
  84% (38)
• C
  2% (1)
• D
  9% (4)

Explanation

Role-Based Access Control (RBAC) exists precisely to grant or restrict data access based on what a user's job function requires - option B captures this perfectly, as RBAC in Adobe Real-Time CDP lets administrators assign permissions (e.g., which sandboxes, schemas, or datasets a user can view or edit) tied to defined roles like "data engineer" or "marketing analyst."

Why the distractors are wrong:

• A (automate profile updates) - Profile updates are driven by data ingestion and merge policies, not by access control mechanisms.
• C (enforce deterministic identity resolution) - Identity resolution (stitching identities using deterministic or probabilistic methods) is a separate capability handled by the identity graph, not RBAC.
• D (create static audience segments) - Audience/segment creation is a segmentation feature; RBAC controls who can access those segments, not how they're built.

Memory tip: Think of RBAC as a "bouncer with a job title list" - it doesn't change the data or build audiences, it just decides who gets through the door based on their role.

No community discussion yet for this question.