Data-Con-101 — Salesforce Certified Data Cloud Consultant

Full question text, answer options, and explanations for this practice set — a spoiler-free alternative is the interactive quiz above for scored, shuffled practice.

1. 1. What is the primary purpose of Salesforce Data Cloud?

   • A. To replace Salesforce CRM with a data warehouse solution
   • B. To unify customer data from multiple sources into a single, real-time customer profile and enable activation across channels(correct)
   • C. To provide ETL (Extract, Transform, Load) capabilities for migrating data between Salesforce orgs
   • D. To host and serve static marketing content to website visitors

   Explanation: Salesforce Data Cloud is a real-time data platform that ingests, harmonizes, and unifies customer data from multiple sources (CRM, web, mobile, third-party) into a unified customer profile. These profiles power intelligent segmentation, personalized activation across marketing/sales/service channels, and AI-powered insights. It is a customer data platform (CDP), not a CRM replacement or traditional ETL tool.

2. 2. In Data Cloud, what is a Data Model Object (DMO)?

   • A. A Salesforce custom object created to store data from external sources
   • B. A standardized schema entity in the Data Cloud data model that ingested data is mapped to for harmonization(correct)
   • C. A machine learning model for predicting customer behavior
   • D. A metadata object that controls data retention policies in Data Cloud

   Explanation: Data Model Objects (DMOs) are the standardized schema entities in the Data Cloud data model. When external data is ingested as Data Streams, it is mapped to DMOs through field mapping. DMOs represent standard concepts like Individual (person), Contact Point Email, Unified Individual, and custom domain-specific objects. Mapping data to DMOs is the harmonization step that enables cross-source identity resolution and segmentation.

3. 3. Which two types of data can be ingested into Salesforce Data Cloud? (Choose 2)

   • A. Salesforce CRM data from the same org (Account, Contact, Opportunity records via the CRM Connector)(correct)
   • B. Streaming event data in real time from web and mobile applications via the Data Cloud Ingestion API(correct)
   • C. Live financial market data streamed directly from stock exchanges
   • D. Data Cloud can only ingest data from Salesforce Marketing Cloud

   Explanation: Data Cloud supports multiple ingestion patterns: (1) Salesforce CRM data from the same org using the Salesforce CRM Connector (native connection, no ETL required); (2) Real-time streaming event data via the Data Cloud Ingestion API (for web clicks, mobile interactions, point-of-sale events). Other supported sources include cloud storage (S3), external CDPs, Marketing Cloud, and third-party connectors. Live financial market data requires a custom connector.

4. 4. A company has multiple Salesforce orgs (Sales Cloud, Service Cloud, B2B Commerce). How does Data Cloud ingest data from all three?

   • A. Each org's data must be exported to CSV files and uploaded to Data Cloud manually
   • B. Data Cloud connects to multiple Salesforce orgs simultaneously using the Salesforce CRM Connector configured for each org(correct)
   • C. Only one Salesforce org can be connected to Data Cloud at a time
   • D. An intermediate MuleSoft integration is required to combine data before sending to Data Cloud

   Explanation: Data Cloud supports connecting to multiple Salesforce orgs using the Salesforce CRM Connector. Each connected org is configured as a separate connector source, and Data Streams are created for each object from each org. Data Cloud then harmonizes and unifies the data across all connected orgs. This multi-org connectivity is a key architectural feature for enterprise customers with org proliferation.

5. 5. In Salesforce Data Cloud, what is the 'Unified Individual'?

   • A. A Data Cloud user account for accessing the admin console
   • B. A consolidated customer profile created by resolving and merging identity records from multiple data sources into a single golden record(correct)
   • C. A Salesforce Contact record linked to Data Cloud
   • D. An individual field mapping rule applied during data stream setup

   Explanation: The Unified Individual is the central concept in Data Cloud: a golden record representing a real-world person, created by the Identity Resolution process that matches and merges individual records from multiple sources (CRM Contact, website visitor, email subscriber, etc.) into a single, comprehensive customer profile. The Unified Individual aggregates all associated contact points, behaviors, and attributes for that person.

