AD0-E605 practice question 13 of 15

A large retail company is currently using a traditional relational database management system (RDBMS) to store and manage order data. However, the…

A large retail company is currently using a traditional relational database management system (RDBMS) to store and manage order data. However, the company is experiencing scalability and performance issues as the number of orders continues to grow. The company is considering loading to Adobe Real-Time CDP to take advantage of its Experience Data Model (XDM) data model and real- time data capabilities. The company's order table includes the following attributes: Order ID Customer ID Order date Order status Shipping address Billing address The company's order items table includes the following attributes: Order ID Item ID How would the architect translate this data model into Adobe Experience Platform XDM data model?

Answer options

A: Create a single XDM experience event schema Correct answer

B: Create an XDM individual profile schema

C: Create an XDM experience event schema and an XDM custom schema

D: Create an XDM individual profile schema and an XDM custom schema

Correct Answer:

A. Create a single XDM experience event schema

Explanation

An order is a transactional, point-in-time event and should be modeled using the XDM ExperienceEvent class. A single ExperienceEvent schema is sufficient and is the standard practice. This schema would use the "Commerce Details" and "Order" standard field groups, which provide predefined structures for order details. The productListItems array within this structure is specifically designed to capture the list of items in the order, effectively modeling the data from both the orders and orderitems RDBMS tables in one cohesive, standardized event schema. This approach is efficient and aligns with AEP's real-time capabilities.

Why Incorrect

B. An order is an event, not a persistent attribute of a person. Storing transactional data directly on the profile schema is inefficient and not the intended design pattern.
C. A separate custom schema is unnecessary. The standard XDM ExperienceEvent class with the Commerce Details field group is designed to handle both order headers and item details.
D. This is incorrect because an order is an event, not a profile attribute. Using a profile schema for transactional data is fundamentally the wrong approach in XDM.

References

1. Adobe Experience Platform Documentation. (2023). Commerce Details field group for XDM ExperienceEvent Class. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/xdm/field-groups/event/commerce.html. (This page details the commerce object and the productListItems array for modeling purchases).

2. Adobe Experience Platform Documentation. (2023). XDM ExperienceEvent Class. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/xdm/classes/experienceevent.html. (This document explains that the ExperienceEvent class is used to represent a snapshot of the system when an event occurs).

3. Adobe Experience Platform Documentation. (2023). Best practices for data modeling. Adobe Experience League. Retrieved from https://experienceleague.adobe.com/docs/experience-platform/xdm/schema/best-practices.html. (This guide emphasizes using appropriate classes for different types of data, such as ExperienceEvent for time-series data).

Keep practicing

Take the free AD0-E605 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test