A retail company uses Adobe RT-CDP to manage customer data across multiple regions. To comply with local regulations, they must restrict data activation based on geographic location. What governance f

Question

Options

• ARole-based access control to limit user access.
• BData Usage Labeling and Enforcement (DULE) policies tied to geographic data attributes.
• CStatic segmentation based on user preferences.
• DBatch activation workflows for regional data.

• A
  3% (2)
• B
  74% (43)
• C
  7% (4)
• D
  16% (9)

Explanation

DULE policies (Option B) are the correct governance mechanism because they allow organizations to attach usage labels directly to data fields (such as a "region" or "country" attribute) and then enforce policies that automatically block or allow data activation based on those labels - precisely matching the requirement to restrict activation by geographic location.

Option A (RBAC) controls who can access the platform, not how data can be used or where it can be sent, so it doesn't address geographic data activation restrictions.

Option C (Static segmentation) is a targeting strategy for grouping users, not a compliance enforcement mechanism - it has no policy enforcement capability.

Option D (Batch activation) describes a delivery method, not a governance control; it says nothing about whether data is permitted to flow to a given region.

Memory tip: Think of DULE as a "label and lock" system - you label data with attributes (e.g., geo:EU) and then lock its use with policies (e.g., "do not activate outside EU"). Whenever you see "data governance + geographic restriction" in a question, DULE is almost always the answer.

No community discussion yet for this question.