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

Explanation:

The question tests the consultant's knowledge of ethical data practices, governance, and compliance considerations within Salesforce Data Cloud. It focuses on the principle of data minimization and ethical responsibility when collecting, managing, and storing highly sensitive personal attributes belonging to consumers.

✅ Correct Option:

A. Carefully consider asking for sensitive data such as age, gender, and ethnicity.
Adhering to ethical data principles requires a consultant to practice data minimization by evaluating whether collecting highly sensitive personal demographic data is truly necessary for business operations. Restricting collection reduces the risk of compliance violations, unintended algorithmic bias in downstream modeling, and security exposures for the consumer.

❌ Incorrect options:

B. Give senior leaders in the firm access to customer data for audit purposes.
Broadly granting access to raw, sensitive customer data based entirely on executive status violates the ethical rule of least privilege access. Access permissions must be governed strictly by specific operational roles and clear, audited regulatory business requirements rather than general internal seniority hierarchies.

C. Collect and use all of the data to create more personalized experiences.
Collecting absolutely every available piece of information without constraint contradicts modern ethical data handling and data privacy laws (such as GDPR and CCPA). Organizations must only capture specific data relevant to current needs, rather than hoarding arbitrary customer records under the pretext of future personalization.

D. Map sensitive data to the same data model object for ease of deletion.
Mapping fields purely based on deletion convenience violates structural modeling guidelines and compromises architectural integrity. Data should always be mapped strictly according to semantic relationships within the Cloud Information Model, while using native data deletion compliance APIs to handle privacy erasure requests securely.

🔧 Reference:
→ See Salesforce Ethical Data Use Guidance which emphasizes the importance of data minimization and responsible collection of sensitive personal attributes.

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.

Explanation:

This question tests the consultant's understanding of how Data 360 (Data Cloud) resolves duplicate customer records from multiple source systems (web portal, mobile app, POS system). The goal is to recognize a customer as the same individual across all three sources to enable a consistent service experience. Identity Resolution is the dedicated feature for this purpose, and matching rules are the specific mechanism within Identity Resolution that define how records from different sources are linked together .

✅ Correct Option: A. Matching rules within the Identity Resolution settings to link source records
Matching rules are configured within an Identity Resolution ruleset and define the criteria that Data 360 uses to determine that two or more source records belong to the same individual . For example, a match rule can link records that share the same email address, phone number, or a loyalty ID across the web portal, mobile app, and POS system . When a ruleset runs, these rules evaluate the source profiles and create unified individual profiles that stitch together all identifiers belonging to one customer . This is precisely the functionality required to ensure a customer is recognized consistently across all three channels.

❌ Incorrect Option: B. Data transform logic to normalize naming conventions during the ingestion process
Data transforms are used to clean, standardize, or enrich data as it is ingested . While normalizing data (e.g., making all name formats consistent) is an important preparatory step, it cannot by itself link records from different systems. Transform logic does not perform cross-record matching or create unified profiles—it only modifies individual records before they are stored.

❌ Incorrect Option: C. Partitioning strategies to separate data based on the original source system
Partitioning strategies segregate data based on source systems, which is the opposite of what is needed here. The requirement is to combine data across three sources, not separate it. Partitioning would keep web portal data isolated from POS data, actively preventing the unified view that the business outcome demands.

❌ Incorrect Option: D. Streaming insights to detect real-time changes in customer contact information
Streaming insights are used for continuous aggregation and low-latency analytics on high-velocity event data (as seen in the first question of this set). They do not perform identity resolution, link records from different sources, or create unified profiles. This option addresses real-time detection of changes, not the fundamental problem of duplicate recognition across systems.

🔧 Reference:
→ Salesforce Help: Identity Resolution Rulesets – Confirms that rulesets contain match rules that tell Data Cloud how to link multiple sources of data into a unified profile, and that match rules define the criteria for determining which profiles to unify.

Explanation:

This question tests the consultant's understanding of data privacy compliance, specifically handling Right to be Forgotten (Data Erasure) requests inside Salesforce Data Cloud using the platform's native developer tools.

✅ Correct Option:

A. Use Consent API to request deletion of the customer ' s information.
To comply with global data privacy regulations like GDPR or CCPA, Salesforce Data Cloud provides a specialized Consent API (specifically the Data Delete request endpoint). When a consultant submits a deletion payload for a specific Individual ID via this API, Data Cloud automatically orchestrates the erasure of that profile's corresponding data records across Data Lake Objects (DLOs), Data Model Objects (DMOs), and unified identity clusters.

❌ Incorrect options:

B. Use a streaming API call to delete the customer ' s information from the data lake object.
The Ingestion Streaming API is structurally designed as a one-way path to insert or append new event streams and transactional records into Data Cloud in real time. It does not possess the capability to target, scan, or execute hard-deletion or erasure operations on existing historical data blocks inside Data Lake Objects.

