Free Salesforce-Data-360-Consultant Practice Test Questions (2026)

Explanation:

This question tests knowledge of choosing the correct Data 360 architecture component for large-scale analytics and dashboard reporting. The scenario requires processing massive engagement volumes, refreshing data within 15 minutes, and delivering fast dashboard performance for executives viewing trending product metrics.

🟢 B. Calculated Insights
Calculated Insights are built for large-scale aggregations and analytical processing in Salesforce Data 360. They can process hundreds of millions of engagement events and generate metrics such as “Top 10 Trending Products” efficiently. They also support scheduled refresh intervals that satisfy the 15-minute freshness requirement while ensuring dashboards load quickly through precomputed aggregated data.

🔴 A. Direct Related List
Direct Related Lists are designed to display related Salesforce records in the UI. They are not intended for analytical workloads, large-scale aggregations, or ranking calculations based on hundreds of millions of engagement events.

🔴 C. Real-Time Data Graph
Real-Time Data Graphs focus on unified customer profile access and real-time relationship queries. They are not optimized for computing large aggregated trend metrics or supporting high-performance executive dashboards with ranked analytics.

🔴 D. Streaming Insight
Streaming Insights are primarily used for immediate event processing and real-time triggers. Although they support low-latency processing, they are not the best fit for heavy historical aggregation and dashboard-oriented trend analysis across massive datasets.

🔧 Reference:
⇒ Salesforce Data Cloud Architecture – Calculated Insights
Confirms that Calculated Insights are designed for aggregated metrics and large-scale analytical processing.

⇒ Salesforce Help – Enhance Data with Insights
Explains when to use Calculated Insights versus Streaming Insights in Data Cloud.

Explanation:

This question tests understanding of relationship cardinality in Salesforce Data Cloud when modeling DMOs. The scenario describes a classic parent-child relationship for car ownership.

✅ Correct Option:

C. Many-to-One (N:1)
When creating the relationship from the Vehicle DMO to the Individual DMO, the architect should select Many-to-One (N:1). This means many Vehicles can relate to one Individual (one person can own multiple cars), while one Vehicle can only relate to one Individual (one car has only one owner). This is implemented via a lookup field on the Vehicle DMO.

❌ Incorrect options:

A. One-to-One (1:1)
One-to-One would restrict each Vehicle to one Individual and each Individual to only one Vehicle. This violates the requirement that one individual can own multiple vehicles.

B. Many-to-Many (N:N)
Many-to-Many allows multiple Vehicles to relate to multiple Individuals (e.g., shared ownership). This is unnecessary and overly complex for the stated requirement of single ownership per vehicle.

D. One-to-Many (1:N)
One-to-Many from Vehicle to Individual would mean one Vehicle can link to many Individuals, which contradicts the rule that one vehicle has only one owner.

🔧 Reference:
→ Data Cloud Data Modeling – Relationships
Explains cardinality options (1:1, 1:N, N:1, N:N) when creating relationships between DMOs.

Explanation:

This question tests the consultant's knowledge of data type behavior in Salesforce Data 360 streams, specifically how different field types handle leading zeros. Purchase order numbers (e.g., "0012345") are identifiers, not mathematical values. Numeric field types strip leading zeros because they treat the value as a number, whereas Text preserves the exact string as entered.

✅ Correct Option: C. Text
The Text field type stores data exactly as provided, including leading zeros, spaces, and special characters. When the consultant defines the data stream mapping, choosing Text for the purchase order number ensures that "0012345" remains "0012345" throughout ingestion, transformation, and storage. This is critical for matching, reporting, and downstream system integration where the full identifier including zeros is required.

❌ Incorrect Option: A. Number
The Number field type strips leading zeros because it stores values numerically. For example, "0012345" becomes "12345". This breaks data fidelity for purchase order numbers, causing mismatches in joins, exports, or external system lookups. Only use Number for values that require arithmetic operations.