6. 6. A Data Cloud consultant is designing the solution architecture. Which two layers does Data Cloud's architecture comprise? (Choose 2)

   • A. Ingestion and harmonization layer — where raw data from sources is standardized to the Data Cloud data model(correct)
   • B. Physical storage layer — a proprietary Salesforce data lake managed by the customer on their own infrastructure
   • C. Insight and action layer — where unified profiles are segmented, insights are derived, and data is activated to external systems(correct)
   • D. Reporting layer — where standard Salesforce Reports and Dashboards analyze Data Cloud data

   Explanation: Data Cloud's architecture includes an ingestion/harmonization layer (data streams flow in, are mapped to DMOs, and harmonized into a unified model) and an insight/action layer (segments are built from unified profiles, Einstein AI insights are derived, and data is activated to destinations). The underlying storage is Salesforce-managed (not customer-managed on-premise). Standard Salesforce Reports cannot directly query Data Cloud objects.

7. 7. What is a Data Stream in Salesforce Data Cloud?

   • A. A real-time notification sent to external systems when a Data Cloud record changes
   • B. A configured data pipeline that brings data from a source into Data Cloud, including field mappings and refresh schedule(correct)
   • C. A SOQL query that extracts data from Salesforce objects for Data Cloud
   • D. A segment of customers defined by behavioral attributes

   Explanation: A Data Stream in Data Cloud is a configured ingestion pipeline that defines: the data source (Salesforce CRM connector, S3, Ingestion API, etc.), the object or file being ingested, field mappings to Data Model Objects, refresh frequency (real-time, every hour, daily), and category (Engagement, Profile, Other). Each Data Stream brings a specific dataset from a source into Data Cloud.

8. 8. When setting up a Data Stream from a Salesforce CRM Connector, which field mapping step is required for identity resolution to work correctly?

   • A. Mapping all fields to a single flat DMO
   • B. Mapping the unique person identifier field (e.g., Email, Phone) to a Contact Point DMO (Contact Point Email or Contact Point Phone)(correct)
   • C. Mapping the Salesforce record ID to the Data Cloud Primary Key field
   • D. No field mapping is required — Data Cloud auto-detects identity fields

   Explanation: For identity resolution to link records across sources, each Data Stream must have its person identifier fields (email, phone, name, address) mapped to the appropriate Contact Point DMO (Contact Point Email, Contact Point Phone) or the Individual DMO. These contact points are the identifiers the Identity Resolution Ruleset uses to match and link records to a Unified Individual. Without this mapping, records cannot be resolved across sources.

9. 9. A consultant is setting up a Data Stream from Amazon S3. Which two configurations are required? (Choose 2)

   • A. Configuring an S3 Connected Data Source in Data Cloud with the bucket name, region, and IAM credentials(correct)
   • B. Defining the Data Stream's schema by mapping S3 CSV column headers to Data Cloud DMO fields(correct)
   • C. Creating a Salesforce Custom Object to receive the S3 data before it flows to Data Cloud
   • D. Enabling the 'S3 Bridge' feature in the Salesforce org's connected app settings

   Explanation: Setting up an S3 Data Stream requires: (1) Creating a Connected Data Source for S3 with the bucket configuration and IAM access credentials; (2) Configuring the Data Stream by mapping the CSV file's column headers to the appropriate DMO fields in the Data Cloud schema. Data does not flow through Salesforce Custom Objects — it goes directly into Data Cloud. There is no 'S3 Bridge' feature.

10. 10. A company sends real-time mobile app events (product views, add-to-cart) to Data Cloud. Which ingestion method supports sub-second real-time streaming?

    • A. S3 bucket polling on a 15-minute refresh schedule
    • B. Salesforce CRM Connector with incremental refresh
    • C. Data Cloud Ingestion API with streaming data bundles(correct)
    • D. Marketing Cloud Contact Builder synchronization

    Explanation: The Data Cloud Ingestion API supports real-time streaming ingestion — events can be sent directly from mobile apps, websites, or IoT devices via REST API calls and are processed in near real-time. This is the appropriate method for high-frequency behavioral event streams like product views and cart interactions. S3 polling and CRM connector refreshes operate on scheduled intervals (minutes to hours), not sub-second.