C. Use the Governance API call to delete the customer ' s information.
There is no "Governance API" designed for processing consumer privacy compliance data erasures. Governance features in Data Cloud focus on metadata categorization, data spaces partitioning, and permission sets rather than executing consumer-level transactional data deletion commands.

D. Use Profile Explorer to delete the customer data from Data 360.
Profile Explorer is a read-only administrative user interface tool used strictly for searching, verifying, and troubleshooting individual data attributes and unified profile relationships. It does not contain any functional buttons, tools, or permissions to modify or permanently delete consumer data from the platform.

🔧 Reference:
→ See Salesforce Help: Data Cloud Consent API which explains how to format and send data deletion requests to honor consumer privacy erasure preferences.

Explanation:

This question tests understanding of how predictive model outputs are stored and used in Salesforce Data 360. After activation, prediction scores must be accessible for segmentation, personalization, and analytics within the Data Cloud data model.

🟢 B. As an attribute on a related data model object (DMO)
When predictive models are activated in Data 360, the generated scores or predictions are typically written back as attributes on related DMOs such as Individual or Unified Profile objects. This allows marketers and analysts to directly use prediction values in segmentation, activation, and personalization workflows without relying on external systems.

🔴 A. Within the Audit Trail logs for security compliance
Audit Trail logs are used for tracking administrative and security-related activities. They are not designed to store predictive scores for segmentation or business use cases.

🔴 C. In a temporary CSV file available in the Setup menu
Predictive outputs are not stored as temporary CSV exports. Data 360 integrates predictions directly into the data model for operational use.

🔴 D. Directly within the source system (for example, Marketing Cloud or Sales Cloud) only
Predictions are not limited to external source systems. Data 360 stores and exposes them within its own unified data model to support segmentation and analytics.

🔧 Reference:
⇒ Salesforce Data Cloud Predictive Models Overview
Explains how prediction results are stored and used within Data Cloud for segmentation and customer intelligence.

Explanation:

This question tests your understanding of data modeling extension patterns within Salesforce Data Cloud. It focuses on the recommended architectural approach when a source data stream consists primarily of standard transaction details alongside a single, unique business-specific field.

✅ Correct Option:

A. Map standard fields to the Sales Order DMO and add a custom attribute for the fee.
Salesforce best practices dictate using standard Data Model Objects (DMOs) whenever possible to leverage native platform relationships, pre-built query paths, and out-of-the-box segmentation features. When a standard DMO (like Sales Order) is missing a specific business attribute (like a Sustainability Packaging Fee), the correct approach is to extend that standard DMO by adding a custom field (attribute) to it. This preserves the core data model integrity while cleanly accommodating the unique business requirement.

❌ Incorrect options:

B. Map all fields to a new Custom DMO specifically created for NTO transactions.
Creating an entirely new custom DMO for a standard transaction process is an architectural anti-pattern. Doing so forces you to manually recreate all relationships, joins, and lookups to other core objects (like Individual or Product) that are already managed natively by the standard Sales Order DMO framework.

C. Use Sales Order DMO and map the packaging fee to the Order Description field.
Mapping specific financial or structured numeric data into a generic text placeholder field like "Order Description" breaks data integrity. It prevents marketers from performing mathematical operations, such as filtering or aggregating by the fee amount, within the segmentation and insights canvases.

D. Create a calculated model to derive the sustainability fee using a streaming data transform.
The prompt indicates that the Sustainability Packaging Fee is already an incoming field provided in the source transaction data stream. There is no need to derive or calculate it using a transform; it simply needs to be stored and mapped correctly upon ingestion.

🔧 Reference:
→ See Salesforce Help: Data Model Custom Fields which explains how extending standard data model objects with custom attributes is the ideal mechanism to capture business-specific data points.

Explanation:

This question tests knowledge of how Salesforce Data Cloud handles privacy compliance requests — specifically Data Deletion and Right to Be Forgotten (RTBF) — when customer data is ingested via the Marketing Cloud Connector. It evaluates understanding of the correct submission channel for consent and privacy management.

✅ B. Through Consent API
The Consent API is the designated mechanism in Salesforce Data Cloud for submitting Data Deletion and Right to Be Forgotten requests. It processes deletion requests programmatically across all connected data sources, including Marketing Cloud ingested data. This ensures privacy compliance is enforced consistently at the platform level, regardless of which connector brought the data in.

❌ A. In Data 360 Settings
Data 360 settings manage platform configurations such as data streams, mappings, and connector setups. They do not provide a submission interface for individual-level privacy or deletion requests. Privacy compliance actions for specific customer records are not handled through general platform settings.

❌ C. In Marketing Cloud Settings
Marketing Cloud settings govern that platform's own configurations, journeys, and subscriber management. Once data is ingested into Data Cloud via the Marketing Cloud Connector, the responsibility for deletion requests shifts to Data Cloud's privacy framework — the Consent API — not the source system settings.

❌ D. On the Individual Data Profile in Data 360
While individual data profiles in Data Cloud display unified customer information, they do not serve as a submission point for deletion or RTBF requests. Profiles are read-oriented views for data exploration. Programmatic deletion requests must be submitted through the Consent API to ensure proper processing and compliance enforcement.

