The consolidation rate is a metric that measures the amount by which source profiles are combined to produce unified profiles in Data Cloud, calculated as 1 - (number of unified profiles / number of source profiles). A higher consolidation rate means that more source profiles are matched and merged into fewer unified profiles, while a lower consolidation rate means that fewer source profiles are matched and more unified profiles are created. There are two likely explanations for why the consolidation rate has recently increased for a customer:
* New data sources have been added to Data Cloud that largely overlap with the existing profiles. This means that the new data sources contain many profiles that are similar or identical to the profiles from the existing data sources. For example, if a customer adds a new CRM system that has the same customer records as their old CRM system, the new data source will overlap with the existing one.
When Data Cloud ingests the new data source, it will use the identity resolution ruleset to match and merge the overlapping profiles into unified profiles, resulting in a higher consolidation rate.
* Identity resolution rules have been added to the ruleset to increase the number of matched profiles. This means that the customer has modified their identity resolution ruleset to include more match rules or more match criteria that can identify more profiles as belonging to the same individual. For example, if a customer adds a match rule that matches profiles based on email address and phone number, instead of just email address, the ruleset will be able to match more profiles that have the same email address and phone number, resulting in a higher consolidation rate.
References: Identity Resolution Calculated Insight: Consolidation Rates for Unified Profiles, Configure Identity Resolution Rulesets

A streaming insight is a type of insight that analyzes streaming data in real time and triggers actions based on predefined conditions. 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. By using a streaming insight paired with a data action, a consultant can accommodate Cumulus Financial's request to track the daily transaction volume of each customer and send out a notification when the volume is outside the normal range. A calculated insight is a type of insight that performs calculations on data in a data space and stores the results in a data extension. A streaming data transform is a type of data transform that applies transformations to streaming data in real time and stores the results in a data extension. A flow is a type of automation that executes a series of actions when triggered by an event, a schedule, or another flow. None of these options can achieve the same functionality as a streaming insight paired with a data action. References: Use Insights in Data Cloud Unit, Streaming Insights and Data Actions Use Cases, Streaming Insights and Data Actions Limits and Behaviors

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. References: Configure Identity Resolution Rulesets, Identity Resolution Match Rules, Data Cloud Identity Resolution Ruleset, Data Cloud Identity Resolution Config Input

The correct answer is D. The CRM Connector allows standard fields to stream into Data Cloud in real time.
This means that any changes to the standard fields in the CRM data source are reflected in Data Cloud almost instantly, without waiting for the next scheduled synchronization. This feature enables Data Cloud to have the most up-to-date and accurate CRM data for segmentation and activation1.
The other options are incorrect for the following reasons:
* A. CRM data can be manually refreshed at any time by clicking the Refresh button on the data stream detail page2. This option is false.
* B. The CRM Connector's synchronization times can be customized to up to 60-minute intervals, not
15-minute intervals3. This option is false.
* C. Formula fields are not refreshed at regular sync intervals, but only at the next full refresh4. A full refresh is a complete data ingestion process that occurs once every 24 hours or when manually triggered.
This option is false.
References:
* 1: Connect and Ingest Data in Data Cloud article on Salesforce Help
* 2: Data Sources in Data Cloud unit on Trailhead
* 3: Data Cloud for Admins module on Trailhead
* 4: [Formula Fields in Data Cloud] unit on Trailhead
* : [Data Streams in Data Cloud] unit on Trailhead

The time zone that is used to publish and refresh data when performing segmentation or activation is D. Time zone set by the Salesforce Data Cloud org. This time zone is the one that is configured in the org settings when Data Cloud is provisioned, and it applies to all users and activities in Data Cloud. This time zone determines when the segments are scheduled to refresh and when the activations are scheduled to publish. Therefore, it is important to consider the time zone difference between the Data Cloud org and the destination systems or channels when planning the segmentation and activation strategies. References: Salesforce Data Cloud Consultant Exam Guide, Segmentation, Activation