Salesforce Data Cloud Consultant Practice Exams
Last updated on Sep 13,2026- Exam Code: Data Cloud Consultant
- Exam Name: Salesforce Certified Data Cloud Consultant
- Certification Provider: Salesforce
- Latest update: Sep 13,2026
Question #161
What are the two minimum requirements needed when using the Visual Insights Builder to create a
calculated insight? Choose 2 answers
- A . At least one measure
- B . At least one dimension
- C . At least two objects to Join
- D . A WHERE clause
Correct Answer: A, B
A, B
Explanation:
Introduction to Visual Insights Builder:
The Visual Insights Builder in Salesforce Data Cloud is a tool used to create calculated insights, which are custom metrics derived from the existing data.
Reference: Salesforce Visual Insights Builder Documentation Requirements for Creating Calculated Insights:
Measure: A measure is a quantitative value that you want to analyze, such as revenue, number of purchases, or total time spent on a platform.
Dimension: A dimension is a qualitative attribute that you use to categorize or filter the measures, such as date, region, or customer segment.
Reference: Salesforce Insights Builder Guide
Steps to Create a Calculated Insight:
Navigate to the Visual Insights Builder within Salesforce Data Cloud.
Select "Create New Insight" and choose the dataset.
Add at least one measure: This could be any metric you want to analyze, such as "Total Sales."
Add at least one dimension: This helps to break down the measure, such as "Sales by Region."
Reference: Salesforce Calculated Insights Creation Tutorial Practical Application:
Example: To create an insight on "Average Purchase Value by Region," you would need:
A measure: Total Purchase Value.
A dimension: Customer Region.
This allows for actionable insights, such as identifying high-performing regions.
A, B
Explanation:
Introduction to Visual Insights Builder:
The Visual Insights Builder in Salesforce Data Cloud is a tool used to create calculated insights, which are custom metrics derived from the existing data.
Reference: Salesforce Visual Insights Builder Documentation Requirements for Creating Calculated Insights:
Measure: A measure is a quantitative value that you want to analyze, such as revenue, number of purchases, or total time spent on a platform.
Dimension: A dimension is a qualitative attribute that you use to categorize or filter the measures, such as date, region, or customer segment.
Reference: Salesforce Insights Builder Guide
Steps to Create a Calculated Insight:
Navigate to the Visual Insights Builder within Salesforce Data Cloud.
Select "Create New Insight" and choose the dataset.
Add at least one measure: This could be any metric you want to analyze, such as "Total Sales."
Add at least one dimension: This helps to break down the measure, such as "Sales by Region."
Reference: Salesforce Calculated Insights Creation Tutorial Practical Application:
Example: To create an insight on "Average Purchase Value by Region," you would need:
A measure: Total Purchase Value.
A dimension: Customer Region.
This allows for actionable insights, such as identifying high-performing regions.
Question #162
A user wants to be able to create a multi-dimensional metric to identify unified individual lifetime value (LTV).
Which sequence of data model object (DMO) joins is necessary within the calculated Insight to enable this calculation?
- A . Unified Individual > Unified Link Individual > Sales Order
- B . Unified Individual > Individual > Sales Order
- C . Sales Order > Individual > Unified Individual
- D . Sales Order > Unified Individual
Correct Answer: A
A
Explanation:
To create a multi-dimensional metric to identify unified individual lifetime value (LTV), the sequence of data model object (DMO) joins that is necessary within the calculated Insight is Unified Individual > Unified Link Individual > Sales Order. This is because the Unified Individual DMO represents the unified profile of an individual or entity that is created by identity resolution1. The Unified Link Individual DMO represents the link between a unified individual and an individual from a source system2. The Sales Order DMO represents the sales order information from a source system3. By joining these three DMOs, you can calculate the LTV of a unified individual based on the sales order data from different source systems. The other options are incorrect because they do not join the correct DMOs to enable the LTV calculation.
Option B is incorrect because the Individual DMO represents the source profile of an individual or entity from a source system, not the unified profile4.
Option C is incorrect because the join order is reversed, and you need to start with the Unified Individual DMO to identify the unified profile.
Option D is incorrect because it is missing the Unified Link Individual DMO, which is needed to link the unified profile with the source profile.
Reference: Unified Individual Data Model Object, Unified Link Individual Data Model Object, Sales Order Data Model Object, Individual Data Model Object
A
Explanation:
To create a multi-dimensional metric to identify unified individual lifetime value (LTV), the sequence of data model object (DMO) joins that is necessary within the calculated Insight is Unified Individual > Unified Link Individual > Sales Order. This is because the Unified Individual DMO represents the unified profile of an individual or entity that is created by identity resolution1. The Unified Link Individual DMO represents the link between a unified individual and an individual from a source system2. The Sales Order DMO represents the sales order information from a source system3. By joining these three DMOs, you can calculate the LTV of a unified individual based on the sales order data from different source systems. The other options are incorrect because they do not join the correct DMOs to enable the LTV calculation.
Option B is incorrect because the Individual DMO represents the source profile of an individual or entity from a source system, not the unified profile4.
Option C is incorrect because the join order is reversed, and you need to start with the Unified Individual DMO to identify the unified profile.
Option D is incorrect because it is missing the Unified Link Individual DMO, which is needed to link the unified profile with the source profile.
Reference: Unified Individual Data Model Object, Unified Link Individual Data Model Object, Sales Order Data Model Object, Individual Data Model Object
Question #163
Northern Trail Outfitters (NTD) creates a calculated insight to compute recency, frequency, monetary {RFM) scores on its unified individuals. NTO then creates a segment based on these scores that it activates to a Marketing Cloud activation target.
Which two actions are required when configuring the activation? Choose 2 answers
- A . Add additional attributes.
- B . Choose a segment.
- C . Select contact points.
- D . Add the calculated insight in the activation.
Correct Answer: BC
BC
Explanation:
To configure an activation to a Marketing Cloud activation target, you need to choose a segment and select contact points. Choosing a segment allows you to specify which unified individuals you want to activate. Selecting contact points allows you to map the attributes from the segment to the fields in the Marketing Cloud data extension. You do not need to add additional attributes or add the calculated insight in the activation, as these are already part of the segment definition.
Reference: Create a Marketing Cloud Activation Target; Types of Data Targets in Data Cloud
BC
Explanation:
To configure an activation to a Marketing Cloud activation target, you need to choose a segment and select contact points. Choosing a segment allows you to specify which unified individuals you want to activate. Selecting contact points allows you to map the attributes from the segment to the fields in the Marketing Cloud data extension. You do not need to add additional attributes or add the calculated insight in the activation, as these are already part of the segment definition.
Reference: Create a Marketing Cloud Activation Target; Types of Data Targets in Data Cloud
Question #164
A consultant is ingesting a list of employees from their human resources database that they want to segment on.
Which data stream category should the consultant choose when ingesting this data?
- A . Profile Data
- B . Contact Data
- C . Other Data
- D . Engagement Data
Correct Answer: C
C
Explanation:
Categories of Data Streams:
Profile Data: Customer profiles and demographic information.
Contact Data: Contact points like email and phone numbers.
Other Data: Miscellaneous data that doesn’t fit into the other categories.
Engagement Data: Interactions and behavioral data.
Reference: Salesforce Data Stream Categories
Ingesting Employee Data:
Employee data typically doesn’t fit into profile, contact, or engagement categories meant for customer data.
"Other Data" is appropriate for non-customer-specific data like employee information.
Reference: Salesforce Data Ingestion Guide
Steps to Ingest Employee Data:
Navigate to the data ingestion settings in Salesforce Data Cloud.
Select "Create New Data Stream" and choose the "Other Data" category.
Map the fields from the HR database to the corresponding fields in Data Cloud.
Reference: Salesforce Data Ingestion Tutorial
Practical Application:
Example: A company ingests employee data to segment internal communications or analyze workforce metrics.
Choosing the "Other Data" category ensures that this non-customer data is correctly managed and utilized.
Reference: Salesforce Data Management Case Studies
C
Explanation:
Categories of Data Streams:
Profile Data: Customer profiles and demographic information.
Contact Data: Contact points like email and phone numbers.
Other Data: Miscellaneous data that doesn’t fit into the other categories.
Engagement Data: Interactions and behavioral data.
Reference: Salesforce Data Stream Categories
Ingesting Employee Data:
Employee data typically doesn’t fit into profile, contact, or engagement categories meant for customer data.
"Other Data" is appropriate for non-customer-specific data like employee information.
Reference: Salesforce Data Ingestion Guide
Steps to Ingest Employee Data:
Navigate to the data ingestion settings in Salesforce Data Cloud.
Select "Create New Data Stream" and choose the "Other Data" category.
Map the fields from the HR database to the corresponding fields in Data Cloud.
Reference: Salesforce Data Ingestion Tutorial
Practical Application:
Example: A company ingests employee data to segment internal communications or analyze workforce metrics.
Choosing the "Other Data" category ensures that this non-customer data is correctly managed and utilized.
Reference: Salesforce Data Management Case Studies
Question #165
A retailer wants to unify profiles using Loyalty ID which is different than the unique ID of their customers.
Which object should the consultant use in identity resolution to perform exact match rules on the Loyalty ID?
- A . Party Identification object
- B . Loyalty Identification object
- C . Individual object
- D . Contact Identification object
Correct Answer: A
A
Explanation:
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.
Reference: 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
A
Explanation:
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.
Reference: 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
Question #166
A customer has multiple team members who create segment audiences that work in different time zones. One team member works at the home office in the Pacific time zone, that matches the org Time Zone setting. Another team member works remotely in the Eastern time zone.
Which user will see their home time zone in the segment and activation schedule areas?
- A . The team member in the Pacific time zone.
- B . The team member in the Eastern time zone.
- C . Neither team member; Data Cloud shows all schedules in GMT.
- D . Both team members; Data Cloud adjusts the segment and activation schedules to the time zone of the logged-in user
Correct Answer: D
D
Explanation:
The correct answer is D, both team members; Data Cloud adjusts the segment and activation schedules to the time zone of the logged-in user. Data Cloud uses the time zone settings of the logged-in user to display the segment and activation schedules. This means that each user will see the schedules in their own home time zone, regardless of the org time zone setting or the location of other team members. This feature helps users to avoid confusion and errors when scheduling segments and activations across different time zones. The other options are incorrect because they do not reflect how Data Cloud handles time zones. The team member in the Pacific time zone will not see the same time zone as the org time zone setting, unless their personal time zone setting matches the org time zone setting. The team member in the Eastern time zone will not see the schedules in the org time zone setting, unless their personal time zone setting matches the org time zone setting. Data Cloud does not show all schedules in GMT, but rather in the user’s local time zone.
Reference: Data Cloud Time Zones
Change default time zones for Users and the organization Change your time zone settings in Salesforce, Google & Outlook
DateTime field and Time Zone Settings in Salesforce
D
Explanation:
The correct answer is D, both team members; Data Cloud adjusts the segment and activation schedules to the time zone of the logged-in user. Data Cloud uses the time zone settings of the logged-in user to display the segment and activation schedules. This means that each user will see the schedules in their own home time zone, regardless of the org time zone setting or the location of other team members. This feature helps users to avoid confusion and errors when scheduling segments and activations across different time zones. The other options are incorrect because they do not reflect how Data Cloud handles time zones. The team member in the Pacific time zone will not see the same time zone as the org time zone setting, unless their personal time zone setting matches the org time zone setting. The team member in the Eastern time zone will not see the schedules in the org time zone setting, unless their personal time zone setting matches the org time zone setting. Data Cloud does not show all schedules in GMT, but rather in the user’s local time zone.
Reference: Data Cloud Time Zones
Change default time zones for Users and the organization Change your time zone settings in Salesforce, Google & Outlook
DateTime field and Time Zone Settings in Salesforce
Question #167
The Salesforce CRM Connector is configured and the Case object data stream is set up. Subsequently, a new custom field named Business Priority is created on the Case object in Salesforce CRM. However, the new field is not available when trying to add it to the data stream.
Which statement addresses the cause of this issue?
- A . The Salesforce Integration User Is missing Rad permissions on the newly created field.
- B . The Salesforce Data Loader application should be used to perform a bulk upload from a desktop.
- C . Custom fields on the Case object are not supported for ingesting into Data Cloud.
- D . After 24 hours when the data stream refreshes it will automatically include any new fields that were added to the Salesforce CRM.
Correct Answer: A
A
Explanation:
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.
Reference: Create a Salesforce CRM Data Stream, Edit a Data Stream, Salesforce Data Cloud Full Refresh for CRM, SFMC, or Ingestion API Data Streams
A
Explanation:
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.
Reference: Create a Salesforce CRM Data Stream, Edit a Data Stream, Salesforce Data Cloud Full Refresh for CRM, SFMC, or Ingestion API Data Streams
Question #168
A consultant is connecting sales order data to Data Cloud and considers whether to use the Profile, Engagement, or Other categories to map the DLO. The consultant chooses to map the DLO called Order-Headers to the Sales Order DMO using the Engagement category.
What is the impact of this action on future mappings?
- A . A DLO with category Engagement can be mapped to any DMO using either Profile. Engagement, or Other categories.
- B . When mapping a Profile DLO to the Sales Order DMO, the category gets updated to Profile.
- C . Sales Order DMO gets assigned to both the Profile and Engagement categories when mapping a Profile DLO.
- D . Only Engagement category DLOs can be mapped to the Sales Order DMO. Sales Order gets assigned to the Engagement Category.
Correct Answer: D
D
Explanation:
Data Lake Objects (DLOs) and Data Model Objects (DMOs): In Salesforce Data Cloud, DLOs are mapped to DMOs to organize and structure data. Categories like Profile, Engagement, and Other define how these mappings are used.
Engagement Category: Mapping a DLO to the Engagement category indicates that the data is related to customer interactions and activities.
Impact on Future Mappings:
Engagement Category Restriction: When a DLO like Order-Headers is mapped to the Sales Order DMO under the Engagement category, future mappings of the Sales Order DMO are restricted to Engagement category DLOs.
Category Assignment: The Sales Order DMO is assigned to the Engagement category, meaning only DLOs categorized as Engagement can be mapped to it in the future.
Benefits:
Consistency: Ensures consistent data categorization and usage, aligning data with its intended purpose.
Accuracy: Helps in maintaining the integrity of data mapping and ensures that engagement-related
data is accurately captured and utilized.
Reference: Salesforce Data Cloud Mapping
Salesforce Data Cloud Categories
D
Explanation:
Data Lake Objects (DLOs) and Data Model Objects (DMOs): In Salesforce Data Cloud, DLOs are mapped to DMOs to organize and structure data. Categories like Profile, Engagement, and Other define how these mappings are used.
Engagement Category: Mapping a DLO to the Engagement category indicates that the data is related to customer interactions and activities.
Impact on Future Mappings:
Engagement Category Restriction: When a DLO like Order-Headers is mapped to the Sales Order DMO under the Engagement category, future mappings of the Sales Order DMO are restricted to Engagement category DLOs.
Category Assignment: The Sales Order DMO is assigned to the Engagement category, meaning only DLOs categorized as Engagement can be mapped to it in the future.
Benefits:
Consistency: Ensures consistent data categorization and usage, aligning data with its intended purpose.
Accuracy: Helps in maintaining the integrity of data mapping and ensures that engagement-related
data is accurately captured and utilized.
Reference: Salesforce Data Cloud Mapping
Salesforce Data Cloud Categories
Question #169
What should an organization use to stream inventory levels from an inventory management system into Data Cloud in a fast and scalable, near-real-time way?
- A . Cloud Storage Connector
- B . Commerce Cloud Connector
- C . Ingestion API
- D . Marketing Cloud Personalization Connector
Correct Answer: C
C
Explanation:
The Ingestion API is a RESTful API that allows you to stream data from any source into Data Cloud in a fast and scalable way. You can use the Ingestion API to send data from your inventory management system into Data Cloud as JSON objects, and then use Data Cloud to create data models, segments, and insights based on your inventory data. The Ingestion API supports both batch and streaming modes, and can handle up to 100,000 records per second. The Ingestion API also provides features such as data validation, encryption, compression, and retry mechanisms to ensure data quality and security.
Reference: Ingestion API Developer Guide, Ingest Data into Data Cloud
C
Explanation:
The Ingestion API is a RESTful API that allows you to stream data from any source into Data Cloud in a fast and scalable way. You can use the Ingestion API to send data from your inventory management system into Data Cloud as JSON objects, and then use Data Cloud to create data models, segments, and insights based on your inventory data. The Ingestion API supports both batch and streaming modes, and can handle up to 100,000 records per second. The Ingestion API also provides features such as data validation, encryption, compression, and retry mechanisms to ensure data quality and security.
Reference: Ingestion API Developer Guide, Ingest Data into Data Cloud
Question #170
Northern Trail Outfitters wants to create a segment with customers that have purchased in the last 24 hours. The segment data must be as up to date as possible.
What should the consultant Implement when creating the segment?
- A . Use streaming insights for near real-time segmentation results.
- B . Use Einstein segmentation optimization to collect data from the last 24 hours.
- C . Use rapid segments with a publish interval of 1 hour.
- D . Use standard segment with a publish interval of 30 minutes.
Correct Answer: A
A
Explanation:
To address Northern Trail Outfitters’ requirement of creating a segment with customers who have purchased in the last 24 hours, while ensuring the data is as up to date as possible, streaming insights is the most appropriate solution.
Here’s why:
Understanding Streaming Insights:
Salesforce Data Cloud provides Streaming Insights, which enables near real-time data processing and segmentation. This feature allows businesses to capture and act on customer interactions or transactions almost instantly, making it ideal for time-sensitive use cases like identifying recent purchasers.
Why Not Other Options?
Option B (Einstein Segmentation Optimization): Einstein Segmentation Optimization focuses on improving segment performance using AI but does not inherently provide near real-time data updates. It is more about refining existing segments rather than ensuring low-latency data availability.
Option C (Rapid Segments with a Publish Interval of 1 Hour): Rapid Segments are faster than standard segments but still involve a delay due to the publish interval. A 1-hour interval would not meet the "as up to date as possible" requirement.
Option D (Standard Segment with a Publish Interval of 30 Minutes): Standard segments are processed less frequently and typically involve longer delays. Even with a 30-minute interval, this option cannot match the near real-time capabilities of streaming insights.
How Streaming Insights Works:
Streaming Insights processes data from connected sources (e.g., CRM, external systems) in near real-time.
When a customer makes a purchase, the transaction data is ingested into Data Cloud and immediately available for segmentation.
The consultant can configure a segment rule to include only customers whose purchase timestamp
falls within the last 24 hours.
Salesforce Documentation Reference:
According to Salesforce’s official Data Cloud documentation, Streaming Insights is designed for scenarios where timely data is critical. It ensures that segments reflect the latest customer behavior without significant delays, aligning perfectly with Northern Trail Outfitters’ needs.
A
Explanation:
To address Northern Trail Outfitters’ requirement of creating a segment with customers who have purchased in the last 24 hours, while ensuring the data is as up to date as possible, streaming insights is the most appropriate solution.
Here’s why:
Understanding Streaming Insights:
Salesforce Data Cloud provides Streaming Insights, which enables near real-time data processing and segmentation. This feature allows businesses to capture and act on customer interactions or transactions almost instantly, making it ideal for time-sensitive use cases like identifying recent purchasers.
Why Not Other Options?
Option B (Einstein Segmentation Optimization): Einstein Segmentation Optimization focuses on improving segment performance using AI but does not inherently provide near real-time data updates. It is more about refining existing segments rather than ensuring low-latency data availability.
Option C (Rapid Segments with a Publish Interval of 1 Hour): Rapid Segments are faster than standard segments but still involve a delay due to the publish interval. A 1-hour interval would not meet the "as up to date as possible" requirement.
Option D (Standard Segment with a Publish Interval of 30 Minutes): Standard segments are processed less frequently and typically involve longer delays. Even with a 30-minute interval, this option cannot match the near real-time capabilities of streaming insights.
How Streaming Insights Works:
Streaming Insights processes data from connected sources (e.g., CRM, external systems) in near real-time.
When a customer makes a purchase, the transaction data is ingested into Data Cloud and immediately available for segmentation.
The consultant can configure a segment rule to include only customers whose purchase timestamp
falls within the last 24 hours.
Salesforce Documentation Reference:
According to Salesforce’s official Data Cloud documentation, Streaming Insights is designed for scenarios where timely data is critical. It ensures that segments reflect the latest customer behavior without significant delays, aligning perfectly with Northern Trail Outfitters’ needs.