🔧 Reference:
→ Consent API for Data Deletion in Data Cloud – Salesforce Help
Confirms that the Consent API is the correct channel for submitting Data Deletion and Right to Be Forgotten requests in Salesforce Data Cloud, covering all ingested data sources including Marketing Cloud.

Explanation:

This question tests how to choose the best initial Data 360 use case. Salesforce best practice is to start with one clear, high-value business problem that can be solved with a focused set of data sources, not a large-scale, multi-region, or overly complex architecture. A single-view customer use case for a specific audience is a strong first project because it is practical, measurable, and delivers quick business value.

A. Implementing a complex, sub-second web personalization engine using 15 disparate third-party data streams with varying schemas
❌ This is too complex for an initial use case. It depends on many data sources, schema harmonization, and very low latency, which makes it a risky first project instead of a good pilot.

B. Moving 20 years of legacy transaction data into Data 360 to reduce storage costs in their primary CRM org
❌ This is mainly a storage or data migration goal, not a strong customer-experience use case. Salesforce guidance emphasizes starting with a business outcome such as activation or service improvement, not a historical archive move.

C. Redefining the global identity resolution rules for 1 billion records across 12 global regions simultaneously without a specific departmental pilot
❌ This is too broad and operationally risky for a first implementation. It affects core identity logic at massive scale without a narrow pilot, which conflicts with the recommended “start small” approach.

D. Consolidating three systems (Sales, Service, and Marketing Cloud) to provide a "Single View of the Customer" for high-tier support agents
✅ This is the best initial use case because it solves a clear business problem for a defined user group. It uses a focused set of core systems to improve agent experience and customer support, which aligns with Salesforce’s recommendation to begin with one business question and a small, high-value pilot.

🔧 Reference:
→ Salesforce Architects — Get Started with Data 360 Decision Guides
— provides architectural guidance for practical, phased Data 360 implementation choices.

Explanation:

This question tests efficient segment-building practices in Salesforce Data 360. The requirement combines an existing segment with an additional spending condition using OR logic. The best approach should maximize reuse, flexibility, and maintainability without unnecessary complexity.

🟢 C. Use a nested segment for "Platinum Loyalty" and add a separate container for the minimum spend with an OR operator.
Nested segments allow reuse of existing audience definitions without rebuilding logic. By combining the existing “Platinum Loyalty” segment with a separate spending rule using an OR operator, the architect can efficiently create a broader “High Value Customers” segment. This approach is scalable, easy to maintain, and aligns with standard Data 360 segmentation best practices.

🔴 A. Create two separate segments and join them together in a Tableau dashboard for activation.
This is inefficient because segmentation should be handled directly within Data 360, not externally in Tableau. Tableau is for analytics and visualization, not audience-building logic or activation workflows.

🔴 B. Build a calculated insight that joins both conditions and use that as the only filter in a new segment.
Calculated Insights are mainly intended for aggregated metrics, not combining reusable segment logic with OR conditions. This adds unnecessary complexity to a straightforward segmentation requirement.

🔴 D. Create a waterfall segment, prioritizing the "Platinum Loyalty" group first and the "High Spender" group second.
Waterfall segmentation is designed for prioritization and mutually exclusive audience assignment. The requirement simply needs inclusive OR logic, making waterfall segmentation unnecessary and incorrect.

🔧 Reference:
⇒ Salesforce Data Cloud Segment Builder Overview
Explains how nested segments and logical operators are used to create reusable and flexible audience definitions.

Explanation:

This question tests the recommended approach for mapping prep when source data contains business-specific fields that do not exist in the standard model. The goal is to preserve the standard model as much as possible while still making the data available for mapping and downstream use. Best practice is to review the standard DMOs first and extend them only where needed.

A. Extend the relevant standard DMOs by adding custom fields to accommodate the missing data.
✅ This is correct because Salesforce recommends extending standard DMOs when the source system contains fields that do not exist in the standard model. Adding custom fields keeps the mapping aligned to the business requirement while preserving the standard object structure. It is the preferred approach when the missing data belongs logically to an existing standard DMO.

B. Ignore the business-specific fields and map only the fields that exist in the standard DMOs.
❌ This would cause data loss. If the business-specific fields are relevant to the use case, leaving them unmapped means the source data will not fully support identity, segmentation, reporting, or activation needs.

C. Create a new custom DMO for every business-specific field identified in the source system.
❌ This is excessive and not a best-practice approach. A new custom DMO should be used only when the business data represents a distinct object model, not for every missing field.

D. Map the business-specific fields to the "Other" category to avoid modifying the standard model.
❌ The "Other" category is not a substitute for proper field modeling. It does not solve the mapping gap and can make the data model harder to maintain and use correctly.

🔧 Reference:
→ Salesforce Help — Data Mapping Best Practices
— confirms that if gaps are found, you should extend standard objects with custom fields or create a new custom DMO.