11. 11. In the Data Cloud data model, what is the difference between an 'Engagement' category data stream and a 'Profile' category data stream?

    • A. Engagement streams contain time-series behavioral events (clicks, opens, purchases); Profile streams contain relatively static person attributes (name, address, preferences)(correct)
    • B. Engagement streams are for B2C data; Profile streams are for B2B data
    • C. Engagement streams are processed in real time; Profile streams are batch-only
    • D. There is no functional difference; both categories are for organizational purposes only

    Explanation: Data Cloud categorizes Data Streams by their data type: Engagement (time-stamped behavioral events — email opens, web clicks, transactions) and Profile (relatively static identity and preference attributes — name, contact info, demographics, account details). This categorization affects how the Identity Resolution process uses the data and how segments are built (behavioral engagement vs. profile attributes). Other category is available for data that doesn't fit these two.

12. 12. A consultant is mapping ingested CRM Contact data to the Data Cloud data model. Which two standard DMOs should Contact fields be mapped to? (Choose 2)

    • A. Individual DMO — for person identity attributes (First Name, Last Name, Birthdate)(correct)
    • B. Contact Point Email DMO — for email address fields to be used in identity resolution(correct)
    • C. Unified Individual DMO — directly mapped during ingestion
    • D. Party DMO — for all Salesforce Account data

    Explanation: When mapping CRM Contact data to Data Cloud, the standard mapping is: person identity attributes (First Name, Last Name, Birthdate, External ID) map to the Individual DMO; contact point identifiers (Email address, Phone number, Mailing address) map to their respective Contact Point DMOs (Contact Point Email, Contact Point Phone, Contact Point Address). The Unified Individual is created by Identity Resolution from these ingested records — it is not directly mapped. The Party DMO is for organizations/accounts, not individual people.

13. 13. A company ingests Salesforce Contact and Marketing Cloud email engagement data into Data Cloud. After field mapping, which process creates the unified customer profile?

    • A. Data Stream refresh runs automatically merge all matching records
    • B. Identity Resolution runs against the ingested data using configured match rules to create Unified Individuals(correct)
    • C. A manual merge operation performed by the Data Cloud admin
    • D. The Salesforce CRM Connector automatically deduplicates records during ingestion

    Explanation: Identity Resolution is the process in Data Cloud that analyzes ingested Individual and Contact Point records, applies configured match rules (fuzzy name match, email match, phone match), and groups matching records into a Unified Individual. This is a scheduled process that runs after data ingestion. Merge logic (survivorship rules) determines which field values from source records populate the Unified Individual. Deduplication does not happen automatically during ingestion.

14. 14. In Data Cloud Identity Resolution, what is a 'Match Rule'?

    • A. A rule that determines which field's value is retained on the Unified Individual when source records conflict
    • B. A criteria-based rule that determines when two Individual records represent the same real-world person and should be linked(correct)
    • C. A rule controlling which users can view Unified Individual records
    • D. A data quality rule that rejects records missing required identity fields

    Explanation: Match Rules in Identity Resolution define the criteria for determining when two Individual records from different sources represent the same real person. Match Rules are based on combinations of contact point matches (exact email match, exact phone match, fuzzy name + address match, etc.) and are assigned match rates. When records meet a Match Rule, they are linked to the same Unified Individual. Survivorship rules (not match rules) determine which field values are retained.

15. 15. After Identity Resolution runs, a consultant notices that some Unified Individuals contain records that should not be merged (false matches). How can this be addressed?

    • A. Delete the incorrectly merged Unified Individual records manually
    • B. Tighten the Match Rule criteria (e.g., require more matching fields, use exact match instead of fuzzy) and re-run Identity Resolution(correct)
    • C. Add a Validation Rule on the Individual DMO to prevent false matches
    • D. Enable 'Block Merge' on the incorrectly matched Contact Points

    Explanation: False matches in Identity Resolution are caused by Match Rules that are too permissive. The solution is to refine the Match Rules — either by requiring more fields to match simultaneously (e.g., require name AND email AND phone instead of just email), increasing the match threshold for fuzzy matches, or switching from fuzzy to exact matching for high-accuracy scenarios. After tightening the rules, Identity Resolution is re-run to produce a cleaner resolution.

