What are key components of role-based access control in RT-CDP? (Select two.)

The correct answer is A. Assigning permissions based on user roles. C. Restricting access to sensitive datasets. Role-Based Access Control (RBAC) in RT-CDP is built on two pillars: assigning permissions to users based on their role (A) - such as admin, analyst, or marketer - and restricting which datasets those roles can access (C), particularly sensitive or regulated data. Together…

Data Governance and Privacy

Question

Options

AAssigning permissions based on user roles.
BConfiguring identity namespaces for profiles.
CRestricting access to sensitive datasets.
DAutomating data governance workflows.

How the community answered

(42 responses)

A
81% (34)
B
5% (2)
D
14% (6)

Explanation

Role-Based Access Control (RBAC) in RT-CDP is built on two pillars: assigning permissions to users based on their role (A) - such as admin, analyst, or marketer - and restricting which datasets those roles can access (C), particularly sensitive or regulated data. Together, these ensure that users only see and act on data appropriate to their function, which is the core definition of RBAC.

B is wrong because identity namespaces (e.g., email, CRM ID) govern how profiles are merged and identified - that's identity resolution, a separate concern from access control entirely.

D is wrong because automating governance workflows (like consent enforcement or data expiration) falls under Data Governance policies, not RBAC - it's a different system within RT-CDP.

Memory tip: Think of RBAC as two questions - "Who are you?" (your role → A) and "What can you touch?" (your data access → C). If an answer is about identity or automation rather than roles and restrictions, it's out of scope for RBAC.

Topics

#role-based access control#permissions#sensitive datasets#user roles

Community Discussion

No community discussion yet for this question.

Full AD0-E605 Practice