A financial institution is implementing Adobe Real-Time CDP and has critical data coming from multiple sources, raising data security concerns. What…

The recommended feature to handle sensitive financial data is AEP's Data Governance framework, specifically using Data Usage Labels and Policies. The institution can apply predefined or custom labels (e.g., C4 - "Sensitive Personally Identifiable Information") to sensitive data fields within their schemas. Subsequently, they can create data usage policies that restrict how this labeled data can be used. For example, a policy can be created to prevent any data labeled as "Sensitive" from being exported to certain third-party marketing destinations, ensuring compliance and proper handling of critical customer information.

A. The Profile API is an interface for accessing profile data; it does not provide the governance controls needed to manage how sensitive data is used.

B. Query Service is an analytical tool for running SQL queries on AEP data. While it has access controls, it is not the primary feature for data governance.

D. A Privacy Request, managed by the Adobe Privacy Service, is for fulfilling consumer rights requests (e.g., data deletion), not for ongoing data handling policies.

1. Adobe Experience Platform Documentation, "Data Governance: Data usage labels overview". This guide details the standard labels, including C4 ("Sensitive Personally Identifiable Information") and C5 ("Financial Information"), which are directly applicable to the scenario.

2. Adobe Experience Platform Documentation, "Data Governance: Data usage policies overview". This document explains how policies are created to enforce rules based on data labels. It states, "Data usage policies are rules that describe the kinds of marketing actions that you are allowed to, or restricted from, performing on data in Adobe Experience Platform." This is the mechanism for ensuring proper handling.