AD0-E605 · Question #33
A customer is looking to implement the Adobe Real-Time CDP (RTCDP) platform and has a number of customers who have agreed to have their data collected for personalization, but have opted out to have t
The correct answer is B. Create a profile-enabled dataset based upon a schema which contains a privacy and consent field. Option B is correct because Adobe RTCDP compliance with data collection and consent policies requires that the underlying XDM schema includes a Privacy and Consent field group - this is the architectural foundation that allows RTCDP to enforce consent at the data model level, ens
Question
A customer is looking to implement the Adobe Real-Time CDP (RTCDP) platform and has a number of customers who have agreed to have their data collected for personalization, but have opted out to have their data shared with a third party. How should the data engineer create the related objects to be compliant with the Adobe RTCDP data collection policy?
Options
- ACreate a profile-enabled dataset and use data collection to stream data into advertising details
- BCreate a profile-enabled dataset based upon a schema which contains a privacy and consent field
- CCreate a profile-enabled dataset and configure the Opt-in privacy preference using Adobe Data
- DCreate a dataset without a privacy and consent field group and use manual policies for compliance
How the community answered
(37 responses)- A5% (2)
- B78% (29)
- C14% (5)
- D3% (1)
Explanation
Option B is correct because Adobe RTCDP compliance with data collection and consent policies requires that the underlying XDM schema includes a Privacy and Consent field group - this is the architectural foundation that allows RTCDP to enforce consent at the data model level, ensuring opted-out sharing preferences are captured and respected natively within the platform.
Why the distractors are wrong:
- A is wrong because streaming data into advertising details serves ad-targeting purposes and completely ignores the consent/opt-out requirement - it would actually violate the stated policy.
- C is wrong because "Adobe Data" is not a recognized, specific RTCDP tool for configuring opt-in preferences; consent must be modeled at the schema level, not applied as a separate configuration layer after the fact.
- D is wrong because manually-applied policies cannot substitute for the required schema structure - omitting the Privacy and Consent field group means consent signals have no standardized place to live, making automated enforcement unreliable.
Memory tip: Think "Schema First, Compliance Always" - in RTCDP, privacy compliance is baked into the data model (schema + field group), not bolted on afterward. If a question involves consent/opt-out, the answer almost always involves the Privacy and Consent field group at the schema level.
Topics
Community Discussion
No community discussion yet for this question.