❌ Incorrect Option: B. Decimal
Decimal, like Number, stores numeric values and automatically removes leading zeros. It also adds decimal precision, which is irrelevant and misleading for an identifier like a purchase order number. Using Decimal would corrupt the original value and waste storage.

❌ Incorrect Option: D. Serial
Serial is an auto-incrementing integer field type, typically used for system-generated unique IDs (e.g., record IDs or sequence numbers). The consultant cannot import or preserve external purchase order numbers in a Serial field because Salesforce generates the value automatically, overriding the source data.

🔧 Reference:
→ Salesforce Data Streams Field Types Documentation – Confirms that Text fields preserve leading zeros, while Number and Decimal types do not.

Explanation:

The question tests how to control the payload of related attributes sent during activation from Salesforce Data Cloud to external targets like Marketing Cloud. It highlights a scenario where a profile segment functions correctly, but unconstrained 1-to-many relationship paths cause extraneous historical engagement records to bypass the segment’s timeline intent.

✅ Correct Option:

C. Apply a 30-day date filter on the Sales Order DMO within the activation.
When a segment is built on the Individual profile grain, its criteria only determine which customers qualify. When including related 1-to-many child attributes (like Sales Orders) in the activation payload, Data Cloud pulls all historical records for those individuals by default unless an explicit activation filter is applied to that specific related object to restrict the output.

❌ Incorrect options:

A. Filter out older orders in Marketing Cloud after activation.
Filtering data after it reaches Marketing Cloud shifts data volume and processing overhead to the downstream system instead of keeping it source-governed. This creates unnecessary processing strain, delays journeys, and creates compliance and synchronization issues by moving unnecessary historical records out of Data Cloud.

B. Apply a data space filter to exclude orders older than 30 days.
Data space filters are global boundary controls used to govern permissions and partition data visibility for entire business units or brands. They are completely static and are not intended to dynamically restrict rolling time-based transactional windows for individual marketing campaign activation payloads.

D. Build a segment using the Sales Order DMO and filter orders to the last 30 days.
Changing the segmentation entity to the Sales Order DMO shifts the entire core grain from a profile audience to a transactional audience. While it limits orders, it changes the segmentation structure entirely and fails to natively resolve the issue of constraining related payload attributes on a profile-based activation.

🔧 Reference:
→ See Considerations for Selecting Related Attributes in Data 360 Activations which explains how activation filters constrain the records exported for 1-to-many related data model objects.

Explanation:

This question is testing the most efficient way to surface engagement history from Data 360 on a Salesforce Lead record. The right approach is to use the native related list enrichment feature, because it can display Data 360 engagement data directly on the record page without copying records into custom Salesforce objects.

A. Embed a filtered report chart on the record page that queries the Data 360 objects directly
❌ This is not the best fit because a report chart is a reporting view, not a native record-level engagement timeline. It also adds more complexity and does not provide the direct chronological related-list experience sales reps need.

B. Drag the native Data 360 Related List Enrichment onto the Lead Lightning page and configure the relevant Engagement data model objects (DMOs)
✅ This is correct because Data 360 Related List Enrichment is designed to show Data 360 data directly on Salesforce record pages. It lets you configure the relevant engagement DMOs so sales reps can see Web Page Views and Email Clicks in context on the Lead record, which is efficient and avoids data duplication.

C. Create a custom object in Salesforce, use Flow to sync Data 360 Engagement records back to CRM, and add a standard related list
❌ This works, but it is not efficient. It creates extra storage, Flow maintenance, and synchronization overhead, when the native related list enrichment already solves the use case directly.

D. Use Dynamic Forms to conditionally show fields from the Data 360 Individual object based on the Lead's status
❌ Dynamic Forms control field visibility, not a chronological activity feed. They cannot present a list of engagement events like page views and email clicks in the way the question requires.

🔧 Reference:
→ Salesforce Help — Create a Related List Enrichment
— confirms the native Data Cloud Related List feature for adding related data to Lead, Contact, or Account pages.

