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

 To package Data Cloud components from one organization to another, the consultant should include the following components in a data kit:

• Data model objects: These are the custom objects that define the data model for Data Cloud, such as Individual, Segment, Activity, etc. They store the data ingested from various sources and enable the creation of unified profiles and segments1.
• Identity resolution rulesets: These are the rules that determine how data from different sources are matched and merged to create unified profiles. They specify the criteria, logic, and priority for identity resolution2. References:
• 1: Data Model Objects in Data Cloud
• 2: Identity Resolution Rulesets in Data Cloud

To create a segment for a birthday campaign that is evaluated daily, the consultant should use the Is Anniversary Of operator. This operator compares a date field with the current date and returns true if the month and day are the same, regardless of the year. For example, if the date field is 1990-01-01 and the current date is 2023-01-01, the operator returns true. This way, the consultant can create a segment that includes all the customers who have their birthday on the same day as the current date, and the segment will be updated daily with the new birthdays. The other options are not the best operators to use for this purpose because:

• A. The Is Today operator compares a date field with the current date and returns true if the date is the same, including the year. For example, if the date field is 1990-01-01 and the current date is 2023-01-01, the operator returns false. This operator is not suitable for a birthday campaign, as it will only include the customers who were born on the same day and year as the current date, which is very unlikely.
• B. The Is Birthday operator is not a valid operator in Data Cloud. There is no such operator available in the segment canvas or the calculated insight editor.
• C. The Is Between operator compares a date field with a range of dates and returns true if the date is within the range, including the endpoints. For example, if the date field is 1990-01-01 and the range is 2022-12-25 to 2023-01-05, the operator returns true. This operator is not suitable for a birthday campaign, as it will only include the customers who have their birthday within a fixed range of dates, and the segment will not be updated daily with the new birthdays.

 Engagement-based related attributes are attributes that describe the interactions of a person with an email message, such as opens, clicks, unsubscribes, etc. These attributes are stored in the Engagement data model object (DMO) and can be added to an activation to send more personalized communications. However, there are some considerations and limitations when using engagement-based related attributes, such as:

• For engagement data, activation supports a 90-day lookback window. This means that only the attributes from the engagement events that occurred within the last 90 days are considered for activation. Any records outside of this window are not included in the activation payload. Therefore, the consultant should review the event time of the related engagement events and make sure they are within the lookback window.
• The correct path to the related attributes must be selected for the activation. A path is a sequence of DMOs that are connected by relationships in the data model. For example, the path from Individual to Engagement is Individual -> Email -> Engagement. The path determines which related attributes are available for activation and how they are filtered. Therefore, the consultant should review the path selection and make sure it matches the desired related attributes and filters.

The other two options are not relevant for this issue. The activations can reference segments that segment on profile data rather than engagement data, as long as the activation target supports related attributes. The activated profiles do not need to have a Unified Contact Point, which is a unique identifier for a person across different data sources, to activate engagement-based related attributes. References: Add Related Attributes to an Activation, Related Attributes in Data Cloud activation have no values, Explore the Engagement Data Model Object

The Party Identification object is the correct object to use in identity resolution to perform exact match rules on the Loyalty ID. The Party Identification object is a child object of the Individual object that stores different types of identifiers for an individual, such as email, phone, loyalty ID, social media handle, etc. Each identifier has a type, a value, and a source. The consultant can use the Party Identification object to create a match rule that compares the Loyalty ID type and value across different sources and links the corresponding individuals.

The other options are not correct objects to use in identity resolution to perform exact match rules on the Loyalty ID. The Loyalty Identification object does not exist in Data Cloud. The Individual object is the parent object that represents a unified profile of an individual, but it does not store the Loyalty ID directly. The Contact Identification object is a child object of the Contact object that stores identifiers for a contact, such as email, phone, etc., but it does not store the Loyalty ID.

References:

• Data Modeling Requirements for Identity Resolution
• Identity Resolution in a Data Space
• Configure Identity Resolution Rulesets
• Map Required Objects
• Data and Identity in Data Cloud