CRT-250 practice question 10 of 25
A customer has an eCommerce site and imports data into three data extensions daily: Orders, Order_Details, and 'Products. The data extensions contain…
Full set: 165 questionsThe goal in Data Designer is to model the relationships between different data sources to build a comprehensive view of the contact.
(B) An Order can contain multiple line items (e.g., a customer orders a shirt, pants, and shoes in a single transaction). Therefore, one record in the Orders data extension can relate to multiple records in the OrderDetails data extension. This is a classic one-to-many relationship, linked by the OrderID.
(D) Each record in the OrderDetails data extension represents a single line item, which corresponds to exactly one product in the Products data extension. This establishes a lookup relationship from an order line item to its product definition. While the overall cardinality from Products to OrderDetails is one-to-many, the relationship from a specific OrderDetails record to a Products record is singular. In this context, the option describes this lookup characteristic.
A. Create a one-to-one relationship between the contact record and Order Details. A contact can place multiple orders, resulting in many order detail records. Therefore, the relationship is one-to-many, not one-to-one.
C. Create a one-to-one relationship between Orders and OrderDetails. This is incorrect as it would imply an order can only ever contain a single product or line item, which contradicts a standard eCommerce model.
1. Salesforce Help Documentation, "Data Designer": This document outlines the purpose of Data Designer, which is to "define information about your contacts and how different data extensions relate to each other." The scenario described is a primary use case for linking related data extensions to the contact model. (Salesforce Help, Doc ID: mccodatadesigner.html)
2. Salesforce Help Documentation, "Link Data Extensions": This guide explains how to create relationships between data extensions in Contact Builder. It specifies the need to define cardinality, such as one-to-one or one-to-many. The relationship between Orders and OrderDetails is a clear example of a one-to-many relationship. (Salesforce Help, Doc ID: mccolinkdataextensions.html, Section: "Create a Data Extension Relationship")
3. Salesforce Help Documentation, "Attribute Groups": This document explains that attribute groups are collections of data extensions linked together and to the contact model. The eCommerce data (Orders, OrderDetails, Products) would form a logical attribute group, with relationships defined between the data extensions as described in the correct answers. (Salesforce Help, Doc ID: mccocreateattributegroups.html)
Keep practicing
Take the free CRT-250 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other CRT-250 practice questions
- Question 1Marketing Cloud admin is asked to determine the total number of emails sent across all of…
- Question 2Which activity should be used for multivariate content testing within Journey Builder?
- Question 3What does Marketing Cloud authenticate when a user logs in through the user interface?
- Question 4Northern Trail Outfitters (NTO) wants to limit who can receive Marketing Cloud tracking d…
- Question 5What elements of CAN-SPAM should the Marketing Cloud admin ensure are present for each Co…
- Question 6Northern Trail Outfitters has noticed an issue with their sends today. Which two links in…
