Data-Cloud-Consultant Salesforce Exam Lab Questions

When advising a customer about using the Consent API in Salesforce to comply with requests for the right to be forgotten, the consultant should focus on two primary considerations:

Data deletion requests are submitted for Individual profiles (Answer C): The Consent API in Salesforce is designed to handle data deletion requests specifically for individual profiles. This means that when a request is made to delete data, it is targeted at the personal data associated with an individual's profile in the Salesforce system. The consultant should inform the customer that the requests must be specific to individual profiles to ensure accurate processing and compliance with privacy laws.

Data deletion requests submitted to Data Cloud are passed to all connected Salesforce clouds (Answer D): When a data deletion request is made through the Consent API in Salesforce Data Cloud, the request is not limited to the Data Cloud alone. Instead, it propagates through all connected Salesforce clouds, such as Sales Cloud, Service Cloud, Marketing Cloud, etc. This ensures comprehensive compliance with the right to be forgotten across the entire Salesforce ecosystem. The customer should be aware that the deletion request will affect all instances of the individual’s data across the connected Salesforce environments.

The most efficient approach that a consultant should take when ingesting this data to ensure all the different phone numbers are properly mapped and available for use in activation is B. Ingest the Contact object and use streaming transforms to normalize the phone numbers from the Contact data stream into a separate Phone data lake object (DLO) that contains three rows, and then map this new DLO to the Contact Point Phone data map object. This approach allows the consultant to use the streaming transforms feature of Data Cloud, which enables data manipulation and transformation at the time of ingestion, without requiring any additional processing or storage. Streaming transforms can be used to normalize the phone numbers from the Contact data stream, such as removing spaces, dashes, or parentheses, and adding country codes if needed. The normalized phone numbers can then be stored in a separate Phone DLO, which can have one row for each phone number type (work, home, mobile). The Phone DLO can then be mapped to the Contact Point Phone data map object, which is a standard object that represents a phone number associated with a contact point. This way, the consultant can ensure that all the phone numbers are available for activation, such as sending SMS messages or making calls to the customers.

The other options are not as efficient as option B. Option A is incorrect because it does not normalize the phone numbers, which may cause issues with activation or identity resolution. Option C is incorrect because it requires creating a calculated insight, which is an additional step that consumes more resources and time than streaming transforms. Option D is incorrect because it requires creating formula fields in the Contact data stream, which may not be supported by the CRM Connector or may cause conflicts with the existing fields in the Contact object. References: Salesforce Data Cloud Consultant Exam Guide, Data Ingestion and Modeling, Streaming Transforms, Contact Point Phone

The filter operator Last Number of Days allows you to filter on date fields using a relative date range that specifies the number of days before today. For example, you can use this operator to filter on customers who have visited your website in the last 7 days, or the last 30 days, or any number of days you want. This operator is useful for creating dynamic segments that update automatically based on the current date12. References:

Relative Date Filter Reference

Create Filtered Segments

 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.

 References:

Salesforce Data Cloud Ingestion Methods

Salesforce Bulk Data Ingestion

Salesforce Streaming Data Ingestion