→ Salesforce Help — Create a Direct-DMO Related List Enrichment
— confirms that related list enrichment can display DMO records on Salesforce object pages.

Explanation:

This question tests knowledge of how Salesforce Data Cloud configurations are packaged and migrated between environments using Change Sets. The key challenge is identifying the correct metadata component type that encapsulates a data kit — including data streams and identity resolution rules — for successful deployment.

✅ D. Data Package Kit Definition
In Salesforce Data Cloud, a data kit is represented in Change Sets as a Data Package Kit Definition component type. This metadata type bundles all associated configurations — including data streams and identity resolution rulesets — into a single deployable unit. Selecting this component ensures the entire kit structure is captured and transferred intact to the target org.

❌ A. Data Stream Configuration
While Data Streams are part of the kit, selecting them individually as a standalone component type does not ensure the full kit structure is preserved. Individual data stream components lack the packaging context needed to carry associated dependencies and rules across environments reliably.

❌ B. Identity Resolution Ruleset
Identity Resolution Rulesets are a sub-component within a data kit, not a top-level deployable unit for this scenario. Selecting this alone would only migrate the ruleset logic and would not capture the associated data streams or the overarching kit configuration required for a complete transfer.

❌ C. Data 360 Metadata Definition
This is not a recognized or valid component type within Salesforce Data Cloud Change Sets. It is a fabricated option designed to mislead. No such metadata component exists in the official Data Cloud deployment framework, making it an invalid selection for any migration scenario.

🔧 Reference:
→ Data Cloud – Deploy Data Kits with Change Sets – Salesforce Help
Confirms that Data Package Kit Definition is the correct component type to select when adding data kits to outbound Change Sets for cross-org deployment.

Explanation:

This question assesses the impact of performing a Full Sandbox refresh on an existing Data 360 configuration. It evaluates understanding of how metadata and ingested data behave differently during a sandbox refresh from production.

✅ Correct Option:

D. All Data 360 metadata is replicated from the current version of production instance, and the ingested records are cleared and must be re-ingested.
When a Full Sandbox is refreshed, Salesforce copies all Data 360 metadata (such as data streams, mappings, identity resolution rules, segments, and calculated insights) from the production environment. However, all ingested records, unified profiles, and calculated data are cleared. The team must re-ingest data and re-run processes to restore data volume for performance testing.

❌ Incorrect options:

A. The sandbox maintains its connection to the existing Data 360 instance, but all data mapping is reverted to Draft status.
The connection breaks after refresh due to Org ID change, and data mappings are replicated from production without reverting to Draft.

B. Only the identity resolution rules are deleted, while data streams remain active and continue to pull data from the refreshed sandbox objects.
All metadata is replicated from production. Data streams do not remain active automatically after refresh.

C. The Data 360 instance is deleted and a new, blank Data 360 instance must be provisioned after the refresh.
The Data 360 instance is not deleted. Metadata is replicated; only ingested data is cleared.

🔧 Reference:
→ Refresh and Synchronize Your Data 360 Sandbox
Explains sandbox refresh behavior for Data 360 metadata and ingested data.

Explanation:

This question tests understanding of logical data isolation in Salesforce Data 360. The requirement is governance-level separation between business units while still operating under the same home org. The solution must isolate both data and metadata, not just access or UI-level visibility.

🟢 C. Use separate data spaces for each business unit
Data Spaces in Data 360 are designed specifically for logical separation of data, metadata, and configurations within a single org. Each business unit can operate in its own isolated environment while sharing the same underlying Data 360 instance. This ensures compliance, governance boundaries, and independent data management without requiring separate orgs.

🔴 A. Use separate companion connections within the same data space
Companion connections are used for connecting external systems or data sources, not for isolating business units. They do not provide logical separation of data or metadata within Data 360.

