Free Salesforce Data 360 Consultant Practice Test Questions

Explanation:

This question tests understanding of Salesforce Data Cloud's core features for unifying customer data across multiple sources. The key requirement is matching and reconciling data about the same individual from different data sources into a single, consolidated unified profile.

✅ A. Identity Resolution
Identity Resolution is the purpose-built Data Cloud feature that matches, links, and reconciles individual records from multiple data sources into a single Unified Individual Profile. It uses configurable match rules and reconciliation rules to resolve identities across fragmented data, ensuring a complete and accurate 360-degree view of each customer.

❌ B. Data Consolidation
Data Consolidation is a general data management term referring to combining data into a central repository. It is not a specific Salesforce Data Cloud feature. It does not include the matching logic, ruleset configuration, or identity linking mechanisms required to reconcile individual-level records into unified profiles.

❌ C. Data Cleansing
Data Cleansing refers to detecting and correcting inaccurate, incomplete, or duplicate records to improve data quality. While it supports better data hygiene, it does not perform identity matching or profile unification. It addresses data accuracy, not the reconciliation of the same individual across multiple disconnected data sources.

❌ D. Harmonization
Harmonization in Data Cloud refers to mapping ingested data to a standard Data Model Object (DMO) structure for consistency. It standardizes data formats and schema alignment but does not perform individual matching or profile merging. It is a prerequisite step to Identity Resolution, not a replacement for it.

🔧 Reference:
→ About Identity Resolution – Salesforce Help
Confirms that Identity Resolution matches and reconciles records from multiple data sources into a single Unified Individual Profile using configurable match and reconciliation rules.

Explanation:

The question tests the consultant's knowledge of the configurable settings within Salesforce Data Cloud Identity Resolution. Specifically, it focuses on how the system handles null or blank values across different source systems when consolidating attribute data to form a single, trusted golden record for a unified profile.

✅ Correct Option:

C. Ignores empty fields when running reconciliation rules
The Ignore Empty Value option is an attribute-level setting applied strictly within Identity Resolution reconciliation rules. When enabled, it instructs the consolidation engine to completely skip over any incoming data sources that contain blank or null values for that specific field, ensuring that an empty value does not accidentally overwrite a populated field from a lower-priority source.

❌ Incorrect options:

A. Ignores Individual object records with empty fields when running identity resolution rules
Identity resolution processes evaluate incoming data at the granular attribute layer rather than the entire record layer. This option does not skip or drop whole individual profile records from the processing pipeline just because certain optional fields happen to be empty.

B. Ignores Contact Point object records with empty fields when running identity resolution rules
Contact point records (such as phone numbers or email addresses) are processed during identity resolution to map communication channels. The configuration does not ignore entire contact point records based on blank fields; it resolves values based on specific rule setups.

D. Ignores empty fields when running match rules
Match rules are used to establish a link between separate records using techniques like exact or fuzzy matching to find duplicates. The Ignore Empty Value toggle does not control match execution behavior, as blank fields are already naturally bypassed in matching to avoid false-positive link matches.

🔧 Reference:
→ See Salesforce Help: Configure Reconciliation Rules which confirms that the Ignore Empty Values selection applies directly to attribute selection within reconciliation rules to prevent null values from overriding valid data.

Explanation:

This question tests how to validate Identity Resolution results in Salesforce Data 360 after configuring a ruleset. The goal is to confirm that records are correctly unified into a single profile and can be queried accurately.

🟢 A. Profile Explorer and Query Editor
Profile Explorer is used to visually inspect unified customer profiles and verify how source records have been stitched together after identity resolution. Query Editor allows direct querying of unified profiles and related attributes to validate correctness at a data level. Together, they provide both visual confirmation and technical verification of identity resolution outcomes.

🔴 B. Data Explorer and Actions
Data Explorer is useful for browsing datasets but not specifically for validating unified identity resolution results. Actions relate to automation or activation, not validation of profile stitching.

🔴 C. Identity Resolution and Query API
Identity Resolution is the configuration process itself, not a validation tool. Query API can retrieve data but lacks the visual inspection capabilities needed to validate unified profiles effectively.

🔴 D. Data Actions and Query API
Data Actions are used for triggering workflows or downstream processes, not validation. Query API alone is insufficient because it does not provide a UI-based view of unified profiles for verification.

🔧 Reference:
⇒ Salesforce Data Cloud Profile Explorer Overview
Explains how Profile Explorer is used to inspect unified customer profiles after identity resolution.