A leading clothing retail company is in the process of migrating from a relational database management system (RDBMS) to Adobe's Real-Time CDR Currently, their RDBMS includes tables for Customers, Orders, and Items with appropriate relationships. The customer table includes customer profiles, the order table details the orders made by the customers, and the items table holds information about the items purchased.The Adobe Real-Time CDP uses Experience Data Model (XDM), a standard schema model that allows users to combine, capture, and process customer data. The aim is to integrate the current RDBMS data into the Adobe Real-Time CDP's XDM schema while maintaining the integrity and relationship of the data.What is the most efficient way to structure the RDBMS data into Adobe Real-Time CDP's XDM data model?
Answer(s): C
The most efficient strategy is to create separate XDM schemas for each table (Customers, Orders, and Items) and define relationships using identifier fields. This approach preserves the relational integrity of the originalRDBMS within Adobe Real-Time CDP's XDM model, while enabling flexible linkage through unique identifiers such as customer ID and order ID. It ensures accurate profile stitching and maintains scalability in the NoSQL environment.
An Adobe Experience Platform data engineer has been given a data model from an existing customer relationship management (CRM) system. The data model includes various entities such as Customers, Orders, and Products. The Orders entity includes a productID field which is a foreign key to the Products table. It has been decided that the product information will not be loaded into the Adobe Experience Platform, only the productID will be used and any product detail will be obtained from a separate API if needed.The data engineer must now consider the best way to create the Experience Data Model (XDM) schema for the Real-Time Customer Profile in Adobe Experience Platform.What is a proper and effective strategy to model this data in Adobe Experience Platform considering that only product IDs will be ingested and actual product details will be obtained via separate API if needed?
Answer(s): B
The most effective strategy is to include the productID field in the Orders schema and not model the Products schema. Since product details will not be ingested into Adobe Experience Platform and will instead be retrieved from an external API, there is no need to maintain a Products schema. Storing only the productID in the Orders schema maintains the link while avoiding unnecessary schema complexity.
A healthcare organization uses a Relational Database Management System (RDBMS) to store information about patients' medical histories. The data is organized into two main tables: "Patients", which stores data on individual patients, and "Visits", which stores data on each patient visit. Each row in the "Visits" table is linked to a row in the "Patients" table, forming a one-to-many relationship. The organization wants to migrate this data to Adobe Real-Time CDP to deliver personalized experiences to patients based on their medical histories and requires that preservation of the one-to-many relationship between patients and visits be maintained.Which data modeling approach should the organization adopt when translating this RDBMS data model to Real-Time CDP's NoSQL data model?
The correct approach is to store the "Patients" data in one XDM schema (Individual Profile) and the "Visits" data in a separate time-series schema (Experience Event), connecting them via a common identity such as patient ID. This preserves the one-to-many relationship between patients and visits while aligning with Adobe Real-Time CDP's best practice of keeping profile data persistent and event data time-series based.
Which two are required to define a one-to-one relationship between schemas? (Choose two.)
Answer(s): A,D
Both schemas must have defined primary identities using the same namespace: Required so the one-to-one mapping can be resolved accurately by Adobe Experience Platform.A dedicated relationship field must be added to a source schema: This field establishes the explicit link to the reference schema, enabling the one-to-one relationship.
A data engineer creates a custom identity namespace within Adobe Experience Platform. However, this custom Identity namespace is the wrong Identity type.What would the data engineer do to correct the situation?
Answer(s): D
Once a custom Identity Namespace is created in Adobe Experience Platform, its identity type cannot be modified. The correct approach is to create a new custom Identity Namespace with the correct identity type and then use it in the schema and data ingestion process.
Post your Comments and Discuss Adobe AD0-E605 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AD0-E605 content, but please register or login to continue.