🔴 B. Use different permission sets within the same data space
Permission sets control user access and visibility but do not separate data or metadata. All business units would still share the same underlying data space, which fails governance isolation requirements.

🔴 D. Use separate objects per business unit with record-type filtering
Using separate objects or record types only provides logical segmentation at the data model level, not true isolation. It introduces complexity and does not enforce strict separation of metadata, configurations, or governance boundaries.

🔧 Reference:
⇒ Salesforce Data Cloud Data Spaces Overview
Explains how Data Spaces provide logical separation of data, metadata, and configurations for multi-business-unit scenarios.

Explanation:

This question tests the consultant's knowledge of packaging and promoting Data 360 (formerly Data Cloud) configurations across multiple orgs. After completing and testing an Amazon S3 data stream and its mappings in one Data 360 org, the recommended approach to move that configuration to a second org is creating a data kit—a reusable package of metadata that can be exported and imported across environments.

✅ Correct Option: D. Create a data kit
Data kits are the native Salesforce mechanism for packaging and promoting Data 360 configurations across different orgs or environments. They allow consultants to export metadata such as data streams, mappings, data model objects, and calculated insights from a source Data 360 org and import them into a target org. This is the recommended migration approach for configurations like Amazon S3 data streams that have been fully tested in one environment.

❌ Incorrect Option: A. Use the Salesforce CRM Connector
The Salesforce CRM Connector is used to connect a Salesforce Core org to Data 360 for ingesting CRM data. It is not designed for packaging or promoting custom S3 data stream configurations. This option confuses data source connectivity with metadata migration.

❌ Incorrect Option: B. Use the Metadata API
The Metadata API can be used to rotate credentials or retrieve metadata for S3 connectors, but it is not the recommended tool for packaging and promoting complete data stream configurations across Data 360 orgs. Data kits provide a purpose-built, higher-level abstraction for this specific migration need.

❌ Incorrect Option: C. Package as an AppExchange application
AppExchange applications are designed for packaging and distributing Salesforce solutions to external customers or the broader ecosystem. Creating an AppExchange app for internal configuration promotion between two orgs is heavy-handed, time-consuming, and unnecessary when data kits offer a simpler, direct migration path.

🔧 Reference:
→ Salesforce Ingestion API Documentation – Confirms that data kits are used to package and promote Data 360 configurations, and notes that the Metadata API is for credential management, not configuration packaging.

Explanation:

The question tests the consultant's ability to implement governance, efficiency, and maintenance best practices within the Data Cloud segmentation canvas. It addresses a scenario where common exclusion filters must be standardized across multiple distinct brand segments and updated centrally every month to prevent operational duplication.

✅ Correct Option:

C. Create a reusable container block with common criteria.
Creating a reusable container block allows a consultant to define specific exclusion rules once and insert that single block across multiple target segments. When exclusion criteria change on a monthly basis, modifying the core reusable container instantly propagates those updates across every brand segment utilizing it, minimizing configuration effort and ensuring architectural consistency.

❌ Incorrect options:

A. Create a segment and copy it for each brand.
Copying a standalone segment for each brand team creates completely independent copies of the filtering criteria. This approach eliminates centralized control, forcing the consultant to manually find, open, and update every single brand's copied segment individually every month, which is error-prone and highly inefficient.

B. Create, publish, and deploy a data kit.
Data kits are specialized package containers designed to transfer metadata structures, schemas, and mappings across completely separate Salesforce orgs or sandbox environments. They are not intended for managing rolling, monthly operational data filter logic or segment criteria modifications within a single live production environment.

D. Create a nested segment.
A nested segment allows you to reuse an entire existing segment's output as an eligibility filter inside another segment. While useful, nesting focuses on compiling whole population subsets rather than establishing a modular, easily managed exclusion rule-set component block explicitly designed for cross-team structural reuse.

🔧 Reference:
→ See Salesforce Help: Segment Your Data with Attributes which details how to build and maintain reusable container blocks for unified segmentation criteria.