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 #141
A customer wants to create segments of users based on their Customer Lifetime Value.
However, the source data that will be brought into Data Cloud does not include that key performance indicator (KPI).
Which sequence of steps should the consultant follow to achieve this requirement?
- A . Ingest Data > Map Data to Data Model > Create Calculated Insight > Use in Segmentation
- B . Create Calculated Insight > Map Data to Data Model> Ingest Data > Use in Segmentation
- C . Create Calculated Insight > Ingest Data > Map Data to Data Model> Use in Segmentation
- D . Ingest Data > Create Calculated Insight > Map Data to Data Model > Use in Segmentation
Correct Answer: A
A
Explanation:
To create segments of users based on their Customer Lifetime Value (CLV), the sequence of steps that the consultant should follow is Ingest Data > Map Data to Data Model > Create Calculated Insight > Use in Segmentation. This is because the first step is to ingest the source data into Data Cloud using data streams1. The second step is to map the source data to the data model, which defines the structure and attributes of the data2. The third step is to create a calculated insight, which is a derived attribute that is computed based on the source or unified data3. In this case, the calculated insight would be the CLV, which can be calculated using a formula or a query based on the sales order data4. The fourth step is to use the calculated insight in segmentation, which is the process of creating groups of individuals or entities based on their attributes and behaviors. By using the CLV calculated insight, the consultant can segment the users by their predicted revenue from the lifespan of their relationship with the brand. The other options are incorrect because they do not follow the correct sequence of steps to achieve the requirement.
Option B is incorrect because it is not possible to create a calculated insight before ingesting and mapping the data, as the calculated insight depends on the data model objects3.
Option C is incorrect because it is not possible to create a calculated insight before mapping the data, as the calculated insight depends on the data model objects3.
Option D is incorrect because it is not recommended to create a calculated insight before mapping the data, as the calculated insight may not reflect the correct data model structure and attributes3.
Reference: Data Streams Overview, Data Model Objects Overview, Calculated Insights Overview, Calculating Customer Lifetime Value (CLV) With Salesforce, [Segmentation Overview]
A
Explanation:
To create segments of users based on their Customer Lifetime Value (CLV), the sequence of steps that the consultant should follow is Ingest Data > Map Data to Data Model > Create Calculated Insight > Use in Segmentation. This is because the first step is to ingest the source data into Data Cloud using data streams1. The second step is to map the source data to the data model, which defines the structure and attributes of the data2. The third step is to create a calculated insight, which is a derived attribute that is computed based on the source or unified data3. In this case, the calculated insight would be the CLV, which can be calculated using a formula or a query based on the sales order data4. The fourth step is to use the calculated insight in segmentation, which is the process of creating groups of individuals or entities based on their attributes and behaviors. By using the CLV calculated insight, the consultant can segment the users by their predicted revenue from the lifespan of their relationship with the brand. The other options are incorrect because they do not follow the correct sequence of steps to achieve the requirement.
Option B is incorrect because it is not possible to create a calculated insight before ingesting and mapping the data, as the calculated insight depends on the data model objects3.
Option C is incorrect because it is not possible to create a calculated insight before mapping the data, as the calculated insight depends on the data model objects3.
Option D is incorrect because it is not recommended to create a calculated insight before mapping the data, as the calculated insight may not reflect the correct data model structure and attributes3.
Reference: Data Streams Overview, Data Model Objects Overview, Calculated Insights Overview, Calculating Customer Lifetime Value (CLV) With Salesforce, [Segmentation Overview]
Question #142
Which tool allows users to visualize and analyze unified customer data in Data Cloud?
- A . Salesforce CLI
- B . Heroku
- C . Tableau
- D . Einstein Analytics
Correct Answer: C
C
Explanation:
Salesforce Data Cloud Overview: Salesforce Data Cloud enables organizations to unify and manage customer data from multiple sources, providing a comprehensive view of customer interactions and behaviors.
Visualization and Analysis: For visualizing and analyzing this unified data, Salesforce provides multiple tools, each serving different purposes. Tableau is particularly noted for its advanced analytics and visualization capabilities.
Tableau Integration: Tableau is integrated with Salesforce, allowing users to create detailed and interactive visualizations. It can connect directly to Salesforce Data Cloud, pulling in unified data for comprehensive analysis.
Capabilities: Tableau supports a wide range of data sources and formats, offering drag-and-drop features to create complex charts and dashboards. This makes it an ideal tool for analyzing the rich datasets managed within Salesforce Data Cloud.
Reference: Salesforce Help: Tableau Integration
Salesforce Data Cloud Overview
C
Explanation:
Salesforce Data Cloud Overview: Salesforce Data Cloud enables organizations to unify and manage customer data from multiple sources, providing a comprehensive view of customer interactions and behaviors.
Visualization and Analysis: For visualizing and analyzing this unified data, Salesforce provides multiple tools, each serving different purposes. Tableau is particularly noted for its advanced analytics and visualization capabilities.
Tableau Integration: Tableau is integrated with Salesforce, allowing users to create detailed and interactive visualizations. It can connect directly to Salesforce Data Cloud, pulling in unified data for comprehensive analysis.
Capabilities: Tableau supports a wide range of data sources and formats, offering drag-and-drop features to create complex charts and dashboards. This makes it an ideal tool for analyzing the rich datasets managed within Salesforce Data Cloud.
Reference: Salesforce Help: Tableau Integration
Salesforce Data Cloud Overview
Question #143
A customer has a Master Customer table from their CRM to ingest into Data Cloud. The table contains a name and primary email address, along with other personally Identifiable information (Pll).
How should the fields be mapped to support identity resolution?
- A . Create a new custom object with fields that directly match the incoming table.
- B . Map all fields to the Customer object.
- C . Map name to the Individual object and email address to the Contact Phone Email object.
- D . Map all fields to the Individual object, adding a custom field for the email address.
Correct Answer: C
C
Explanation:
To support identity resolution in Data Cloud, the fields from the Master Customer table should be mapped to the standard data model objects that are designed for this purpose. The Individual object is used to store the name and other personally identifiable information (PII) of a customer, while the Contact Phone Email object is used to store the primary email address and other contact information of a customer. These objects are linked by a relationship field that indicates the contact information belongs to the individual. By mapping the fields to these objects, Data Cloud can use the identity resolution rules to match and reconcile the profiles from different sources based on the name and email address fields. The other options are not recommended because they either create a new custom object that is not part of the standard data model, or map all fields to the Customer object that is not intended for identity resolution, or map all fields to the Individual object that does not have a standard email address field.
Reference: Data Modeling Requirements for Identity Resolution, Create Unified Individual Profiles
C
Explanation:
To support identity resolution in Data Cloud, the fields from the Master Customer table should be mapped to the standard data model objects that are designed for this purpose. The Individual object is used to store the name and other personally identifiable information (PII) of a customer, while the Contact Phone Email object is used to store the primary email address and other contact information of a customer. These objects are linked by a relationship field that indicates the contact information belongs to the individual. By mapping the fields to these objects, Data Cloud can use the identity resolution rules to match and reconcile the profiles from different sources based on the name and email address fields. The other options are not recommended because they either create a new custom object that is not part of the standard data model, or map all fields to the Customer object that is not intended for identity resolution, or map all fields to the Individual object that does not have a standard email address field.
Reference: Data Modeling Requirements for Identity Resolution, Create Unified Individual Profiles
Question #144
A segment fails to refresh with the error "Segment references too many data lake objects (DLOS)".
Which two troubleshooting tips should help remedy this issue? Choose 2 answers
- A . Split the segment into smaller segments.
- B . Use calculated insights in order to reduce the complexity of the segmentation query.
- C . Refine segmentation criteria to limit up to five custom data model objects (DMOs).
- D . Space out the segment schedules to reduce DLO load.
Correct Answer: A, B
A, B
Explanation:
The error “Segment references too many data lake objects (DLOs)” occurs when a segment query exceeds the limit of 50 DLOs that can be referenced in a single query. This can happen when the segment has too many filters, nested segments, or exclusion criteria that involve different DLOs.
To remedy this issue, the consultant can try the following troubleshooting tips:
Split the segment into smaller segments. The consultant can divide the segment into multiple segments that have fewer filters, nested segments, or exclusion criteria. This can reduce the number of DLOs that are referenced in each segment query and avoid the error. The consultant can then use the smaller segments as nested segments in a larger segment, or activate them separately.
Use calculated insights in order to reduce the complexity of the segmentation query. The consultant can create calculated insights that are derived from existing data using formulas. Calculated insights can simplify the segmentation query by replacing multiple filters or nested segments with a single attribute. For example, instead of using multiple filters to segment individuals based on their purchase history, the consultant can create a calculated insight that calculates the lifetime value of each individual and use that as a filter.
The other options are not troubleshooting tips that can help remedy this issue. Refining segmentation criteria to limit up to five custom data model objects (DMOs) is not a valid option, as the limit of 50 DLOs applies to both standard and custom DMOs. Spacing out the segment schedules to reduce DLO load is not a valid option, as the error is not related to the DLO load, but to the segment query complexity.
Reference: Troubleshoot Segment Errors
Create a Calculated Insight
Create a Segment in Data Cloud
A, B
Explanation:
The error “Segment references too many data lake objects (DLOs)” occurs when a segment query exceeds the limit of 50 DLOs that can be referenced in a single query. This can happen when the segment has too many filters, nested segments, or exclusion criteria that involve different DLOs.
To remedy this issue, the consultant can try the following troubleshooting tips:
Split the segment into smaller segments. The consultant can divide the segment into multiple segments that have fewer filters, nested segments, or exclusion criteria. This can reduce the number of DLOs that are referenced in each segment query and avoid the error. The consultant can then use the smaller segments as nested segments in a larger segment, or activate them separately.
Use calculated insights in order to reduce the complexity of the segmentation query. The consultant can create calculated insights that are derived from existing data using formulas. Calculated insights can simplify the segmentation query by replacing multiple filters or nested segments with a single attribute. For example, instead of using multiple filters to segment individuals based on their purchase history, the consultant can create a calculated insight that calculates the lifetime value of each individual and use that as a filter.
The other options are not troubleshooting tips that can help remedy this issue. Refining segmentation criteria to limit up to five custom data model objects (DMOs) is not a valid option, as the limit of 50 DLOs applies to both standard and custom DMOs. Spacing out the segment schedules to reduce DLO load is not a valid option, as the error is not related to the DLO load, but to the segment query complexity.
Reference: Troubleshoot Segment Errors
Create a Calculated Insight
Create a Segment in Data Cloud
Question #145
Which data stream category type should be assigned in order to use the dataset for date and time-based operations in segmentation and calculated insights?
- A . Individual
- B . Engagement
- C . Sales Order
- D . Profile
Correct Answer: B
B
Explanation:
To use a dataset for date and time-based operations in segmentation and calculated insights, the data stream category type should be assigned as Engagement.
Here’s why:
Understanding the Requirement
The goal is to perform date and time-based operations (e.g., filtering customers based on specific dates or times) in segmentation and calculated insights.
This requires a data stream category that captures customer interactions or activities over time.
Why Engagement?
Engagement Data Streams:
Engagement data streams are designed to capture customer interactions, such as website visits, email opens, purchases, or other time-based activities.
These streams inherently include timestamps, making them ideal for date and time-based operations.
Use in Segmentation and Calculated Insights:
Segmentation often involves filtering customers based on their engagement behavior (e.g., "customers who visited the website in the last 7 days").
Calculated insights leverage engagement data to derive metrics like recency, frequency, and trends over time.
Other Categories Are Less Suitable:
Individual: Focuses on demographic or static attributes (e.g., name, age) rather than time-based interactions.
Sales Order: Captures transactional data but is not optimized for general engagement-based operations.
Profile: Represents unified customer profiles and does not directly support date and time-based operations.
Steps to Implement This Solution
Step 1: Assign the Correct Category
When setting up the data stream, assign the Engagement category to ensure it is optimized for time-based operations.
Step 2: Map Date-Time Fields
Ensure that relevant fields (e.g., interaction timestamps) are mapped correctly during ingestion.
Step 3: Use in Segmentation and Insights
Leverage the ingested engagement data for segmentation (e.g., "customers who engaged in the last 24 hours") and calculated insights (e.g., "average time between interactions").
Conclusion
The Engagement category is specifically designed for capturing time-based interactions, making it the best choice for datasets used in date and time-based operations in segmentation and calculated insights.
B
Explanation:
To use a dataset for date and time-based operations in segmentation and calculated insights, the data stream category type should be assigned as Engagement.
Here’s why:
Understanding the Requirement
The goal is to perform date and time-based operations (e.g., filtering customers based on specific dates or times) in segmentation and calculated insights.
This requires a data stream category that captures customer interactions or activities over time.
Why Engagement?
Engagement Data Streams:
Engagement data streams are designed to capture customer interactions, such as website visits, email opens, purchases, or other time-based activities.
These streams inherently include timestamps, making them ideal for date and time-based operations.
Use in Segmentation and Calculated Insights:
Segmentation often involves filtering customers based on their engagement behavior (e.g., "customers who visited the website in the last 7 days").
Calculated insights leverage engagement data to derive metrics like recency, frequency, and trends over time.
Other Categories Are Less Suitable:
Individual: Focuses on demographic or static attributes (e.g., name, age) rather than time-based interactions.
Sales Order: Captures transactional data but is not optimized for general engagement-based operations.
Profile: Represents unified customer profiles and does not directly support date and time-based operations.
Steps to Implement This Solution
Step 1: Assign the Correct Category
When setting up the data stream, assign the Engagement category to ensure it is optimized for time-based operations.
Step 2: Map Date-Time Fields
Ensure that relevant fields (e.g., interaction timestamps) are mapped correctly during ingestion.
Step 3: Use in Segmentation and Insights
Leverage the ingested engagement data for segmentation (e.g., "customers who engaged in the last 24 hours") and calculated insights (e.g., "average time between interactions").
Conclusion
The Engagement category is specifically designed for capturing time-based interactions, making it the best choice for datasets used in date and time-based operations in segmentation and calculated insights.
Question #146
Cloud Kicks plans to do a full deletion of one of its existing data streams and its underlying data lake object (DLO).
What should the consultant consider before deleting the data stream?
- A . The underlying DLO can be used in a data transform.
- B . The underlying DLO cannot be mapped to a data model object.
- C . The data stream must be associated with a data kit.
- D . The data stream can be deleted without implicitly deleting the underlying DLO.
Correct Answer: A
A
Explanation:
Data Streams and DLOs: In Salesforce Data Cloud, data streams are used to ingest data, which is then stored in Data Lake Objects (DLOs).
Deletion Considerations: Before deleting a data stream, it’s crucial to consider the dependencies and usage of the underlying DLO.
Data Transform Usage:
Impact of Deletion: If the underlying DLO is used in a data transform, deleting the data stream will affect any transforms relying on that DLO.
Dependency Check: Ensure that the DLO is not part of any active data transformations or processes that could be disrupted by its deletion.
Reference: Salesforce Data Cloud Documentation: Data Streams
Salesforce Data Cloud Documentation: Data Transforms
A
Explanation:
Data Streams and DLOs: In Salesforce Data Cloud, data streams are used to ingest data, which is then stored in Data Lake Objects (DLOs).
Deletion Considerations: Before deleting a data stream, it’s crucial to consider the dependencies and usage of the underlying DLO.
Data Transform Usage:
Impact of Deletion: If the underlying DLO is used in a data transform, deleting the data stream will affect any transforms relying on that DLO.
Dependency Check: Ensure that the DLO is not part of any active data transformations or processes that could be disrupted by its deletion.
Reference: Salesforce Data Cloud Documentation: Data Streams
Salesforce Data Cloud Documentation: Data Transforms
Question #147
A consultant at Northern Trail Outfitters is attempting to ingest a field from the Contact object in Salesforce CRM that contains both yyyy-mm-dd and yyyy-mm-dd hh:mm:ss values. The target field is set to Date datatype.
Which statement is true in this situation?
- A . The target field will throw an error and store null values.
- B . The target field will be able to hold both types of values.
- C . The target field will only hold the time part and ignore the date part.
- D . The target field will only hold the date part and ignore the time part.
Correct Answer: D
D
Explanation:
Field Data Types: Salesforce CRM’s Contact object fields can store data in various formats. When ingesting data into Salesforce Data Cloud, the target field’s data type determines how the data is processed and stored.
Date Data Type: If the target field in Data Cloud is set to Date data type, it is designed to store date values without time information.
Mixed Format Values: When ingesting a field containing both date (yyyy-mm-dd) and datetime (yyyy-mm-dd hh:mm:ss) values into a Date data type field:
The Date field will extract and store only the date part (yyyy-mm-dd), ignoring the time part (hh:mm:ss).
Result:
Date Values: yyyy-mm-dd values are stored as-is.
Datetime Values: yyyy-mm-dd hh:mm:ss values are truncated to yyyy-mm-dd, and the time component is ignored.
Reference: Salesforce Data Cloud Field Mapping
Salesforce Data Types
D
Explanation:
Field Data Types: Salesforce CRM’s Contact object fields can store data in various formats. When ingesting data into Salesforce Data Cloud, the target field’s data type determines how the data is processed and stored.
Date Data Type: If the target field in Data Cloud is set to Date data type, it is designed to store date values without time information.
Mixed Format Values: When ingesting a field containing both date (yyyy-mm-dd) and datetime (yyyy-mm-dd hh:mm:ss) values into a Date data type field:
The Date field will extract and store only the date part (yyyy-mm-dd), ignoring the time part (hh:mm:ss).
Result:
Date Values: yyyy-mm-dd values are stored as-is.
Datetime Values: yyyy-mm-dd hh:mm:ss values are truncated to yyyy-mm-dd, and the time component is ignored.
Reference: Salesforce Data Cloud Field Mapping
Salesforce Data Types
Question #148
A new user of Data Cloud only needs to be able to review individual rows of ingested data and validate that it has been modeled successfully to its linked data model object. The user will also need to make changes if required.
What is the minimum permission set needed to accommodate this use case?
- A . Data Cloud for Marketing Specialist
- B . Data Cloud Admin
- C . Data Cloud User
- D . Data Cloud for Marketing Data Aware Specialist
Correct Answer: C
C
Explanation:
The Data Cloud User permission set is the minimum permission set needed to accommodate this use case. The Data Cloud User permission set grants access to the Data Explorer feature, which allows the user to review individual rows of ingested data and validate that it has been modeled successfully to its linked data model object. The user can also make changes to the data model object fields, such as adding or removing fields, changing field types, or creating formula fields. The Data Cloud User permission set does not grant access to other Data Cloud features or tasks, such as creating data streams, creating segments, creating activations, or managing users. The other permission sets are either too restrictive or too permissive for this use case. The Data Cloud for Marketing Specialist permission set only grants access to the segmentation and activation features, but not to the Data Explorer feature. The Data Cloud Admin permission set grants access to all Data Cloud features and tasks, including the Data Explorer feature, but it is more than what the user needs. The Data Cloud for Marketing Data Aware Specialist permission set grants access to the Data Explorer feature, but also to the segmentation and activation features, which are not required for this use case.
Reference: Data Cloud Standard Permission Sets, Data Explorer, Set Up Data Cloud Unit
C
Explanation:
The Data Cloud User permission set is the minimum permission set needed to accommodate this use case. The Data Cloud User permission set grants access to the Data Explorer feature, which allows the user to review individual rows of ingested data and validate that it has been modeled successfully to its linked data model object. The user can also make changes to the data model object fields, such as adding or removing fields, changing field types, or creating formula fields. The Data Cloud User permission set does not grant access to other Data Cloud features or tasks, such as creating data streams, creating segments, creating activations, or managing users. The other permission sets are either too restrictive or too permissive for this use case. The Data Cloud for Marketing Specialist permission set only grants access to the segmentation and activation features, but not to the Data Explorer feature. The Data Cloud Admin permission set grants access to all Data Cloud features and tasks, including the Data Explorer feature, but it is more than what the user needs. The Data Cloud for Marketing Data Aware Specialist permission set grants access to the Data Explorer feature, but also to the segmentation and activation features, which are not required for this use case.
Reference: Data Cloud Standard Permission Sets, Data Explorer, Set Up Data Cloud Unit
Question #149
How does identity resolution select attributes for unified individuals when there Is conflicting information in the data model?
- A . Creates additional contact points
- B . Leverages reconciliation rules
- C . Creates additional rulesets
- D . Leverages match rules
Correct Answer: B
B
Explanation:
Identity resolution is the process of creating unified profiles of individuals by matching and merging data from different sources. When there is conflicting information in the data model, such as different names, addresses, or phone numbers for the same person, identity resolution leverages reconciliation rules to select the most accurate and complete attributes for the unified profile. Reconciliation rules are configurable rules that define how to resolve conflicts based on criteria such as recency, frequency, source priority, or completeness. For example, a reconciliation rule can specify that the most recent name or the most frequent phone number should be selected for the unified profile. Reconciliation rules can be applied at the attribute level or the contact point level.
Reference: Identity Resolution, Reconciliation Rules, Salesforce Data Cloud Exam Questions
B
Explanation:
Identity resolution is the process of creating unified profiles of individuals by matching and merging data from different sources. When there is conflicting information in the data model, such as different names, addresses, or phone numbers for the same person, identity resolution leverages reconciliation rules to select the most accurate and complete attributes for the unified profile. Reconciliation rules are configurable rules that define how to resolve conflicts based on criteria such as recency, frequency, source priority, or completeness. For example, a reconciliation rule can specify that the most recent name or the most frequent phone number should be selected for the unified profile. Reconciliation rules can be applied at the attribute level or the contact point level.
Reference: Identity Resolution, Reconciliation Rules, Salesforce Data Cloud Exam Questions
Question #150
Cumulus Financial uses calculated insights to compute the total banking value per branch for its high net worth customers. In the calculated insight, "banking value" is a metric, "branch" is a dimension, and "high net worth" is a filter.
What can be included as an attribute in activation?
- A . "high net worth" (filter)
- B . "branch" (dimension) and "banking metric)
- C . "banking value" (metric)
- D . "branch" (dimension)
Correct Answer: D
D
Explanation:
According to the Salesforce Data Cloud documentation, an attribute is a dimension or a measure that can be used in activation. A dimension is a categorical variable that can be used to group or filter data, such as branch, region, or product. A measure is a numerical variable that can be used to calculate metrics, such as revenue, profit, or count. A filter is a condition that can be applied to limit the data that is used in a calculated insight, such as high net worth, age range, or gender. In this question, the calculated insight uses “banking value” as a metric, which is a measure, and “branch” as a dimension. Therefore, only “branch” can be included as an attribute in activation, since it is a dimension. The other options are either measures or filters, which are not attributes.
Reference: Data Cloud Permission Sets, Salesforce Data Cloud Exam Questions
D
Explanation:
According to the Salesforce Data Cloud documentation, an attribute is a dimension or a measure that can be used in activation. A dimension is a categorical variable that can be used to group or filter data, such as branch, region, or product. A measure is a numerical variable that can be used to calculate metrics, such as revenue, profit, or count. A filter is a condition that can be applied to limit the data that is used in a calculated insight, such as high net worth, age range, or gender. In this question, the calculated insight uses “banking value” as a metric, which is a measure, and “branch” as a dimension. Therefore, only “branch” can be included as an attribute in activation, since it is a dimension. The other options are either measures or filters, which are not attributes.
Reference: Data Cloud Permission Sets, Salesforce Data Cloud Exam Questions