16. 16. Identity Resolution creates Unified Individuals. Which two mechanisms control which field value is used on the Unified Individual when multiple source records have different values for the same attribute? (Choose 2)

    • A. Reconciliation Rules (Survivorship Rules) — e.g., 'Use the value from the most recently updated source record'(correct)
    • B. Source Priority rules — e.g., 'Prefer the value from CRM over Marketing Cloud when both have a value'(correct)
    • C. Alphabetical ordering — Data Cloud automatically picks the alphabetically first value
    • D. The Unified Individual always uses the value from the first-ingested source regardless of updates

    Explanation: When Identity Resolution merges records that have different values for the same attribute (e.g., two sources have different phone numbers for the same person), Reconciliation/Survivorship Rules determine which value is used on the Unified Individual. These include: (1) 'Most Recently Updated' — prefer the most recent value; (2) 'Source Priority' — configure which data source is the authoritative source for specific fields. Alphabetical ordering and first-ingested-wins are not survivorship strategies.

17. 17. A Data Cloud consultant observes that after Identity Resolution, a very large number of records are being merged into single Unified Individuals (e.g., thousands of records per individual). This is a sign of:

    • A. Excellent identity resolution quality — more merges mean better data quality
    • B. Over-matching caused by Match Rules that are too permissive, creating 'super profiles' by incorrectly merging unrelated individuals(correct)
    • C. A Data Stream configuration error causing duplicate records to be ingested
    • D. A normal behavior for large enterprise datasets

    Explanation: When Match Rules are too permissive (e.g., matching only on first name, or using very low fuzzy match thresholds), unrelated individuals with common names or shared devices get incorrectly merged into 'super profiles' — single Unified Individuals containing hundreds or thousands of unrelated source records. This is a critical Identity Resolution quality issue. The fix is to tighten match criteria to require stronger, multi-field matching evidence.

18. 18. In Data Cloud, what is a Segment?

    • A. A partition of the Data Cloud storage infrastructure
    • B. A defined group of Unified Individuals who meet specified criteria, used for targeted activation(correct)
    • C. A portion of a Data Stream refresh that processes a batch of records
    • D. A geographic region in which Data Cloud data is stored

    Explanation: A Segment in Data Cloud is an audience definition — a set of criteria that identifies a group of Unified Individuals with specific characteristics (attributes, behaviors, relationships). For example: 'Customers who purchased in the last 30 days AND have not opened a marketing email in 60 days.' Segments are the foundation for targeted activation to marketing, sales, and service channels.

19. 19. A marketer needs to build a Data Cloud Segment of customers who made a purchase in the last 90 days AND have a loyalty tier of 'Gold'. Which segment criteria type is used for the behavioral purchase condition?

    • A. Profile attribute filter on the Purchase Date field of the Unified Individual
    • B. Engagement data filter on the Purchase transaction DMO with a relative date range of last 90 days(correct)
    • C. A calculated insight filter based on a pre-computed purchase count metric
    • D. A Flow-triggered filter that runs nightly to flag qualifying individuals

    Explanation: Behavioral/transactional criteria (like 'made a purchase in the last 90 days') are applied using Engagement data filters in the segment builder — filtering rows in the related Engagement-category DMO (e.g., a Purchase or Order DMO) with a date range condition. Profile attribute filters are for static characteristics like loyalty tier. Calculated Insights can also be used for pre-aggregated metrics but are a separate mechanism.

20. 20. A Data Cloud segment needs to be activated to Marketing Cloud for email campaign execution. Which two configurations are required? (Choose 2)

    • A. Create an Activation Target connecting Data Cloud to the Marketing Cloud org(correct)
    • B. Create an Activation mapping the segment's contact attributes to Marketing Cloud Contact fields(correct)
    • C. Export the segment to a CSV file and import it into Marketing Cloud manually
    • D. Enable the 'Marketing Cloud Sync' toggle in the segment's settings

    Explanation: To activate a Data Cloud segment to Marketing Cloud: (1) Configure an Activation Target for Marketing Cloud (specifying the business unit, connection credentials); (2) Create an Activation that maps the segment to the Activation Target and defines which contact point fields (email address, subscriber key) are sent to Marketing Cloud. The activated segment creates or updates Marketing Cloud contacts/subscribers that can be used in journey or email send audiences.

21. 21. What is an 'Activation' in Data Cloud?

    • A. The process of enabling Data Cloud in a Salesforce org
    • B. A configured pipeline that sends a segment's member data to an external destination (Marketing Cloud, advertising platform, etc.)(correct)
    • C. Turning on a scheduled Data Stream refresh
    • D. Activating an Einstein prediction model for production use

    Explanation: An Activation in Data Cloud is a configured export pipeline that takes a Segment's members and their associated data attributes, and sends them to a destination system (Activation Target) such as Marketing Cloud, Google Ads, Facebook Audiences, or a CRM. Activations define which contact points and attributes are included, the schedule, and the mapping to destination field names. Activations close the loop from data unification to execution.

