AD0-E605: Adobe Real-Time Customer Data Platform Developer Expert

By Adobe · Question Mode

QuestionQ48

Data Architecture

An Adobe Experience Platform data engineer receives a data model from an existing customer relationship management (CRM) system. The model contains various entities, including Customers, Orders, and Products. The Orders entity has a productID field that is a foreign key to the Products table. It has been decided that product information will not be loaded into Adobe Experience Platform; only the productID will be used, and any product details will be retrieved from a separate API when needed.

The data engineer must now determine the best approach for creating the Experience Data Model (XDM) schema for Real-Time Customer Profile in Adobe Experience Platform.

What is an appropriate and effective strategy for modeling this data in Adobe Experience Platform, given that only product IDs will be ingested and actual product details will be obtained through a separate API if needed?

Explanation

When product attributes are not ingested, the Orders schema should store productID as the identifier needed to reference the external product. Creating a separate product schema is unnecessary without product data to populate it, and Adobe Experience Platform does not automatically retrieve external API product details. Adobe’s XDM documentation describes schemas as defining the structure of data that is ingested, while schema relationships reference another schema only when that referenced entity is modeled in Platform.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!