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 #151
A customer requests that their personal data be deleted.
Which action should the consultant take to accommodate this request in Data Cloud?
- A . Use a streaming API call to delete the customer’s information.
- B . Use Profile Explorer to delete the customer data from Data Cloud.
- C . Use Consent API to request deletion of the customer’s information.
- D . Use the Data Rights Subject Request tool to request deletion of the customer’s information.
Correct Answer: D
Question #152
A bank collects customer data for its loan applicants and high net worth customers. A customer can be both a load applicant and a high net worth customer, resulting in duplicate data.
How should a consultant ingest and map this data in Data Cloud?
- A . Use a data transform to consolidate the data into one DLO and them map it to the individual and Contact Point Email DMOs.
- B . Ingest the data into two DLOs and map each to the individual and Contact point Email DMOs.
- C . Ingest the data into two DLOs and then map to two custom DMOs.
- D . Ingest the data into one DLO and then map to one custom DMO.
Correct Answer: B
B
Explanation:
To handle duplicate data for customers who are both loan applicants and high net worth individuals, the consultant should ingest the data into two separate Data Lake Objects (DLOs) and map them to the Individual and Contact Point Email Data Model Objects (DMOs). Here’s why and how this works: Understanding the Problem:
Customers may exist in both datasets (loan applicants and high net worth individuals), leading to potential duplication.
To avoid redundancy while maintaining data integrity, the data must be ingested and mapped carefully.
Why Two DLOs?
By ingesting the data into two DLOs, you can maintain separation between the two datasets while still leveraging shared attributes (e.g., email addresses).
Mapping both DLOs to the Individual and Contact Point Email DMOs ensures that identity resolution can consolidate duplicate records based on shared identifiers like email. Steps to Implement This Solution:
Step 1: Create two DLOs―one for loan applicants and another for high net worth customers.
Step 2: Map both DLOs to the Individual DMO to consolidate customer profiles.
Step 3: Map the email fields from both DLOs to the Contact Point Email DMO to enable identity resolution based on email addresses.
Step 4: Configure identity resolution rules to merge duplicate records based on shared attributes like email.
Why Not Other Options?
B
Explanation:
To handle duplicate data for customers who are both loan applicants and high net worth individuals, the consultant should ingest the data into two separate Data Lake Objects (DLOs) and map them to the Individual and Contact Point Email Data Model Objects (DMOs). Here’s why and how this works: Understanding the Problem:
Customers may exist in both datasets (loan applicants and high net worth individuals), leading to potential duplication.
To avoid redundancy while maintaining data integrity, the data must be ingested and mapped carefully.
Why Two DLOs?
By ingesting the data into two DLOs, you can maintain separation between the two datasets while still leveraging shared attributes (e.g., email addresses).
Mapping both DLOs to the Individual and Contact Point Email DMOs ensures that identity resolution can consolidate duplicate records based on shared identifiers like email. Steps to Implement This Solution:
Step 1: Create two DLOs―one for loan applicants and another for high net worth customers.
Step 2: Map both DLOs to the Individual DMO to consolidate customer profiles.
Step 3: Map the email fields from both DLOs to the Contact Point Email DMO to enable identity resolution based on email addresses.
Step 4: Configure identity resolution rules to merge duplicate records based on shared attributes like email.
Why Not Other Options?
Question #153
When creating a segment on an individual, what is the result of using two separate containers linked by an AND as shown below?
GoodsProduct | Count | At Least | 1
Color | Is Equal To | red
AND
GoodsProduct | Count | At Least | 1
PrimaryProductCategory | Is Equal To | shoes
- A . Individuals who purchased at least one of any red’ product and also purchased at least one pair of ‘shoes’
- B . Individuals who purchased at least one ‘red shoes’ as a single line item in a purchase
- C . Individuals who made a purchase of at least one ‘red shoes’ and nothing else
- D . Individuals who purchased at least one of any ‘red’ product or purchased at least one pair of ‘shoes’
Correct Answer: A
A
Explanation:
When creating a segment on an individual, using two separate containers linked by an AND means that the individual must satisfy both the conditions in the containers. In this case, the individual must have purchased at least one product with the color attribute equal to ‘red’ and at least one product with the primary product category attribute equal to ‘shoes’. The products do not have to be the same or purchased in the same transaction. Therefore, the correct answer is A.
The other options are incorrect because they imply different logical operators or conditions.
Option B implies that the individual must have purchased a single product that has both the color attribute equal to ‘red’ and the primary product category attribute equal to ‘shoes’.
Option C implies that the individual must have purchased only one product that has both the color attribute equal to ‘red’ and the primary product category attribute equal to ‘shoes’ and no other products.
Option D implies that the individual must have purchased either one product with the color attribute equal to ‘red’ or one product with the primary product category attribute equal to ‘shoes’ or both, which is equivalent to using an OR operator instead of an AND operator.
Reference: Create a Container for Segmentation Create a Segment in Data Cloud Navigate Data Cloud Segmentation
A
Explanation:
When creating a segment on an individual, using two separate containers linked by an AND means that the individual must satisfy both the conditions in the containers. In this case, the individual must have purchased at least one product with the color attribute equal to ‘red’ and at least one product with the primary product category attribute equal to ‘shoes’. The products do not have to be the same or purchased in the same transaction. Therefore, the correct answer is A.
The other options are incorrect because they imply different logical operators or conditions.
Option B implies that the individual must have purchased a single product that has both the color attribute equal to ‘red’ and the primary product category attribute equal to ‘shoes’.
Option C implies that the individual must have purchased only one product that has both the color attribute equal to ‘red’ and the primary product category attribute equal to ‘shoes’ and no other products.
Option D implies that the individual must have purchased either one product with the color attribute equal to ‘red’ or one product with the primary product category attribute equal to ‘shoes’ or both, which is equivalent to using an OR operator instead of an AND operator.
Reference: Create a Container for Segmentation Create a Segment in Data Cloud Navigate Data Cloud Segmentation
Question #154
Which two common use cases can be addressed with Data Cloud? Choose 2 answers
- A . Understand and act upon customer data to drive more relevant experiences.
- B . Govern enterprise data lifecycle through a centralized set of policies and processes.
- C . Harmonize data from multiple sources with a standardized and extendable data model.
- D . Safeguard critical business data by serving as a centralized system for backup and disaster recovery.
Correct Answer: A, C
A, C
Explanation:
Data Cloud is a data platform that can help customers connect, prepare, harmonize, unify, query, analyze, and act on their data across various Salesforce and external sources. Some of the common use cases that can be addressed with Data Cloud are:
Understand and act upon customer data to drive more relevant experiences. Data Cloud can help customers gain a 360-degree view of their customers by unifying data from different sources and resolving identities across channels. Data Cloud can also help customers segment their audiences, create personalized experiences, and activate data in any channel using insights and AI.
Harmonize data from multiple sources with a standardized and extendable data model. Data Cloud can help customers transform and cleanse their data before using it, and map it to a common data model that can be extended and customized. Data Cloud can also help customers create calculated insights and related attributes to enrich their data and optimize identity resolution.
The other two options are not common use cases for Data Cloud. Data Cloud does not provide data governance or backup and disaster recovery features, as these are typically handled by other Salesforce or external solutions.
Reference: Learn How Data Cloud Works
About Salesforce Data Cloud
Discover Use Cases for the Platform
Understand Common Data Analysis Use Cases
A, C
Explanation:
Data Cloud is a data platform that can help customers connect, prepare, harmonize, unify, query, analyze, and act on their data across various Salesforce and external sources. Some of the common use cases that can be addressed with Data Cloud are:
Understand and act upon customer data to drive more relevant experiences. Data Cloud can help customers gain a 360-degree view of their customers by unifying data from different sources and resolving identities across channels. Data Cloud can also help customers segment their audiences, create personalized experiences, and activate data in any channel using insights and AI.
Harmonize data from multiple sources with a standardized and extendable data model. Data Cloud can help customers transform and cleanse their data before using it, and map it to a common data model that can be extended and customized. Data Cloud can also help customers create calculated insights and related attributes to enrich their data and optimize identity resolution.
The other two options are not common use cases for Data Cloud. Data Cloud does not provide data governance or backup and disaster recovery features, as these are typically handled by other Salesforce or external solutions.
Reference: Learn How Data Cloud Works
About Salesforce Data Cloud
Discover Use Cases for the Platform
Understand Common Data Analysis Use Cases
Question #155
Northern Trail Outfitters (NTO) wants to send a promotional campaign for customers that have purchased within the past 6 months. The consultant created a segment to meet this requirement. Now, NTO brings an additional requirement to suppress customers who have made purchases within the last week.
What should the consultant use to remove the recent customers?
- A . Batch transforms
- B . Segmentation exclude rules
- C . Related attributes
- D . Streaming insight
Correct Answer: B
B
Explanation:
The consultant should use B. Segmentation exclude rules to remove the recent customers. Segmentation exclude rules are filters that can be applied to a segment to exclude records that meet certain criteria. The consultant can use segmentation exclude rules to exclude customers who have made purchases within the last week from the segment that contains customers who have purchased within the past 6 months. This way, the segment will only include customers who are eligible for the promotional campaign.
The other options are not correct.
Option A is incorrect because batch transforms are data processing tasks that can be applied to data streams or data lake objects to modify or enrich the data. Batch transforms are not used for segmentation or activation.
Option C is incorrect because related attributes are attributes that are derived from the relationships between data model objects. Related attributes are not used for excluding records from a segment.
Option D is incorrect because streaming insights are derived attributes that are calculated at the time of data ingestion. Streaming insights are not used for excluding records from a segment.
Reference: Salesforce Data Cloud Consultant Exam Guide, Segmentation, Segmentation Exclude Rules
B
Explanation:
The consultant should use B. Segmentation exclude rules to remove the recent customers. Segmentation exclude rules are filters that can be applied to a segment to exclude records that meet certain criteria. The consultant can use segmentation exclude rules to exclude customers who have made purchases within the last week from the segment that contains customers who have purchased within the past 6 months. This way, the segment will only include customers who are eligible for the promotional campaign.
The other options are not correct.
Option A is incorrect because batch transforms are data processing tasks that can be applied to data streams or data lake objects to modify or enrich the data. Batch transforms are not used for segmentation or activation.
Option C is incorrect because related attributes are attributes that are derived from the relationships between data model objects. Related attributes are not used for excluding records from a segment.
Option D is incorrect because streaming insights are derived attributes that are calculated at the time of data ingestion. Streaming insights are not used for excluding records from a segment.
Reference: Salesforce Data Cloud Consultant Exam Guide, Segmentation, Segmentation Exclude Rules
Question #156
An automotive dealership wants to implement Data Cloud.
What is a use case for Data Cloud’s capabilities?
- A . Implement a full archive solution with version management.
- B . Use browser cookies to track visitor activity on the website and display personalized recommendations.
- C . Build a source of truth for consent management across all unified individuals.
- D . Ingest customer interaction across different touch points, harmonize, and build a data model for analytical reporting.
Correct Answer: D
D
Explanation:
The most relevant use case for implementing Salesforce Data Cloud in an automotive dealership is ingesting customer interactions across different touchpoints, harmonizing the data, and building a data model for analytical reporting.
Here’s why:
D
Explanation:
The most relevant use case for implementing Salesforce Data Cloud in an automotive dealership is ingesting customer interactions across different touchpoints, harmonizing the data, and building a data model for analytical reporting.
Here’s why:
Question #157
A consultant is discussing the benefits of Data Cloud with a customer that has multiple disjointed data sources.
Which two functional areas should the consultant highlight in relation to managing customer data? Choose 2 answers
- A . Data Harmonization
- B . Unified Profiles
- C . Master Data Management
- D . Data Marketplace
Correct Answer: A, B
A, B
Explanation:
Data Cloud is an open and extensible data platform that enables smarter, more efficient AI with secure access to first-party and industry data1.
Two functional areas that the consultant should highlight in relation to managing customer data are:
Data Harmonization: Data Cloud harmonizes data from multiple sources and formats into a common schema, enabling a single source of truth for customer data1. Data Cloud also applies data quality rules and transformations to ensure data accuracy and consistency.
Unified Profiles: Data Cloud creates unified profiles of customers and prospects by linking data across different identifiers, such as email, phone, cookie, and device ID1. Unified profiles provide a holistic view of customer behavior, preferences, and interactions across channels and touchpoints. The other options are not correct because:
Master Data Management: Master Data Management (MDM) is a process of creating and maintaining a single, consistent, and trusted source of master data, such as product, customer, supplier, or location data. Data Cloud does not provide MDM functionality, but it can integrate with MDM solutions to enrich customer data.
Data Marketplace: Data Marketplace is a feature of Data Cloud that allows users to discover, access, and activate data from third-party providers, such as demographic, behavioral, and intent data. Data Marketplace is not a functional area related to managing customer data, but rather a source of external data that can enhance customer data.
Reference: Salesforce Data Cloud
[Data Harmonization for Data Cloud]
[Unified Profiles for Data Cloud]
[What is Master Data Management?]
[Integrate Data Cloud with Master Data Management]
[Data Marketplace for Data Cloud]
A, B
Explanation:
Data Cloud is an open and extensible data platform that enables smarter, more efficient AI with secure access to first-party and industry data1.
Two functional areas that the consultant should highlight in relation to managing customer data are:
Data Harmonization: Data Cloud harmonizes data from multiple sources and formats into a common schema, enabling a single source of truth for customer data1. Data Cloud also applies data quality rules and transformations to ensure data accuracy and consistency.
Unified Profiles: Data Cloud creates unified profiles of customers and prospects by linking data across different identifiers, such as email, phone, cookie, and device ID1. Unified profiles provide a holistic view of customer behavior, preferences, and interactions across channels and touchpoints. The other options are not correct because:
Master Data Management: Master Data Management (MDM) is a process of creating and maintaining a single, consistent, and trusted source of master data, such as product, customer, supplier, or location data. Data Cloud does not provide MDM functionality, but it can integrate with MDM solutions to enrich customer data.
Data Marketplace: Data Marketplace is a feature of Data Cloud that allows users to discover, access, and activate data from third-party providers, such as demographic, behavioral, and intent data. Data Marketplace is not a functional area related to managing customer data, but rather a source of external data that can enhance customer data.
Reference: Salesforce Data Cloud
[Data Harmonization for Data Cloud]
[Unified Profiles for Data Cloud]
[What is Master Data Management?]
[Integrate Data Cloud with Master Data Management]
[Data Marketplace for Data Cloud]
Question #157
A consultant is discussing the benefits of Data Cloud with a customer that has multiple disjointed data sources.
Which two functional areas should the consultant highlight in relation to managing customer data? Choose 2 answers
- A . Data Harmonization
- B . Unified Profiles
- C . Master Data Management
- D . Data Marketplace
Correct Answer: A, B
A, B
Explanation:
Data Cloud is an open and extensible data platform that enables smarter, more efficient AI with secure access to first-party and industry data1.
Two functional areas that the consultant should highlight in relation to managing customer data are:
Data Harmonization: Data Cloud harmonizes data from multiple sources and formats into a common schema, enabling a single source of truth for customer data1. Data Cloud also applies data quality rules and transformations to ensure data accuracy and consistency.
Unified Profiles: Data Cloud creates unified profiles of customers and prospects by linking data across different identifiers, such as email, phone, cookie, and device ID1. Unified profiles provide a holistic view of customer behavior, preferences, and interactions across channels and touchpoints. The other options are not correct because:
Master Data Management: Master Data Management (MDM) is a process of creating and maintaining a single, consistent, and trusted source of master data, such as product, customer, supplier, or location data. Data Cloud does not provide MDM functionality, but it can integrate with MDM solutions to enrich customer data.
Data Marketplace: Data Marketplace is a feature of Data Cloud that allows users to discover, access, and activate data from third-party providers, such as demographic, behavioral, and intent data. Data Marketplace is not a functional area related to managing customer data, but rather a source of external data that can enhance customer data.
Reference: Salesforce Data Cloud
[Data Harmonization for Data Cloud]
[Unified Profiles for Data Cloud]
[What is Master Data Management?]
[Integrate Data Cloud with Master Data Management]
[Data Marketplace for Data Cloud]
A, B
Explanation:
Data Cloud is an open and extensible data platform that enables smarter, more efficient AI with secure access to first-party and industry data1.
Two functional areas that the consultant should highlight in relation to managing customer data are:
Data Harmonization: Data Cloud harmonizes data from multiple sources and formats into a common schema, enabling a single source of truth for customer data1. Data Cloud also applies data quality rules and transformations to ensure data accuracy and consistency.
Unified Profiles: Data Cloud creates unified profiles of customers and prospects by linking data across different identifiers, such as email, phone, cookie, and device ID1. Unified profiles provide a holistic view of customer behavior, preferences, and interactions across channels and touchpoints. The other options are not correct because:
Master Data Management: Master Data Management (MDM) is a process of creating and maintaining a single, consistent, and trusted source of master data, such as product, customer, supplier, or location data. Data Cloud does not provide MDM functionality, but it can integrate with MDM solutions to enrich customer data.
Data Marketplace: Data Marketplace is a feature of Data Cloud that allows users to discover, access, and activate data from third-party providers, such as demographic, behavioral, and intent data. Data Marketplace is not a functional area related to managing customer data, but rather a source of external data that can enhance customer data.
Reference: Salesforce Data Cloud
[Data Harmonization for Data Cloud]
[Unified Profiles for Data Cloud]
[What is Master Data Management?]
[Integrate Data Cloud with Master Data Management]
[Data Marketplace for Data Cloud]
Question #159
A consultant is reviewing a recent activation using engagement-based related attributes but is not seeing any related attributes in their payload for the majority of their segment members.
Which two areas should the consultant review to help troubleshoot this issue? Choose 2 answers
- A . The related engagement events occurred within the last 90 days.
- B . The activations are referencing segments that segment on profile data rather than engagement data.
- C . The correct path is selected for the related attributes.
- D . The activated profiles have a Unified Contact Point.
Correct Answer: A C
A C
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.
Reference: Add Related Attributes to an Activation, Related Attributes in Data Cloud activation have no values, Explore the Engagement Data Model Object
A C
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.
Reference: Add Related Attributes to an Activation, Related Attributes in Data Cloud activation have no values, Explore the Engagement Data Model Object
Question #160
Cumulus Financial wants its service agents to view a display of all cases associated with a Unified Individual on a contact record.
Which two features should a consultant consider for this use case? Choose 2 answers
- A . Data Action
- B . Profile API
- C . Lightning Web Components
- D . Query APL
Correct Answer: B, C
B, C
Explanation:
A Unified Individual is a profile that combines data from multiple sources using identity resolution rules in Data Cloud. A Unified Individual can have multiple contact points, such as email, phone, or address, that link to different systems and records.
A consultant can use the following features to display all cases associated with a Unified Individual on a contact record:
Profile API: This is a REST API that allows you to retrieve and update Unified Individual profiles and related attributes in Data Cloud. You can use the Profile API to query the cases that are related to a Unified Individual by using the contact point ID or the unified ID as a filter. You can also use the Profile API to update the Unified Individual profile with new or modified case information from other systems.
Lightning Web Components: These are custom HTML elements that you can use to create reusable UI components for your Salesforce apps. You can use Lightning Web Components to create a custom component that displays the cases related to a Unified Individual on a contact record. You can use the Profile API to fetch the data from Data Cloud and display it in a table, list, or chart format. You can also use Lightning Web Components to enable actions, such as creating, editing, or deleting cases, from the contact record.
The other two options are not relevant for this use case. A Data Action is a type of action that executes a flow, a data action target, or a data action script when an insight is triggered. A Data Action is used for activation and personalization, not for displaying data on a contact record. A Query APL is a query language that allows you to access and manipulate data in Data Cloud. A Query APL is used for data exploration and analysis, not for displaying data on a contact record.
Reference: Profile API Developer Guide, Lightning Web Components Developer Guide, Create Unified Individual Profiles Unit
B, C
Explanation:
A Unified Individual is a profile that combines data from multiple sources using identity resolution rules in Data Cloud. A Unified Individual can have multiple contact points, such as email, phone, or address, that link to different systems and records.
A consultant can use the following features to display all cases associated with a Unified Individual on a contact record:
Profile API: This is a REST API that allows you to retrieve and update Unified Individual profiles and related attributes in Data Cloud. You can use the Profile API to query the cases that are related to a Unified Individual by using the contact point ID or the unified ID as a filter. You can also use the Profile API to update the Unified Individual profile with new or modified case information from other systems.
Lightning Web Components: These are custom HTML elements that you can use to create reusable UI components for your Salesforce apps. You can use Lightning Web Components to create a custom component that displays the cases related to a Unified Individual on a contact record. You can use the Profile API to fetch the data from Data Cloud and display it in a table, list, or chart format. You can also use Lightning Web Components to enable actions, such as creating, editing, or deleting cases, from the contact record.
The other two options are not relevant for this use case. A Data Action is a type of action that executes a flow, a data action target, or a data action script when an insight is triggered. A Data Action is used for activation and personalization, not for displaying data on a contact record. A Query APL is a query language that allows you to access and manipulate data in Data Cloud. A Query APL is used for data exploration and analysis, not for displaying data on a contact record.
Reference: Profile API Developer Guide, Lightning Web Components Developer Guide, Create Unified Individual Profiles Unit