22. 22. A company wants to use Data Cloud segments to personalize the Salesforce Service Cloud agent experience — showing the agent which segment(s) the customer belongs to. Which two approaches enable this? (Choose 2)

    • A. Activate the segment back to the Salesforce CRM using the Salesforce CRM Activation Target, writing segment membership to a custom field on Contact(correct)
    • B. Use Data Cloud's Data Actions to trigger a Salesforce Flow when a customer enters or exits a segment(correct)
    • C. Export segment members to a CSV and import them into the Contact object nightly
    • D. Create a Salesforce Report based on Data Cloud segment data

    Explanation: To surface Data Cloud segment membership in Salesforce Service Cloud: (1) Activate the segment to the Salesforce CRM using the Salesforce CRM Activation Target, which writes segment membership back to Contact or Individual records (viewable by agents); (2) Data Actions (Data Cloud-triggered Flows) can fire when a customer joins/leaves a segment, updating a field on the Contact or creating an alert for the agent. CSV nightly export/import introduces latency. Salesforce Reports cannot directly query Data Cloud segments.

23. 23. What is a 'Calculated Insight' in Salesforce Data Cloud?

    • A. A real-time dashboard built with CRM Analytics on top of Data Cloud data
    • B. A pre-computed metric or aggregation (e.g., total purchase value, average order value) derived from Data Cloud data and stored for use in segmentation and activation(correct)
    • C. An AI-generated recommendation surfaced to sales reps in Sales Cloud
    • D. A data quality score calculated by Identity Resolution for each Unified Individual

    Explanation: Calculated Insights are pre-computed aggregations and metrics built from Data Cloud DMO data using SQL queries. Examples: total lifetime purchase value, number of purchases in last 90 days, average session duration, churn risk score. These metrics are stored as attributes on the Unified Individual and can be used as filtering criteria in Segments or as attributes sent to Activation destinations. They enable sophisticated behavioral segmentation without recalculating aggregations at query time.

24. 24. A company wants to use Einstein AI in Data Cloud to predict which customers are likely to churn. How is this AI model integrated with Data Cloud?

    • A. Einstein Prediction Builder models are deployed as Calculated Insights in Data Cloud
    • B. Einstein Discovery models trained on CRM Analytics datasets can be pushed to Data Cloud as AI-powered attributes on Unified Individuals
    • C. Data Cloud natively includes pre-built churn prediction models in every org
    • D. External ML models from AWS SageMaker can be connected to Data Cloud via the Einstein Studio connector(correct)

    Explanation: Data Cloud's Einstein Studio supports connecting external ML models from platforms like AWS SageMaker, Google Vertex AI, and internally trained models. These external models can be invoked by Data Cloud on unified customer data and their predictions stored as attributes on Unified Individuals for use in segmentation and activation. Prediction Builder models are for standard Salesforce object-based predictions. Einstein Discovery connects through CRM Analytics separately.

25. 25. A Data Cloud consultant wants to trigger a Salesforce Flow when a high-value customer joins a 'VIP Churn Risk' segment. Which two Data Cloud features enable this? (Choose 2)

    • A. Data Actions — a feature that fires a Salesforce Platform Event or invokes a Salesforce Flow when a segment membership change occurs(correct)
    • B. Segment Entry triggers — automatically invoke a configured webhook or Flow when any individual enters the segment(correct)
    • C. A scheduled Salesforce Report filtered on segment membership to notify service agents
    • D. A Marketing Cloud Journey that starts when a Data Cloud Data Action fires a Platform Event

    Explanation: Data Cloud's Data Actions feature (also called Segment Entry/Exit triggers in some contexts) allows triggering external actions when customers enter or exit a segment: (1) Data Actions can publish a Salesforce Platform Event, triggering a connected Salesforce Flow — enabling real-time CRM actions like creating a task or alert for a service agent; (2) Segment entry triggers with webhook/Flow invocations fire when segment membership changes. Scheduled Reports introduce latency. While Marketing Cloud Journeys can start from Data Cloud events, this is not the direct mechanism for triggering a Salesforce Flow.