AD0-E605 · Question #47
A company has completed their implementation of Adobe Experience Platform (AEP) and is successfully onboarding data and profiles. The company's data steward is reviewing the license dashboard and noti
The correct answer is D. Data Lifecycle E. Experience Event expiration (TTL). Data Lifecycle (D) and Experience Event expiration/TTL (E) are the two correct mechanisms because both actively remove data from the Profile Store for profiles that have already been onboarded. Data Lifecycle enables record-level deletes and pseudonymous profile expiration, direc
Question
A company has completed their implementation of Adobe Experience Platform (AEP) and is successfully onboarding data and profiles. The company's data steward is reviewing the license dashboard and notices that Addressable Audience is significantly exceeding the license amount. The data steward must take steps to keep Addressable Audience in line with the license amount. Which two mechanisms are available for the data steward to reduce the size of Addressable Audience in AEP for profiles that have already been onboarded? (Choose two.)
Options
- AData Distiller
- BPrivacy Service
- CDisable Datasets for Profile
- DData Lifecycle
- EExperience Event expiration (TTL)
How the community answered
(42 responses)- A5% (2)
- B14% (6)
- C7% (3)
- D74% (31)
Explanation
Data Lifecycle (D) and Experience Event expiration/TTL (E) are the two correct mechanisms because both actively remove data from the Profile Store for profiles that have already been onboarded. Data Lifecycle enables record-level deletes and pseudonymous profile expiration, directly eliminating profiles from the Addressable Audience count. Experience Event TTL automatically purges event data after a set period, which can collapse profiles - particularly pseudonymous ones - that no longer have qualifying data to remain active in the store.
Why the distractors are wrong:
- A (Data Distiller) is a query/analytics add-on for running SQL against AEP data; it has no mechanism to delete profiles or reduce license consumption.
- B (Privacy Service) handles individual GDPR/CCPA erasure requests - it's a compliance tool for data subject rights, not a bulk license management tool.
- C (Disable Datasets for Profile) only stops future ingestion from a dataset; it does nothing to remove profiles already in the store, making it useless for the scenario described.
Memory tip: Think "D & E = Delete & Expire." Data Lifecycle lets you Delete records now; Experience Event TTL lets data Expire over time. Everything else either queries (Distiller), blocks future intake (Disable Datasets), or handles individual privacy rights (Privacy Service) - none of which shrinks what's already in your Profile Store.
Topics
Community Discussion
No community discussion yet for this question.