A company based out of California would like to delete profile data from the Adobe Experience Platform (AEP) profile store and data lake based on their customer request. They have reached out to a…

Question

Options

• ABuild a custom solution by leveraging the delete entity API to delete the profiles from both data
• BLeverage query service, create a query by excluding the profiles shared by customer, delete the
• CLeverage privacy service and submit the delete request under CCPA regulation type for a given
• DUse the Segment Export feature to delete the profiles from the dataset and profile store

• A
  3% (1)
• B
  3% (1)
• C
  84% (27)
• D
  9% (3)

Explanation

Option C is correct because a California customer deletion request falls under the California Consumer Privacy Act (CCPA), and Adobe's Privacy Service is the purpose-built, compliant mechanism for handling such requests - it orchestrates deletion across both the profile store and the data lake in a single, auditable workflow.

Why the distractors fail:

• A - The delete entity API only targets the profile store, not the data lake, so it's incomplete and creates compliance gaps for a CCPA request.
• B - Query Service is an analytics/query tool, not a deletion mechanism; rewriting a query to exclude profiles does not actually remove the underlying data, which is what CCPA mandates.
• D - Segment Export is designed to export audiences to destinations, not to delete data; it has no deletion capability against the profile store or data lake.

Memory tip: Think "California = CCPA = Privacy Service." Whenever a question involves a customer rights request (deletion, access, opt-out) tied to a regulation, Privacy Service is almost always the answer - it's Adobe's compliance layer that knows where to delete and ensures the deletion propagates everywhere.

No community discussion yet for this question.