* Initial Data Load: For loading large volumes of historical data, such as the last 90 days of runner profiles and activity logs, bulk ingestion is the most efficient method. It allows for high-throughput data transfer.
Bulk Ingestion: Use Salesforce Data Cloud's bulk ingestion tools to load the historical data quickly and efficiently.
* Ongoing Data Synchronization: To keep the Data Cloud updated with new and modified records as they become available in the Track My Run mobile app, streaming ingestion is appropriate. It ensures near-real-time data updates.
Streaming Ingestion: Configure streaming ingestion to continuously update the Data Cloud with new and updated data from the mobile app.
* Sequence of Actions:
Step 1: Perform bulk ingestion to import the last 90 days of historical data into Data Cloud.
Step 2: Set up streaming ingestion to handle ongoing updates and new data as it becomes available.
* Best Practice: This approach ensures that the initial large data load is handled efficiently, and ongoing updates are processed in near real-time, providing the marketing department with the most up-to-date data.
* Reference:
Salesforce Data Cloud Ingestion Methods
Salesforce Bulk Data Ingestion
Salesforce Streaming Data Ingestion

The consolidation rate is the amount by which source profiles are combined to produce unified profiles, calculated as 1 - (number of unified individuals / number of source individuals). For example, if you ingest 100 source records and create 80 unified profiles, your consolidation rate is 20%. To increase the consolidation rate, you need to increase the number of matches between source profiles, which can be done by adding more match rules. Match rules define the criteria for matching source profiles based on their attributes. By increasing the number of match rules, you can increase the chances of finding matches between source profiles and thus increase the consolidation rate. On the other hand, changing reconciliation rules, including additional attributes, or reducing the number of match rules can decrease the consolidation rate, as they can either reduce the number of matches or increase the number of unified profiles. Reference: Identity Resolution Calculated Insight: Consolidation Rates for Unified Profiles, Identity Resolution Ruleset Processing Results, Configure Identity Resolution Rulesets

* Segmentation in Salesforce Data Cloud:
The Segment Canvas interface is used to define and adjust target populations for marketing campaigns.
Reference:
* Elements for Adjusting Target Populations:
Direct Attributes: These are specific attributes directly related to the target entity (e.g., customer age, location).
Related Attributes: These are attributes related to other entities connected to the target entity (e.g., purchase history).
Population Filters: Filters applied to define and narrow down the segment population (e.g., active customers).
* Steps to Adjust Populations in Segment Canvas:
Direct Attributes: Select attributes that directly describe the target population.
Related Attributes: Incorporate attributes from related entities to enrich the segment criteria.
Population Filters: Apply filters to refine and target specific subsets of the population.
Example: To create a segment of "Active Customers Aged 25-35," use age as a direct attribute, purchase activity as a related attribute, and apply population filters for activity status and age range.
* Practical Application:
Navigate to the Segment Canvas.
Adjust direct attributes and related attributes based on campaign goals.
Apply population filters to fine-tune the target audience.

The consultant should use B. Segmentation exclude rules to remove the recent customers. Segmentation exclude rules are filters that can be applied to a segment to exclude records that meet certain criteria. The consultant can use segmentation exclude rules to exclude customers who have made purchases within the last week from the segment that contains customers who have purchased within the past 6 months. This way, the segment will only include customers who are eligible for the promotional campaign.
The other options are not correct. Option A is incorrect because batch transforms are data processing tasks that can be applied to data streams or data lake objects to modify or enrich the data. Batch transforms are not used for segmentation or activation. Option C is incorrect because related attributes are attributes that are derived from the relationships between data model objects. Related attributes are not used for excluding records from a segment. Option D is incorrect because streaming insights are derived attributes that are calculated at the time of data ingestion. Streaming insights are not used for excluding records from a segment. Reference: Salesforce Data Cloud Consultant Exam Guide, Segmentation, Segmentation Exclude Rules

To address this new use case, the consultant should map the primary key from the two systems to Party Identification, using CRM ID as the identification name for both, and create a matching rule based on party identification that matches on CRM ID as the party identification name. This way, the consultant can ensure that the CRM Contacts and Marketing Contacts are matched based on their CRM ID, which is a unique identifier for each individual. By using Party Identification, the consultant can also leverage the benefits of this attribute, such as being able to match across different entities and sources, and being able to handle multiple values for the same individual. The other options are incorrect because they either do not use the CRM ID as the primary key, or they do not use Party Identification as the attribute type. Reference: Configure Identity Resolution Rulesets, Identity Resolution Match Rules, Data Cloud Identity Resolution Ruleset, Data Cloud Identity Resolution Config Input