Free Salesforce Data 360 Consultant Practice Test Questions
113 questionsUpdated 17-Nov-202617 topics
TopicData Source Connection and Ingestion
Question 11Choose 1
A Data 360 Consultant is explaining the benefits of zero-copy data federation to a stakeholder. Which statement best describes how data federation differs from traditional data ingestion in Data 360?
Correct answer:
C. Data federation allows Data 360 to read data directly from an external provider without moving or
copying the data.
Explanation:
Data federation (also called zero-copy) allows Data 360 to access and query data directly from external data sources without copying or moving it into Data 360 storage. Instead of ingesting data, Data 360 creates an external Data Lake Object (DLO) that acts as a reference pointing to the data physically stored in the external system . This eliminates the need for duplication and enables real-time access to external data.
Correct Option:
C. Data federation allows Data 360 to read data directly from an external provider without moving or copying the data.
This accurately describes the core benefit of data federation. Data stays in its original location (such as Snowflake, Databricks, or BigQuery), and Data 360 queries it in place using Apache Iceberg or other supported connectors. This approach reduces storage costs, eliminates data duplication, and ensures data freshness since queries retrieve the most current information directly from the source .
Incorrect Option:
A. Data federation requires data to be converted into CSV format before it can be accessed.
Data federation does not require CSV conversion. It supports open table formats like Apache Iceberg and connects directly to external data platforms through supported connectors. The data remains in its native format and is queried in place .
B. Data federation copies all data into Data 360 storage every 15 minutes.
This describes caching or accelerated query behavior, not federation itself. Data federation by definition does not copy data into Data 360. While caching can be optionally enabled to improve performance for frequently accessed data, it is not a requirement of federation .
D. Data federation only supports data coming from other Salesforce orgs.
This is incorrect. Data federation in Data 360 supports external platforms including Snowflake, Databricks, Google BigQuery, Amazon Redshift, AWS Glue Data Catalog, and other Iceberg-compatible data sources—not just Salesforce orgs .
Reference:
Salesforce Help: Data Federation, Ingestion, and Modeling; Salesforce Help: Caching or Acceleration in Data Federation; Salesforce Blog: Unlock Trapped Data in Your Data Lakes.
TopicIdentity Resolution and Unification
Question 12Choose 1
A customer has multiple data sources and needs to match and reconcile data about individuals into a single
unified profile. Which feature should the Data 360 Consultant recommend for the customer?
Correct answer:
A. Identity Resolution
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.
Question 13Choose 1
What does the Ignore Empty Value option do in Identity Resolution?
Correct answer:
D. Ignores empty fields when running match 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.
Question 14Choose 1
A Data 360 Consultant has set up an identity resolution ruleset for their client ' s Data 360 implementation and
now wants to confirm the results. Which two features should the consultant use to validate the data on a
unified profile?
Correct answer:
A. Profile ExplorerandQuery Editor
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.
When setting up file federation for a data lake on Azure Blob Storage, what is the role of the manifest file?
Correct answer:
C. It defines metadata and paths to identify specific files for the data stream and track updates.
Explanation:
This question tests the consultant's understanding of file federation configuration in Data 360, specifically the role of the manifest file when connecting to an external data lake like Azure Blob Storage. File federation allows Data 360 to read data directly from external storage without ingesting it. The manifest file acts as a pointer or catalog that tells Data 360 which files to read and how to interpret them.
✅ Correct Option: C. It defines metadata and paths to identify specific files for the data stream and track updates.
The manifest file serves as a configuration blueprint for file federation. It contains metadata about the source files—including file paths, schemas, formats, and timestamps—allowing Data 360 to locate the correct files in Azure Blob Storage and understand their structure. Additionally, it enables incremental processing by tracking which files have already been read, so only new or updated files are processed on subsequent runs.
❌ Incorrect Option: A. It reduces the file size of the source data before Data 360 attempts to read it.
This is incorrect. The manifest file does not perform any compression or file size reduction. Data size reduction, if needed, would be handled by the source system or via separate ETL processes before files are placed in the data lake.
❌ Incorrect Option: B. It is used to manually map source fields to the Cloud Information Model.
This is incorrect. Field mapping to the Cloud Information Model is handled within the data stream configuration in Data 360, not within the manifest file. The manifest file identifies which files to read, while mapping is a separate configuration step.
❌ Incorrect Option: D. It provides the PGP public key required to decrypt the federated data files.
This is incorrect. Encryption and decryption keys, including PGP keys, are managed through separate security configurations such as key stores or credential management in Data 360. The manifest file does not handle encryption keys.
🔧 Reference:
→ Salesforce Data Cloud File Federation Documentation – Confirms that manifest files define metadata, file paths, and schemas for federated data streams, enabling incremental processing by tracking processed files.
Question 16Choose 1
A Data 360 Consultant has a large historical dataset stored in Snowflake as parquet files in an object store.
The consultant needs to run heavy analytics queries periodically, with high throughput but not necessarily
real- time needs. Which Data 360 pattern is most appropriate?
Correct answer:
D. Query federation with acceleration (Caching)
Explanation:
This question tests knowledge of Salesforce Data Cloud's data access patterns for external data sources. The key requirements are handling a large historical Snowflake dataset with heavy analytics queries, high throughput performance, and periodic — not real-time — freshness needs, which directly points to a caching-based federation strategy.
✅ D. Query Federation with Acceleration (Caching)
Query Federation with Acceleration caches query results from the external Snowflake source within Data Cloud, enabling high-throughput analytics without repeatedly hitting the source system. Since real-time freshness is not required, periodic cache refresh aligns perfectly with the use case. This pattern delivers fast query performance at scale while minimizing load on the Snowflake environment.
❌ A. Query Federation Without Acceleration (Live or Direct Access)
Live query federation executes queries directly against Snowflake at runtime without caching. For heavy analytics workloads with high throughput, this creates significant latency and load on the source system. Without acceleration, repeated complex queries against large historical datasets would result in poor performance, making it unsuitable for this scenario.
❌ B. Ingest Data into Data 360 as a Data Lake Object (DLO)
Ingesting the full historical Snowflake dataset as a DLO involves physically moving large volumes of parquet data into Data Cloud storage. This adds unnecessary ingestion overhead, storage costs, and pipeline complexity. Since the data already resides in Snowflake, federation with caching is a more efficient and architecturally appropriate pattern.
❌ C. File Federation
File Federation is designed to query external files stored directly in object stores such as Amazon S3 or Google Cloud Storage. While the data exists as parquet files, the primary access layer here is Snowflake — not the raw object store. File Federation bypasses Snowflake entirely and does not leverage its structure or query optimization capabilities.
🔧 Reference:
→ Query Federation – Salesforce Help
Confirms that Query Federation with Acceleration caches results from external sources like Snowflake, enabling high-throughput periodic analytics without requiring real-time data access or full data ingestion.
TopicData Ingestion and Transformation
Question 17Choose 1
A marketer needs to segment customers based on their Lifetime Loyalty Points. This requires summing all
point-based transactions from a historical ledger brought in from their data lake along with a Commerce
Cloud data stream. Which tool should the marketer use?
Correct answer:
B. Calculated Insight
Explanation:
This question tests knowledge of the correct Salesforce Data Cloud tool for performing aggregated metric computations across historical and streaming data sources. The key requirement is summing point-based transactions from multiple sources to derive a single Lifetime Loyalty Points value usable for segmentation.
✅ B. Calculated Insight
Calculated Insights are designed to compute and persist aggregated metrics — such as summing all point-based transactions — across multiple Data Model Objects (DMOs) from different data sources. The resulting metric is stored as a DMO attribute, making Lifetime Loyalty Points directly available as a segmentation filter within Data Cloud Segment Builder.
❌ A. Streaming Transform
Streaming Transforms process and shape data in real time as it flows into Data Cloud. They handle record-level transformations on incoming events, not historical aggregations. Summing all past loyalty point transactions across a full historical ledger is beyond the scope of what Streaming Transforms are designed to perform.
❌ C. Batch Transform
Batch Transforms are used to reshape, filter, or enrich data during ingestion on a scheduled basis. They operate at the record or row level and do not perform cross-source aggregations like summing transactions. They prepare data for use but cannot produce a persisted, segmentable aggregated metric like Lifetime Loyalty Points.
❌ D. Secondary Index
A Secondary Index improves query performance by creating additional lookup paths on Data Model Object fields. It is purely a performance optimization tool and has no capability to compute, aggregate, or store calculated values. It does not process transactions or generate any derived metrics for segmentation purposes.
🔧 Reference:
→ Calculated Insights in Salesforce Data Cloud – Salesforce Help
Confirms that Calculated Insights aggregate and persist metrics across multiple DMOs, making computed values like Lifetime Loyalty Points available directly for segmentation in Data Cloud.
Question 18Choose 1
Which statement is true related to batch ingestions from Salesforce CRM?
Correct answer:
A. When a column is added or removed, the CRM Connector performs a full refresh.
Explanation:
This question tests understanding of how the Salesforce CRM Connector behaves during batch data ingestion into Data Cloud. It focuses on schema change handling, manual refresh capabilities, deletion thresholds, and synchronization interval configurations — all critical behaviors for managing CRM data pipelines reliably.
✅ A. When a column is added or removed, the CRM Connector performs a full refresh.
When a schema change occurs — such as adding or removing a column — the CRM Connector automatically triggers a full refresh to ensure data integrity and alignment with the updated structure. This behavior prevents mismatched mappings and ensures the Data Cloud Data Model Object accurately reflects the modified CRM schema.
❌ B. CRM data cannot be manually refreshed and must wait for the next scheduled synchronization.
This is incorrect. Salesforce Data Cloud allows administrators to manually trigger a CRM Connector refresh at any time directly from the Data Stream settings. Manual refresh capability is a supported feature, giving teams flexibility to pull updated CRM data outside of the scheduled synchronization window when needed.
❌ C. The CRM Connector performs an incremental refresh when 600,000 or more deletion records are detected.
This is incorrect. When 600,000 or more deletion records are detected, the CRM Connector performs a full refresh, not an incremental one. The high volume of deletions triggers a complete data reload to ensure accuracy and consistency, as incremental processing at that scale risks data integrity issues.
❌ D. The CRM Connector's synchronization times can be customized to up to 15-minute intervals.
This is incorrect. The CRM Connector in Data Cloud supports synchronization on an hourly basis, not 15-minute intervals. The 15-minute latency option applies to other Data Cloud features like Calculated Insights. CRM Connector scheduling does not support sub-hourly customization intervals.
🔧 Reference:
→ Salesforce CRM Connector Behavior – Salesforce Help
Confirms full refresh behavior upon schema changes, deletion record thresholds, and supported synchronization intervals for the CRM Connector in Data Cloud.
Question 19Choose 1
A Data 360 Consultant for a high- growth retail brand is configuring the ingestion of customer behavioral data
from a mobile application. The brand requires that the raw, unmodified data be stored exactly as it appears in
the source system before any mapping or transformations occur to maintain a historical record of the
transmission. Which object serves as the container of this source data in Data 360?
Correct answer:
D. Data Lake Object
Explanation:
This question tests understanding of Salesforce Data Cloud's data storage architecture, specifically which object type holds raw, unprocessed source data prior to any mapping or transformation. The key requirement is preserving an exact historical record of the original transmission from the mobile application source system.
✅ D. Data Lake Object
A Data Lake Object (DLO) is the container in Salesforce Data Cloud that stores raw, unmodified source data exactly as it arrives from the source system — before any mapping, transformation, or harmonization occurs. It acts as the foundational ingestion layer, preserving the original transmission record and serving as the source from which Data Model Objects are later mapped.
❌ A. Calculated Insight Object
Calculated Insight Objects store pre-computed, aggregated metrics derived from processed Data Model Objects. They represent the output of analytical computations, not raw source data. They are the furthest point from ingestion in the Data Cloud pipeline and have no role in storing unmodified source transmissions.
❌ B. Data Model Object
A Data Model Object (DMO) is created after raw data has been mapped and harmonized from the Data Lake Object. It represents structured, standardized data aligned to the Data Cloud data model. Since it exists post-transformation, it does not preserve the original unmodified source data as required by this scenario.
❌ C. Party Identification Object
The Party Identification Object is a specific standard DMO used within Identity Resolution to store identifiers — such as email or phone — associated with individuals. It is a specialized mapped object within the data model layer, not a raw ingestion container, and plays no role in preserving unmodified source transmission records.
🔧 Reference:
→ Data Objects in Data 360 – Salesforce Help
Confirms that Data Lake Objects serve as the raw ingestion containers in Data Cloud, storing source data exactly as received before any mapping or transformation is applied.
Question 20Choose 1
A data source does not have a field that can be designated as a primary key. What should the Data 360
Consultant do?
Correct answer:
D. Create a composite key by combining two or more source fields through a formula field.
Explanation:
This question evaluates how Salesforce Data 360 handles record uniqueness during data ingestion. Every ingested dataset requires a reliable primary key so records can be uniquely identified, updated, synchronized, and deduplicated correctly. When a source system lacks a naturally unique field, the consultant must design an alternative identifier strategy that guarantees uniqueness across all records.
🟢 D. Create a composite key by combining two or more source fields through a formula field.
Creating a composite key is the recommended solution when no single field uniquely identifies records in the source data. By combining multiple attributes—such as customer ID, transaction timestamp, store number, or order reference—into a formula field, the consultant can generate a stable and unique identifier for every record. This ensures Data 360 can accurately track updates, prevent duplicate ingestion issues, maintain synchronization integrity, and support downstream identity resolution and analytics processes.
🔴 A. Use the default primary key recommended by Data 360.
Data 360 does not automatically create a universally reliable primary key for datasets that lack uniqueness. Relying on a default recommendation can result in duplicate records, synchronization problems, and inconsistent record identification during ingestion and updates.
🔴 B. Remove duplicates from the data source and then select a primary key.
Eliminating duplicates improves data quality but does not solve the core issue of missing unique identifiers. Future incoming records could still create conflicts if no stable primary key exists to uniquely distinguish each record over time.
🔴 C. Select a field as a primary key and then add a key qualifier.
A key qualifier is used to distinguish similar identifiers across multiple data sources, but it does not make a non-unique field inherently unique within the same dataset. The primary key itself must still uniquely identify each record.
🔧 Reference:
⇒ Salesforce Data Cloud Primary Keys and Record Identification
Explains the importance of unique primary keys in Data Cloud and how composite keys can be used when source systems lack a single unique identifier.
Experience the real exam before you take it
Our timed 2026 Salesforce Data 360 Consultant practice test mirrors the format, number of questions and time limit of the official exam.
The #1 challenge isn't just knowing the material, it's managing the clock. The simulation builds your speed and stamina, so you walk in knowing exactly what to expect.