What is a key best practice for applying data governance in Adobe RT-CDP?

Question

Options

• ALabel all datasets with appropriate usage tags during ingestion.
• BAvoid mapping data to identity fields.
• CDisable profile updates in real-time workflows.
• DRestrict all data to static batch exports.

• A
  71% (17)
• B
  4% (1)
• C
  8% (2)
• D
  17% (4)

Explanation

Labeling datasets with appropriate usage tags during ingestion (A) is the foundation of data governance in Adobe RT-CDP because it enforces policy controls at the data layer - tags drive downstream enforcement of data usage policies, consent rules, and regulatory restrictions (e.g., GDPR, CCPA) across segments and activations. Option B is wrong because mapping data to identity fields is essential for profile unification and identity resolution, which are core RT-CDP functions. Option C is wrong because real-time profile updates are a primary value proposition of RT-CDP - disabling them defeats its purpose. Option D is wrong because RT-CDP is explicitly designed for real-time activation to streaming destinations, not static batch-only exports.

Memory tip: Think "tag it before you bag it" - data must be labeled at ingestion so governance policies can travel with the data everywhere it goes.

No community discussion yet for this question.