Salesforce Updated Data-Cloud-Consultant Exam Questions and Answers by ettie

 The reason for the activated count being smaller than the segment count is A. Data Cloud enforces the presence of Contact Point for Marketing Cloud activations. If the individual does not have a related Contact Point, it will not be activated. A Contact Point is a data model object that represents a channel or method of communication with an individual, such as email, phone, or social media. For Marketing Cloud activations, Data Cloud requires that the individual has a related Contact Point of type Email, which contains a valid email address. If the individual does not have such a Contact Point, or if the Contact Point is missing or invalid, the individual will not be activated and will not receive the email communication. Therefore, the activated count may be lower than the segment count, depending on how many individuals in the segment have a valid email Contact Point. References: Salesforce Data Cloud Consultant Exam Guide, Contact Point, Marketing Cloud Activation

A segment is a subset of individuals who meet certain criteria based on their attributes and behaviors. A consultant can use different types of criteria when building a segment in Data Cloud, such as:

Direct attributes: These are attributes that describe the characteristics of an individual, such as name, email, gender, age, etc. These attributes are stored in the Profile data model object (DMO) and can be used to filter individuals based on their profile data.

Calculated Insights: These are insights that perform calculations on data in a data space and store the results in a data extension. These insights can be used to segment individuals based on metrics or scores derived from their data, such as customer lifetime value, churn risk, loyalty tier, etc.

Related attributes: These are attributes that describe the relationships of an individual with other DMOs, such as Email, Engagement, Order, Product, etc. These attributes can be used to segment individuals based on their interactions or transactions with different entities, such as email opens, clicks, purchases, etc.

The other two options are not valid criteria for building a segment in Data Cloud. Data stream attributes are attributes that describe the streaming data that is ingested into Data Cloud from various sources, such as Marketing Cloud, Commerce Cloud, Service Cloud, etc. These attributes are not directly available for segmentation, but they can be transformed and stored in data extensions using streaming data transforms. Streaming insights are insights that analyze streaming data in real time and trigger actions based on predefined conditions. These insights are not used for segmentation, but for activation and personalization. References: Create a Segment in Data Cloud, Use Insights in Data Cloud, Data Cloud Data Model

The Salesforce CRM Connector uses the Salesforce Integration User to access the data from the Salesforce CRM org. The Integration User must have the Read permission on the fields that are included in the data stream. If the Integration User does not have the Read permission on the newly created field, the field will not be available for selection in the data stream configuration. To resolve this issue, the administrator should assign the Read permission on the new field to the Integration User profile or permission set. References: Create a Salesforce CRM Data Stream, Edit a Data Stream, Salesforce Data Cloud Full Refresh for CRM, SFMC, or Ingestion API Data Streams

 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