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 #91
A customer notices that their consolidation rate is low across their account unification. They have mapped Account to the Individual and Contact Point Email DMOs.
What should they do to increase their consolidation rate?
- A . Change reconciliation rules to Most Occurring.
- B . Disable the individual identity ruleset.
- C . Increase the number of matching rules.
- D . Update their account address details in the data source
Correct Answer: C
C
Explanation:
Consolidation Rate: The consolidation rate in Salesforce Data Cloud refers to the effectiveness of unifying records into a single profile. A low consolidation rate indicates that many records are not being successfully unified.
Matching Rules: Matching rules are critical in the identity resolution process. They define the criteria for identifying and merging duplicate records.
Solution:
Increase Matching Rules: Adding more matching rules improves the system’s ability to identify duplicate records. This includes matching on additional fields or using more sophisticated matching algorithms.
Steps:
Access the Identity Resolution settings in Data Cloud.
Review the current matching rules.
Add new rules that consider more fields such as phone number, address, or other unique identifiers.
Benefits:
Improved Unification: Higher accuracy in matching and merging records, leading to a higher consolidation rate.
Comprehensive Profiles: Enhanced customer profiles with consolidated data from multiple sources.
Reference: Salesforce Data Cloud Identity Resolution
Salesforce Help: Matching Rules
C
Explanation:
Consolidation Rate: The consolidation rate in Salesforce Data Cloud refers to the effectiveness of unifying records into a single profile. A low consolidation rate indicates that many records are not being successfully unified.
Matching Rules: Matching rules are critical in the identity resolution process. They define the criteria for identifying and merging duplicate records.
Solution:
Increase Matching Rules: Adding more matching rules improves the system’s ability to identify duplicate records. This includes matching on additional fields or using more sophisticated matching algorithms.
Steps:
Access the Identity Resolution settings in Data Cloud.
Review the current matching rules.
Add new rules that consider more fields such as phone number, address, or other unique identifiers.
Benefits:
Improved Unification: Higher accuracy in matching and merging records, leading to a higher consolidation rate.
Comprehensive Profiles: Enhanced customer profiles with consolidated data from multiple sources.
Reference: Salesforce Data Cloud Identity Resolution
Salesforce Help: Matching Rules
Question #92
Luxury Retailers created a segment targeting high value customers that it activates through Marketing Cloud for email communication. The company notices that the activated count is smaller than the segment count.
What is a reason for this?
- A . Data Cloud enforces the presence of Contact Point for Marketing Cloud activations. If the individual does not have a related Contact Point, it will not be activated.
- B . Marketing Cloud activations automatically suppress individuals who are unengaged and have not opened or clicked on an email in the last six months.
- C . Marketing Cloud activations only activate those individuals that already exist in Marketing Cloud.
They do not allow activation of new records. - D . Marketing Cloud activations apply a frequency cap and limit the number of records that can be sent in an activation.
Correct Answer: A
A
Explanation:
The reason for the activated count being smaller than the segment count is A. Data Cloud enforces the presence of Contact Point for Marketing Cloud activations. If the individual does not have a related Contact Point, it will not be activated. A Contact Point is a data model object that represents a channel or method of communication with an individual, such as email, phone, or social media.
For Marketing Cloud activations, Data Cloud requires that the individual has a related Contact Point of type Email, which contains a valid email address. If the individual does not have such a Contact Point, or if the Contact Point is missing or invalid, the individual will not be activated and will not receive the email communication. Therefore, the activated count may be lower than the segment count, depending on how many individuals in the segment have a valid email Contact
Point.
Reference: Salesforce Data Cloud Consultant Exam Guide, Contact Point, Marketing Cloud Activation
A
Explanation:
The reason for the activated count being smaller than the segment count is A. Data Cloud enforces the presence of Contact Point for Marketing Cloud activations. If the individual does not have a related Contact Point, it will not be activated. A Contact Point is a data model object that represents a channel or method of communication with an individual, such as email, phone, or social media.
For Marketing Cloud activations, Data Cloud requires that the individual has a related Contact Point of type Email, which contains a valid email address. If the individual does not have such a Contact Point, or if the Contact Point is missing or invalid, the individual will not be activated and will not receive the email communication. Therefore, the activated count may be lower than the segment count, depending on how many individuals in the segment have a valid email Contact
Point.
Reference: Salesforce Data Cloud Consultant Exam Guide, Contact Point, Marketing Cloud Activation
Question #93
Cloud Kicks received a Request to be Forgotten by a customer.
In which two ways should a consultant use Data Cloud to honor this request? Choose 2 answers
- A . Delete the data from the incoming data stream and perform a full refresh.
- B . Add the Individual ID to a headerless file and use the delete from file functionality.
- C . Use Data Explorer to locate and manually remove the Individual.
- D . Use the Consent API to suppress processing and delete the Individual and related records from source data streams.
Correct Answer: B, D
B, D
Explanation:
: To honor a Request to be Forgotten by a customer, a consultant should use Data Cloud in two ways: Add the Individual ID to a headerless file and use the delete from file functionality. This option allows the consultant to delete multiple Individuals from Data Cloud by uploading a CSV file with their IDs1. The deletion process is asynchronous and can take up to 24 hours to complete1.
Use the Consent API to suppress processing and delete the Individual and related records from source data streams. This option allows the consultant to submit a Data Deletion request for an Individual profile in Data Cloud using the Consent API2. A Data Deletion request deletes the specified Individual entity and any entities where a relationship has been defined between that entity’s identifying attribute and the Individual ID attribute2. The deletion process is reprocessed at 30, 60, and 90 days to ensure a full deletion2. The other options are not correct because:
Deleting the data from the incoming data stream and performing a full refresh will not delete the existing data in Data Cloud, only the new data from the source system3.
Using Data Explorer to locate and manually remove the Individual will not delete the related records from the source data streams, only the Individual entity in Data Cloud.
Reference: Delete Individuals from Data Cloud
Requesting Data Deletion or Right to Be Forgotten Data Refresh for Data Cloud
[Data Explorer]
B, D
Explanation:
: To honor a Request to be Forgotten by a customer, a consultant should use Data Cloud in two ways: Add the Individual ID to a headerless file and use the delete from file functionality. This option allows the consultant to delete multiple Individuals from Data Cloud by uploading a CSV file with their IDs1. The deletion process is asynchronous and can take up to 24 hours to complete1.
Use the Consent API to suppress processing and delete the Individual and related records from source data streams. This option allows the consultant to submit a Data Deletion request for an Individual profile in Data Cloud using the Consent API2. A Data Deletion request deletes the specified Individual entity and any entities where a relationship has been defined between that entity’s identifying attribute and the Individual ID attribute2. The deletion process is reprocessed at 30, 60, and 90 days to ensure a full deletion2. The other options are not correct because:
Deleting the data from the incoming data stream and performing a full refresh will not delete the existing data in Data Cloud, only the new data from the source system3.
Using Data Explorer to locate and manually remove the Individual will not delete the related records from the source data streams, only the Individual entity in Data Cloud.
Reference: Delete Individuals from Data Cloud
Requesting Data Deletion or Right to Be Forgotten Data Refresh for Data Cloud
[Data Explorer]
Question #94
Northern Trail Outfitters uploads new customer data to an Amazon S3 Bucket on a daily basis to be ingested in Data Cloud.
In what order should each process be run to ensure that freshly imported data is ready and available to use for any segment?
- A . Calculated Insight > Refresh Data Stream > Identity Resolution
- B . Refresh Data Stream > Calculated Insight > Identity Resolution
- C . Identity Resolution > Refresh Data Stream > Calculated Insight
- D . Refresh Data Stream > Identity Resolution > Calculated Insight
Correct Answer: D
D
Explanation:
To ensure that freshly imported data from an Amazon S3 Bucket is ready and available to use for any segment, the following processes should be run in this order:
Refresh Data Stream: This process updates the data lake objects in Data Cloud with the latest data from the source system. It can be configured to run automatically or manually, depending on the data stream settings1. Refreshing the data stream ensures that Data Cloud has the most recent and accurate data from the Amazon S3 Bucket.
Identity Resolution: This process creates unified individual profiles by matching and consolidating source profiles from different data streams based on the identity resolution ruleset. It runs daily by default, but can be triggered manually as well2. Identity resolution ensures that Data Cloud has a single view of each customer across different data sources.
Calculated Insight: This process performs calculations on data lake objects or CRM data and returns a result as a new data object. It can be used to create metrics or measures for segmentation or analysis purposes3. Calculated insights ensure that Data Cloud has the derived data that can be used for personalization or activation.
Reference:
1: Configure Data Stream Refresh and Frequency – Salesforce
2: Identity Resolution Ruleset Processing Results – Salesforce
3: Calculated Insights – Salesforce
D
Explanation:
To ensure that freshly imported data from an Amazon S3 Bucket is ready and available to use for any segment, the following processes should be run in this order:
Refresh Data Stream: This process updates the data lake objects in Data Cloud with the latest data from the source system. It can be configured to run automatically or manually, depending on the data stream settings1. Refreshing the data stream ensures that Data Cloud has the most recent and accurate data from the Amazon S3 Bucket.
Identity Resolution: This process creates unified individual profiles by matching and consolidating source profiles from different data streams based on the identity resolution ruleset. It runs daily by default, but can be triggered manually as well2. Identity resolution ensures that Data Cloud has a single view of each customer across different data sources.
Calculated Insight: This process performs calculations on data lake objects or CRM data and returns a result as a new data object. It can be used to create metrics or measures for segmentation or analysis purposes3. Calculated insights ensure that Data Cloud has the derived data that can be used for personalization or activation.
Reference:
1: Configure Data Stream Refresh and Frequency – Salesforce
2: Identity Resolution Ruleset Processing Results – Salesforce
3: Calculated Insights – Salesforce
Question #95
A global fashion retailer operates online sales platforms across AMFR, FMFA, and APAC. the data formats for customer, order, and product Information vary by region, and compliance regulations require data to remain unchanged in the original data sources They also require a unified view of customer profiles for real-time personalization and analytics.
Given these requirement, which transformation approach should the company implement to standardise and cleanse incoming data streams?
- A . Implement streaming data transformations.
- B . Implement batch data transformations.
- C . Transform data before ingesting into Data Cloud.
- D . Use Apex to transform and cleanse data.
Correct Answer: B
B
Explanation:
Given the requirements to standardize and cleanse incoming data streams while keeping the original data unchanged in compliance with regional regulations, the best approach is to implement batch data transformations. Here’s why:
Understanding the Requirements
The global fashion retailer operates across multiple regions (AMER, EMEA, APAC), each with varying data formats for customer, order, and product information.
Compliance regulations require the original data to remain unchanged in the source systems.
The company needs a unified view of customer profiles for real-time personalization and analytics.
Why Batch Data Transformations?
Batch Transformations for Standardization:
Batch data transformations allow you to process large volumes of data at scheduled intervals. They can standardize and cleanse data (e.g., converting different date formats, normalizing product names) without altering the original data in the source systems. Compliance with Regulations:
Since the original data remains unchanged in the source systems, batch transformations comply with regional regulations.
The transformed data is stored in a separate layer (e.g., a new Data Lake Object or Unified Profile) for downstream use.
Unified Customer Profiles:
After transformation, the cleansed and standardized data can be used to create a unified view of customer profiles in Salesforce Data Cloud.
This enables real-time personalization and analytics across regions.
Steps to Implement This Solution
Step 1: Identify Transformation Needs
Analyze the differences in data formats across regions (e.g., date formats, currency, product IDs). Define the rules for standardization and cleansing (e.g., convert all dates to ISO format, normalize product names).
Step 2: Create Batch Transformations
Use Data Cloud’s Batch Transform feature to apply the defined rules to incoming data streams.
Schedule the transformations to run at regular intervals (e.g., daily or hourly).
Step 3: Store Transformed Data Separately
Store the transformed data in a new Data Lake Object (DLO) or Unified Profile.
Ensure the original data remains untouched in the source systems.
Step 4: Enable Unified Profiles
Use the transformed data to create a unified view of customer profiles in Salesforce Data Cloud.
Leverage this unified view for real-time personalization and analytics.
Why Not Other Options?
B
Explanation:
Given the requirements to standardize and cleanse incoming data streams while keeping the original data unchanged in compliance with regional regulations, the best approach is to implement batch data transformations. Here’s why:
Understanding the Requirements
The global fashion retailer operates across multiple regions (AMER, EMEA, APAC), each with varying data formats for customer, order, and product information.
Compliance regulations require the original data to remain unchanged in the source systems.
The company needs a unified view of customer profiles for real-time personalization and analytics.
Why Batch Data Transformations?
Batch Transformations for Standardization:
Batch data transformations allow you to process large volumes of data at scheduled intervals. They can standardize and cleanse data (e.g., converting different date formats, normalizing product names) without altering the original data in the source systems. Compliance with Regulations:
Since the original data remains unchanged in the source systems, batch transformations comply with regional regulations.
The transformed data is stored in a separate layer (e.g., a new Data Lake Object or Unified Profile) for downstream use.
Unified Customer Profiles:
After transformation, the cleansed and standardized data can be used to create a unified view of customer profiles in Salesforce Data Cloud.
This enables real-time personalization and analytics across regions.
Steps to Implement This Solution
Step 1: Identify Transformation Needs
Analyze the differences in data formats across regions (e.g., date formats, currency, product IDs). Define the rules for standardization and cleansing (e.g., convert all dates to ISO format, normalize product names).
Step 2: Create Batch Transformations
Use Data Cloud’s Batch Transform feature to apply the defined rules to incoming data streams.
Schedule the transformations to run at regular intervals (e.g., daily or hourly).
Step 3: Store Transformed Data Separately
Store the transformed data in a new Data Lake Object (DLO) or Unified Profile.
Ensure the original data remains untouched in the source systems.
Step 4: Enable Unified Profiles
Use the transformed data to create a unified view of customer profiles in Salesforce Data Cloud.
Leverage this unified view for real-time personalization and analytics.
Why Not Other Options?
Question #96
A user Is not seeing suggested values from newly-modeled data when building a segment.
What is causing this issue?
- A . Value suggestion will only return results for the first 50 values of a specific attribute,
- B . Value suggestion can only work on direct attributes and not related attributes.
- C . Value suggestion requires Data Aware Specialist permissions at a minimum.
- D . Value suggestion is still processing and takes up to 24 hours to be available.
Correct Answer: D
D
Explanation:
The most likely cause of this issue is that value suggestion is still processing and takes up to 24 hours to be available. Value suggestion is a feature that enables you to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature needs to be enabled for each DMO field, and it can take up to 24 hours for the suggested values to appear after enabling the feature1. Therefore, if a user is not seeing suggested values from newly-modeled data, it could be that the data has not been processed yet by the value suggestion feature.
Reference: Use Value Suggestions in Segmentation
D
Explanation:
The most likely cause of this issue is that value suggestion is still processing and takes up to 24 hours to be available. Value suggestion is a feature that enables you to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature needs to be enabled for each DMO field, and it can take up to 24 hours for the suggested values to appear after enabling the feature1. Therefore, if a user is not seeing suggested values from newly-modeled data, it could be that the data has not been processed yet by the value suggestion feature.
Reference: Use Value Suggestions in Segmentation
Question #96
A user Is not seeing suggested values from newly-modeled data when building a segment.
What is causing this issue?
- A . Value suggestion will only return results for the first 50 values of a specific attribute,
- B . Value suggestion can only work on direct attributes and not related attributes.
- C . Value suggestion requires Data Aware Specialist permissions at a minimum.
- D . Value suggestion is still processing and takes up to 24 hours to be available.
Correct Answer: D
D
Explanation:
The most likely cause of this issue is that value suggestion is still processing and takes up to 24 hours to be available. Value suggestion is a feature that enables you to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature needs to be enabled for each DMO field, and it can take up to 24 hours for the suggested values to appear after enabling the feature1. Therefore, if a user is not seeing suggested values from newly-modeled data, it could be that the data has not been processed yet by the value suggestion feature.
Reference: Use Value Suggestions in Segmentation
D
Explanation:
The most likely cause of this issue is that value suggestion is still processing and takes up to 24 hours to be available. Value suggestion is a feature that enables you to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature needs to be enabled for each DMO field, and it can take up to 24 hours for the suggested values to appear after enabling the feature1. Therefore, if a user is not seeing suggested values from newly-modeled data, it could be that the data has not been processed yet by the value suggestion feature.
Reference: Use Value Suggestions in Segmentation
Question #98
A consultant is planning the ingestion of a data stream that has profile information including a mobile phone number.
To ensure that the phone number can be used for future SMS campaigns, they need to confirm the phone number field is in the proper E164 Phone Number format. However, the phone numbers in the file appear to be in varying formats.
What is the most efficient way to guarantee that the various phone number formats are standardized?
- A . Create a formula field to standardize the format.
- B . Edit and update the data in the source system prior to sending to Data Cloud.
- C . Assign the PhoneNumber field type when creating the data stream.
- D . Create a calculated insight after ingestion.
Correct Answer: C
C
Explanation:
The most efficient way to guarantee that the various phone number formats are standardized is to assign the PhoneNumber field type when creating the data stream. The PhoneNumber field type is a special field type that automatically converts phone numbers into the E164 format, which is the international standard for phone numbers. The E164 format consists of a plus sign (+), the country code, and the national number. For example, +1-202-555-1234 is the E164 format for a US phone number. By using the PhoneNumber field type, the consultant can ensure that the phone numbers are consistent and can be used for future SMS campaigns. The other options are either more time-consuming, require manual intervention, or do not address the formatting issue.
Reference: Data Stream Field Types, E164 Phone Number Format, Salesforce Data Cloud Exam Questions
C
Explanation:
The most efficient way to guarantee that the various phone number formats are standardized is to assign the PhoneNumber field type when creating the data stream. The PhoneNumber field type is a special field type that automatically converts phone numbers into the E164 format, which is the international standard for phone numbers. The E164 format consists of a plus sign (+), the country code, and the national number. For example, +1-202-555-1234 is the E164 format for a US phone number. By using the PhoneNumber field type, the consultant can ensure that the phone numbers are consistent and can be used for future SMS campaigns. The other options are either more time-consuming, require manual intervention, or do not address the formatting issue.
Reference: Data Stream Field Types, E164 Phone Number Format, Salesforce Data Cloud Exam Questions
Question #99
A user is not seeing suggested values from newly-modeled data when building a segment.
What is causing this issue?
- A . Value suggestion is still processing and to be available.
- B . Value suggestion requires Data Aware Specialist permissions at a minimum.
- C . Value suggestion can only work on direct attributes and not related attributes.
- D . Value suggestion will only return result for the first 50 values of a specific attribute.
Correct Answer: A
A
Explanation:
: Value suggestion is a feature that allows users to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature can take up to 24 hours to process and display the values for newly-modeled data. Therefore, if a user is not seeing suggested values from newly-modeled data, it is likely that the value suggestion is still processing and will be available soon. The other options are incorrect because value suggestion does not require any specific permissions, can work on both direct and related attributes, and can return more than 50 values for a specific attribute, depending on the data type and frequency of the values.
Reference: Use Value Suggestions in Segmentation, Data Cloud Limits and Guidelines
A
Explanation:
: Value suggestion is a feature that allows users to see suggested values for data model object (DMO) fields when creating segment filters. However, this feature can take up to 24 hours to process and display the values for newly-modeled data. Therefore, if a user is not seeing suggested values from newly-modeled data, it is likely that the value suggestion is still processing and will be available soon. The other options are incorrect because value suggestion does not require any specific permissions, can work on both direct and related attributes, and can return more than 50 values for a specific attribute, depending on the data type and frequency of the values.
Reference: Use Value Suggestions in Segmentation, Data Cloud Limits and Guidelines
Question #100
Luxury Retailers created a segment targeting high value customers that it activates through
Marketing Cloud for email communication. The company notices that the activated count is smaller
than the segment count.
What is a reason for this?
- A . Marketing Cloud activations apply a frequency cap and limit the number of records that can be sent in an activation.
- B . Data Cloud enforces the presence of Contact Point for Marketing Cloud activations. If the individual does not have a related Contact Point, it will not be activated.
- C . Marketing Cloud activations automatically suppress individuals who are unengaged and have not opened or clicked on an email in the last six months.
- D . Marketing Cloud activations only activate those individuals that already exist in Marketing Cloud.
They do not allow activation of new records.
Correct Answer: B
B
Explanation:
Data Cloud requires a Contact Point for Marketing Cloud activations, which is a record that links an individual to an email address. This ensures that the individual has given consent to receive email communications and that the email address is valid. If the individual does not have a related Contact Point, they will not be activated in Marketing Cloud. This may result in a lower activated count than the segment count.
Reference: Data Cloud Activation, Contact Point for Marketing Cloud
B
Explanation:
Data Cloud requires a Contact Point for Marketing Cloud activations, which is a record that links an individual to an email address. This ensures that the individual has given consent to receive email communications and that the email address is valid. If the individual does not have a related Contact Point, they will not be activated in Marketing Cloud. This may result in a lower activated count than the segment count.
Reference: Data Cloud Activation, Contact Point for Marketing Cloud