The solution that provides an easy way to ingest Marketing Cloud subscriber profile attributes into Data Cloud on a daily basis is the Marketing Cloud Data extension Data Stream. The Marketing Cloud Data extension Data Stream is a feature that allows customers to stream data from Marketing Cloud data extensions to Data Cloud data spaces. Customers can select which data extensions they want to stream, and Data Cloud will automatically create and update the corresponding data model objects (DMOs) in the data space. Customers can also map the data extension fields to the DMO attributes using a user interface or an API. The Marketing Cloud Data extension Data Stream can help customers ingest subscriber profile attributes and other data from Marketing Cloud into Data Cloud without writing any code or setting up any complex integrations.

The other options are not solutions that provide an easy way to ingest Marketing Cloud subscriber profile attributes into Data Cloud on a daily basis. Automation Studio and Profile file API are tools that can be used to export data from Marketing Cloud to external systems, but they require customers to write scripts, configure file transfers, and schedule automations. Marketing Cloud Connect API is an API that can be used to access data from Marketing Cloud in other Salesforce solutions, such as Sales Cloud or Service Cloud, but it does not support streaming data to Data Cloud. Email Studio Starter Data Bundle is a data kit that contains sample data and segments for Email Studio, but it does not contain subscriber profile attributes or stream data to Data Cloud.

Marketing Cloud Data Extension Data Stream

Data Cloud Data Ingestion

[Marketing Cloud Data Extension Data Stream API]

[Marketing Cloud Connect API]

[Email Studio Starter Data Bundle]

 A Unified Individual is a profile that combines data from multiple sources using identity resolution rules in Data Cloud. A Unified Individual can have multiple contact points, such as email, phone, or address, that link to different systems and records. A consultant can use the following features to display all cases associated with a Unified Individual on a contact record:

Profile API: This is a REST API that allows you to retrieve and update Unified Individual profiles and related attributes in Data Cloud. You can use the Profile API to query the cases that are related to a Unified Individual by using the contact point ID or the unified ID as a filter. You can also use the Profile API to update the Unified Individual profile with new or modified case information from other systems.

Lightning Web Components: These are custom HTML elements that you can use to create reusable UI components for your Salesforce apps. You can use Lightning Web Components to create a custom component that displays the cases related to a Unified Individual on a contact record. You can use the Profile API to fetch the data from Data Cloud and display it in a table, list, or chart format. You can also use Lightning Web Components to enable actions, such as creating, editing, or deleting cases, from the contact record.

The other two options are not relevant for this use case. A Data Action is a type of action that executes a flow, a data action target, or a data action script when an insight is triggered. A Data Action is used for activation and personalization, not for displaying data on a contact record. A Query APL is a query language that allows you to access and manipulate data in Data Cloud. A Query APL is used for data exploration and analysis, not for displaying data on a contact record. References: Profile API Developer Guide, Lightning Web Components Developer Guide, Create Unified Individual Profiles Unit

To manage individual client profiles within family portfolios while avoiding blending profiles, the consultant should recommend a more restrictive design approach for identity resolution. Here’s why:

Understanding the Requirement

The financial services firm wants to maintain distinct profiles for individual family members despite shared contact points (e.g., address, phone number).

The goal is to avoid blending profiles to ensure personalized service and accurate financial advice.

Why a Restrictive Design Approach?

Avoiding Over-Matching :

A restrictive design approach ensures that match rules are narrowly defined to prevent over-matching (e.g., merging profiles based solely on shared addresses or phone numbers).

This preserves the uniqueness of individual profiles while still allowing for some shared attributes.

Custom Match Rules :

The consultant can configure custom match rules that prioritize unique identifiers (e.g., email, social security number) over shared contact points.

This ensures that family members with shared addresses or phone numbers remain distinct.

Other Options Are Less Suitable :

A. Configure a single match rule with a single connected contact point based on address : This would likely result in over-matching and blending profiles, which is undesirable.

B. Use multiple contact points without individual attributes in the match rules : This approach lacks the precision needed to maintain distinct profiles.

D. Configure a single match rule based on a custom identifier : While custom identifiers are useful, relying on a single rule may not account for all scenarios and could lead to over-matching.

Steps to Implement the Solution

Step 1: Analyze Shared Attributes

Identify shared attributes (e.g., address, phone number) and unique attributes (e.g., email, social security number).

Step 2: Define Restrictive Match Rules

Configure match rules that prioritize unique attributes and minimize reliance on shared contact points.

Step 3: Test Identity Resolution

Test the match rules to ensure that individual profiles are preserved while still allowing for some shared attributes.

Step 4: Monitor and Refine

Continuously monitor the results and refine the match rules as needed to achieve the desired outcome.

Conclusion

A more restrictive design approach ensures that match rules perform as desired, preserving the uniqueness of individual profiles while accommodating shared attributes within family portfolios.

When creating a segment on an individual, using two separate containers linked by an AND means that the individual must satisfy both the conditions in the containers. In this case, the individual must have purchased at least one product with the color attribute equal to ‘red’ and at least one product with the primary product category attribute equal to ‘shoes’. The products do not have to be the same or purchased in the same transaction. Therefore, the correct answer is A.

The other options are incorrect because they imply different logical operators or conditions. Option B implies that the individual must have purchased a single product that has both the color attribute equal to ‘red’ and the primary product category attribute equal to ‘shoes’. Option C implies that the individual must have purchased only one product that has both the color attribute equal to ‘red’ and the primary product category attribute equal to ‘shoes’ and no other products. Option D implies that the individual must have purchased either one product with the color attribute equal to ‘red’ or one product with the primary product category attribute equal to ‘shoes’ or both, which is equivalent to using an OR operator instead of an AND operator.

Create a Container for Segmentation

Create a Segment in Data Cloud

Navigate Data Cloud Segmentation

The Source Sequence reconciliation rule sets the priority of specific data sources when building attributes in a unified profile, such as a first or last name. This rule allows you to define which data source should be used as the primary source of truth for each attribute, and which data sources should be used as fallbacks in case the primary source is missing or invalid. For example, you can set the Source Sequence rule to use data from Salesforce CRM as the first priority, data from Marketing Cloud as the second priority, and data from Google Analytics as the third priority for the first name attribute. This way, the unified profile will use the first name value from Salesforce CRM if it exists, otherwise it will use the value from Marketing Cloud, and so on. This rule helps you to ensure the accuracy and consistency of the unified profile attributes across different data sources. References: Salesforce Data Cloud Consultant Exam Guide, Identity Resolution, Reconciliation Rules

Building a trust-based, first-party data asset means collecting, managing, and activating data from your own customers and prospects in a way that respects their privacy and preferences. It also means providing them with clear and honest information about how you use their data, what benefits they can expect from sharing their data, and how they can control their data. By doing so, you can create a mutually beneficial relationship with your customers, where they trust you to use their data responsibly and ethically, and you can deliver more relevant and personalized experiences to them. A trust-based, first-party data asset can help you improve customer loyalty, retention, and growth, as well as comply with data protection regulations and standards. References: Use first-party data for a powerful digital experience, Why first-party data is the key to data privacy, Build a first-party data strategy