Exam Data-Cloud-Consultant Topic 1 Question 52 Discussion
Actual exam question for Salesforce's Data-Cloud-Consultant exam
Question #: 52
Topic #: 1
Question #: 52
Topic #: 1
Northern Trail Outfitters (NTO) wants to create a segment where a unique record is created in the published audience for every transaction a customer completes. If a customer makes three separate purchases, the resulting segment should contain three distinct entries for that customer to allow for transaction- specific messaging. All transactions are mapped to the Sales Order data model object (DMO), and NTO is using Identity Resolution to unify customers on the Unified Individual DMO. Which configuration should a Data
360 Consultant use to meet this requirement?
360 Consultant use to meet this requirement?
Suggested Answer: C Vote an answer
The identity logic is about linking source profiles safely, then choosing the best surviving values for the unified profile. Segment on the Sales Order DMO is appropriate because identity resolution needs reliable match inputs, qualified identifiers, and controlled reconciliation. It is not just deduplication; it is a rules-driven process that connects source records into a trusted unified profile. The distractors fall short because they either move the problem into the wrong system, add needless duplication, ignore Data 360 object relationships, or rely on a feature built for a different lifecycle stage. In a real implementation, those choices usually create brittle pipelines, stale data, security exposure, or segments that look correct on paper but fail when activated. Thinking like an architect, the selected option places the logic where Data 360 can govern it and reuse it reliably. This is the nuance exam questions often test: the platform capability must match both the technical layer and the business timing requirement, not just sound related to data.
by Baird at Jun 01, 2026, 08:03 AM
0
0
0
10
Comments
adrian.armijos
2026-06-08 19:52:01D. Segment on the Unified Individual DMO
In Data 360, segments must be built on the Unified Individual DMO (the segmentation population is always Unified Individual or another consumer-grain DMO like Unified Account). You cannot directly segment on a transactional DMO like Sales Order as the population.
To meet NTO's requirement of one published audience entry per transaction, the consultant segments on the Unified Individual DMO and then configures the activation with the Sales Order DMO as a related attribute / activation object. This produces a published audience that is "exploded" to transaction grain — one row per Sales Order — while still anchoring each row to the unified customer for personalization.
Here's why the others don't fit:
A. Segment on the Individual DMO — The Individual DMO holds source-level (un-unified) records. Segmentation should be done on the Unified Individual after identity resolution, not the raw Individual DMO.
B. Segment on a calculated insight based on Sales Orders — Calculated insights aggregate transactions into summary metrics per customer, which collapses the per-transaction grain NTO needs.
C. Segment on the Sales Order DMO — Sales Order is a transactional/related DMO, not a valid segmentation population in Data 360. Segments are anchored to the Unified Individual; Sales Order is referenced via related attributes on the activation.
The mechanism that delivers the per-transaction output is the activation configuration — selecting Sales Order as a related object causes the published audience to contain one row per matching Sales Order, while the segment itself remains anchored to the Unified Individual DMO.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).