Free Salesforce Data 360 Consultant Practice Test Questions

Explanation:

This question tests understanding of relationship cardinality in Salesforce Data Cloud when modeling DMOs. The scenario describes a classic parent-child relationship for car ownership.

✅ Correct Option:

C. Many-to-One (N:1)
When creating the relationship from the Vehicle DMO to the Individual DMO, the architect should select Many-to-One (N:1). This means many Vehicles can relate to one Individual (one person can own multiple cars), while one Vehicle can only relate to one Individual (one car has only one owner). This is implemented via a lookup field on the Vehicle DMO.

❌ Incorrect options:

A. One-to-One (1:1)
One-to-One would restrict each Vehicle to one Individual and each Individual to only one Vehicle. This violates the requirement that one individual can own multiple vehicles.

B. Many-to-Many (N:N)
Many-to-Many allows multiple Vehicles to relate to multiple Individuals (e.g., shared ownership). This is unnecessary and overly complex for the stated requirement of single ownership per vehicle.

D. One-to-Many (1:N)
One-to-Many from Vehicle to Individual would mean one Vehicle can link to many Individuals, which contradicts the rule that one vehicle has only one owner.

🔧 Reference:
→ Data Cloud Data Modeling – Relationships
Explains cardinality options (1:1, 1:N, N:1, N:N) when creating relationships between DMOs.

Explanation:

This question tests your understanding of data modeling extension patterns within Salesforce Data Cloud. It focuses on the recommended architectural approach when a source data stream consists primarily of standard transaction details alongside a single, unique business-specific field.

✅ Correct Option:

A. Map standard fields to the Sales Order DMO and add a custom attribute for the fee.
Salesforce best practices dictate using standard Data Model Objects (DMOs) whenever possible to leverage native platform relationships, pre-built query paths, and out-of-the-box segmentation features. When a standard DMO (like Sales Order) is missing a specific business attribute (like a Sustainability Packaging Fee), the correct approach is to extend that standard DMO by adding a custom field (attribute) to it. This preserves the core data model integrity while cleanly accommodating the unique business requirement.

❌ Incorrect options:

B. Map all fields to a new Custom DMO specifically created for NTO transactions.
Creating an entirely new custom DMO for a standard transaction process is an architectural anti-pattern. Doing so forces you to manually recreate all relationships, joins, and lookups to other core objects (like Individual or Product) that are already managed natively by the standard Sales Order DMO framework.

C. Use Sales Order DMO and map the packaging fee to the Order Description field.
Mapping specific financial or structured numeric data into a generic text placeholder field like "Order Description" breaks data integrity. It prevents marketers from performing mathematical operations, such as filtering or aggregating by the fee amount, within the segmentation and insights canvases.

D. Create a calculated model to derive the sustainability fee using a streaming data transform.
The prompt indicates that the Sustainability Packaging Fee is already an incoming field provided in the source transaction data stream. There is no need to derive or calculate it using a transform; it simply needs to be stored and mapped correctly upon ingestion.

🔧 Reference:
→ See Salesforce Help: Data Model Custom Fields which explains how extending standard data model objects with custom attributes is the ideal mechanism to capture business-specific data points.