A healthcare organization using Adobe RT-CDP must ensure that sensitive patient data is not activated to marketing platforms. How should they enforce this requirement?

Question

Options

• AApply "Restricted Data" labels to sensitive datasets and configure DULE policies to block
• BAvoid activating any data to external destinations.
• CUse deterministic identity stitching for all datasets.
• DCreate a static segment of patients and manually approve each activation.

• A
  74% (28)
• B
  3% (1)
• C
  16% (6)
• D
  8% (3)

Explanation

Option A is correct because Adobe RT-CDP uses Data Usage Labeling and Enforcement (DULE) as its governance framework - you apply data usage labels (like "Restricted Data" or "RHD" for regulated health data) directly to datasets or fields, then define marketing action policies that block activation when those labels are present, creating automated, scalable enforcement without manual intervention.

Why the distractors fail:

• B is impractical and defeats the purpose of a CDP - blocking all external activations is a business dead-end, not a governance strategy.
• C (deterministic identity stitching) is an identity resolution technique, not a data restriction mechanism; it has no bearing on whether data can be sent to a destination.
• D (manual approval per activation) is operationally unsustainable at scale and is not a built-in RT-CDP enforcement feature - it introduces human error where policy automation should exist.

Memory tip: Think "Label it, Policy it, Block it" - DULE is a label-first system. If you label the data and write the policy, RT-CDP refuses the activation automatically. Any answer involving manual work or blanket restrictions misses RT-CDP's automated governance design.

No community discussion yet for this question.