Explanation:

The question tests how to control the payload of related attributes sent during activation from Salesforce Data Cloud to external targets like Marketing Cloud. It highlights a scenario where a profile segment functions correctly, but unconstrained 1-to-many relationship paths cause extraneous historical engagement records to bypass the segment’s timeline intent.

✅ Correct Option:

C. Apply a 30-day date filter on the Sales Order DMO within the activation.
When a segment is built on the Individual profile grain, its criteria only determine which customers qualify. When including related 1-to-many child attributes (like Sales Orders) in the activation payload, Data Cloud pulls all historical records for those individuals by default unless an explicit activation filter is applied to that specific related object to restrict the output.

❌ Incorrect options:

A. Filter out older orders in Marketing Cloud after activation.
Filtering data after it reaches Marketing Cloud shifts data volume and processing overhead to the downstream system instead of keeping it source-governed. This creates unnecessary processing strain, delays journeys, and creates compliance and synchronization issues by moving unnecessary historical records out of Data Cloud.

B. Apply a data space filter to exclude orders older than 30 days.
Data space filters are global boundary controls used to govern permissions and partition data visibility for entire business units or brands. They are completely static and are not intended to dynamically restrict rolling time-based transactional windows for individual marketing campaign activation payloads.

D. Build a segment using the Sales Order DMO and filter orders to the last 30 days.
Changing the segmentation entity to the Sales Order DMO shifts the entire core grain from a profile audience to a transactional audience. While it limits orders, it changes the segmentation structure entirely and fails to natively resolve the issue of constraining related payload attributes on a profile-based activation.

🔧 Reference:
→ See Considerations for Selecting Related Attributes in Data 360 Activations which explains how activation filters constrain the records exported for 1-to-many related data model objects.

Explanation:

The question asks for a Data 360 feature that helps users identify and select text attributes from a picklist of options. Value suggestion enables a drop‑down list of possible values for text fields directly inside the segment builder, so users do not have to type or remember exact values. This improves data quality and reduces errors.

✅ Correct Option: B. Value suggestion
Value suggestion can be enabled on a text field of a Data Model Object (DMO) by checking the “Enable Value Suggestion” box during field creation. When a user later builds a segment filter on that attribute, they see a picklist of existing values and can simply click to select the correct one. This feature ensures consistent and valid inputs without manual typing.

❌ Incorrect Option: A. Data harmonization
Data harmonization is the process of mapping fields from Data Lake Objects (DLOs) to Data Model Objects (DMOs) so that data from different sources can be unified. It does not provide any user‑facing picklist or selection capability for text attributes.

❌ Incorrect Option: C. Transformation formulas
Transformation formulas are used during data ingestion to standardize, derive, or modify field values (e.g., concatenating names or formatting dates). They run behind the scenes and do not offer an interactive picklist for users creating segments.

❌ Incorrect Option: D. Global picklists
Global picklists are a Salesforce Core metadata feature that allows the same set of picklist values to be reused across different objects in Sales or Service Cloud. Data 360 does not have a “global picklist” feature; value suggestion is the correct equivalent for segmentation.

🔧 Reference:
→ Trailhead: Create Fields and Map Your Data – Confirms the existence of the “Enable Value Suggestion” checkbox when creating a text field on a Data Model Object.

Explanation:

This question tests understanding of Calculated Insights and identity-based joins in Salesforce Data 360 (Data Cloud). To calculate metrics such as Unified Individual Lifetime Value (LTV), the system must connect unified customer profiles with transactional data across multiple source records.

Because transactions are typically linked to source-level Individual records, the calculation must traverse the identity resolution layer to connect unified profiles with related sales activity.

🟢 Correct Option:

D. Unified Individual > Unified Link Individual > Sales Order
This is the correct join path because Unified Individuals represent the resolved customer profile created through identity resolution. The Unified Link Individual object acts as the bridge between the unified profile and the source-level Individual records tied to transactional objects like Sales Orders. Using this sequence allows calculated insights to aggregate all purchases associated with linked profiles, producing an accurate unified customer lifetime value metric across systems and channels.

🔴 Incorrect Options:

A. Sales Order > Unified Individual
Sales Orders are not directly linked to Unified Individuals. A bridging relationship through identity resolution objects is required to connect transactional records to unified customer profiles.

B. Unified Individual > Individual > Sales Order
This path skips the Unified Link Individual relationship object, which is required to correctly map resolved profiles to their linked source records.

C. Sales Order > Individual > Unified Individual
Although this path references related objects, it does not reflect the proper identity resolution relationship structure used in Data 360 calculated insights.

🔧 Reference:
→ Salesforce Data Cloud Identity Resolution Data Model
Explains how Unified Individual and Unified Link Individual objects connect source records to unified profiles.

→ Salesforce Data Cloud Calculated Insights Documentation
Describes how calculated insights aggregate transactional data across unified customer profiles using DMO relationships.

Explanation:

This question tests the consultant's understanding of how calculated insights are structured to work with different data model objects in Data 360. The segmentation canvas allows filtering on attributes from both Individual (source) and Unified Individual (after identity resolution) DMOs. For a calculated insight to appear when segmenting on Unified Individual, the insight's SQL must include a proper relationship—typically via the Individual Identity Link DMO (bridge table)—that connects the insight's source data to the Unified Individual DMO . Without this relationship, the insight remains visible only for the source Individual DMO.

✅ Correct Option: B. The calculated insight is missing a relationship to the Unified Individual data model object (DMO).
Calculated insights appear in the segmentation canvas for a DMO only when the insight has a direct or join-based relationship to that DMO. If an insight is visible when segmenting on Individual but not Unified Individual, it means the insight's SQL query joins to the Individual DMO but not to the Unified Individual DMO. To make it available for Unified Individual, the consultant must add a join through the Individual Identity Link DMO (bridge table), which maps source Individual IDs to Unified Individual IDs . This join enables the system to associate aggregated metrics with unified profiles.

❌ Incorrect Option: A. The consultant doesn't have the correct permissions to see the calculated insight for Unified Individual segments.
Permission sets control access to Data 360 features but do not selectively show or hide an insight based on whether the segmentation canvas is targeting Individual versus Unified Individual. If the consultant can see the insight for Individual segmentation, permissions are correctly configured. This is a data relationship issue, not a security issue.

❌ Incorrect Option: C. The data space for the Unified Individual is different than the Individual data model object (DMO).
Both Individual and Unified Individual DMOs reside within the same data space. Data spaces are logical partitions for segregating data by business unit or compliance requirements, but they do not separate Individual from Unified Individual objects. Changing data spaces would hide the insight entirely, not make it visible for one DMO but not the other.

❌ Incorrect Option: D. Calculated insights can't be used for the Unified Individual data model object (DMO).
This statement is false. Calculated insights are commonly created for Unified Individual DMOs to power segmentation with metrics like Customer Lifetime Value, email open counts, and purchase insights . Official Salesforce documentation and examples explicitly demonstrate creating calculated insights that join to the Unified Individual DMO via the Identity Link bridge table .

🔧 Reference:
→ Trailhead: Create Insights with the Insights Builder – Confirms that to use a calculated insight with unified profiles, you must first connect your Unified Individual DMO to the Individual Identity Link DMO (bridge table) before joining with other DMOs, because engagement data contains Individual IDs, not Unified Individual IDs.

Explanation:
The critical requirement is to avoid blending family members into a single unified profile while still connecting their engagement data. Family members may share contact points like address or phone, but they have distinct financial preferences and goals. Therefore, the match rule must require both an individual attribute (such as name or a unique identifier) AND a contact point attribute to confirm a match, preventing shared household contact points from incorrectly merging distinct individuals.

Correct Option:

C. Include a match rule that incorporates match on individual and contact point attributes.
This approach creates a compound match condition where records only unify if BOTH an individual-specific attribute AND a contact point match. For example, a rule requiring "Exact First Name AND Exact Normalized Email" ensures that even if two family members share an address, they won't merge unless their names also align. This balances the need to link engagement records while respecting the firm's requirement to maintain separate client profiles for personalized financial advice .

Incorrect Option:

A. Use multiple contact points without individual attributes in the match rules.
This strategy relies solely on shared contact points (like address or phone) to match records, which would incorrectly blend all family members at the same address into one unified profile. This directly violates the firm's requirement to avoid merging individual family profiles .

B. Configure a single match rule with a single connected contact point based on address.
Matching solely on address is the most dangerous option for this use case. All family members sharing a residence would be merged into a single profile, destroying the ability to deliver personalized financial advice based on distinct investment preferences and goals .

D. Configure a single match rule based on contact phone number.
While more specific than address, phone numbers can still be shared among household members (especially landlines or family plans). This rule alone would merge family members who share a phone number, again failing to maintain separate client profiles .

Reference:
Salesforce Help: Identity Resolution Match Rules; Trailhead: Create Effective Identity Resolution Rulesets for Data 360; Salesforce Data 360 Identity Resolution Best Practices.