Data Cloud Overview practice questions

Data Cloud requires a standalone platform with no connection to Salesforce CRM editions.

Why it fails: Data Cloud tightly integrates with Salesforce CRM editions and leverages core user management.

Data Cloud is only available on Developer Edition for testing.

Why it fails: Developer editions are not supported for production Data Cloud deployments.

Data Cloud is included automatically in all Professional Edition orgs without extra cost.

Why it fails: Professional Edition does not support Data Cloud.

Activation Targets

Why it fails: Activation targets publish audience segments on a schedule or stream, rather than acting as transactional real-time event brokers.

Batch Segmentation

Why it fails: Batch segmentation runs on scheduled intervals and is not designed for real-time transactional alerting.

Enable Private Connect for the European region.

Why it fails: Private Connect is a network-level integration tool for secure connectivity, not an architectural partition for data spaces.

Configure a Segment-level override in Setup.

Why it fails: Segments do not have standalone overrides; their behavior is determined by the Data Space they are created within.

Modify the global Identity Resolution ruleset to ignore European records.

Why it fails: This does not isolate or correctly partition the data space; it inappropriately filters out business data.

Switch the Ingestion API stream to a batch CSV file upload via Amazon S3.

Why it fails: Switching to batch CSV upload via Amazon S3 changes the ingestion method but does not raise the API's per-request rate ceiling for the clickstream stream. It is tempting because batch loading reduces call frequency, and would be correct for bulk historical backfills rather than continuous high-volume real-time ingestion.

Upgrade the Salesforce CRM license to Unlimited edition.

Why it fails: CRM edition governs Salesforce user features and storage, not Data 360 Ingestion API request limits, so it cannot resolve throttling. It is tempting because licence tiers often gate platform capabilities, and upgrading would be correct when the constraint is CRM functionality or user capacity rather than ingestion throughput.

Disable Identity Resolution for clickstream data streams.

Why it fails: Identity resolution runs after ingestion and does not consume Ingestion API request quota, so disabling it leaves the rate-limiting errors unchanged. It is tempting because it reduces downstream processing load, and would be the right choice when reconciliation rules cause performance or matching problems rather than API throttling.

It must be left unmapped because custom fields are not supported on standard DMOs.

Why it fails: Custom fields are fully supported on standard DMOs.

It must be stored inside a Calculated Insight.

Why it fails: Calculated Insights are for metrics, not raw attribute mapping.

PNG and JPEG

Why it fails: Image formats are not supported for tabular data stream ingestion.

EXE and DLL

Why it fails: Executable and dynamic link library files are not data storage formats.

DOCX and XLSX

Why it fails: Word and Excel documents are not natively ingested as direct data streams without conversion to CSV.

Marketing Cloud Engagement Activation Target

Why it fails: Marketing Cloud is an engagement platform, not an enterprise data warehouse like Snowflake.

Webhooks via Data Actions

Why it fails: Webhooks are designed for real-time event messaging, not bulk data warehouse synchronization.

Salesforce CRM Outbound Message

Why it fails: Outbound messages are legacy SOAP-based CRM features, not enterprise data warehouse connectors.

Marketing Cloud Connect

Why it fails: Marketing Cloud Connect links CRM to Marketing Cloud, not Data Cloud.

Third-party ETL tool via REST API

Why it fails: While possible, third-party tools are unnecessary because Data Cloud provides a native CRM connector.

Bulk CSV Data Loader

Why it fails: Data Loader is for CRM record management, not the recommended streaming or native data stream setup for Data Cloud.

Manual CSV Export and Import via Data Loader

Why it fails: Manual exports are inefficient and non-automated.

Marketing Cloud API webhooks

Why it fails: Marketing Cloud is an external channel tool, not the mechanism for embedding insights in Sales Cloud page layouts.

Salesforce Outbound Messaging

Why it fails: Outbound messaging does not render UI components in Lightning record pages.

Automatic physical deletion of data across all global data centers within 1 second of a consent revocation.

Why it fails: Data Spaces partition data by region, team or purpose for access control; they do not execute physical deletion. Consent revocation triggers policy enforcement, not cross-datacentre erasure within one second. This option is tempting because Data Spaces support compliance-driven segregation, but deletion is handled by retention policies and data management tooling.

Elimination of all credit consumption limits within partitioned environments.

Why it fails: Data Spaces isolate data and metadata by business unit or region; they do not alter billing meters or credit consumption limits, which remain governed by contract and platform entitlements. It tempts because partitioning affects query scope, yet credit accounting operates independently of Data Space boundaries.

Automatic generation of encryption keys for HIPAA compliance.

Why it fails: Data Spaces partition data and metadata by user group for segregation; encryption key generation is handled by platform security services, not Data Spaces. It tempts because Data Spaces support compliance boundaries, but they enforce access and visibility segmentation rather than cryptographic key lifecycle management.

The user is logged into Sales Cloud instead of Marketing Cloud.

Why it fails: User login location does not dictate schema segmentation availability in Data Cloud.

Calculated Insights must be created first to expose fields.

Why it fails: Calculated Insights are not required for standard data mapping.

The Data Stream needs to be paused and resumed to refresh metadata cache.

Why it fails: Pausing a stream does not resolve unmapped schema metadata.

The streaming platform requires manual schema publication via API.

Why it fails: Salesforce manages schema publication natively through the UI mapping interface.

Use Calculated Insights to overwrite the primary key values.

Why it fails: Calculated Insights cannot alter core DMO primary key definitions.

Create a custom DMO for each source object and merge them using an external ETL tool.

Why it fails: External ETL tools are unnecessary because Data Cloud's data model mapping and Identity Resolution natively handle multiple sources.

Transform the keys using an Apex trigger before ingestion.

Why it fails: Data Cloud ingestion does not support custom Apex triggers for data stream pre-processing.

Manual CSV uploads daily

Why it fails: Manual CSV uploads are batch, scheduled transfers, so behavioural data arrives hours or a day late and cannot drive ongoing journey personalisation. Streaming ingestion via APIs or connectors suits near-real-time tracking; CSV uploads fit historical backfills or one-off data loads.

Cloud File Storage ingestion via Amazon S3

Why it fails: S3 ingestion requires files to be exported and staged before Data Cloud ingests them, adding latency incompatible with near-real-time tracking. It is tempting because cloud file storage suits scheduled bulk loads of large datasets, and would be correct when source systems already publish parquet or CSV extracts.

Marketing Cloud Connector via SOAP API batch job

Why it fails: SOAP API batch jobs run on a schedule, so behavioural events arrive minutes or hours late, not near-real-time. It is tempting because the Marketing Cloud Connector is the native integration path for bulk subscriber and journey data, and would be right for periodic synchronisation rather than streaming engagement events.

Standard Data Stream bundle with scheduled syncs

Why it fails: Standard data streams replicate data into Data Cloud, creating duplicate storage and ingestion overhead.

Ingestion API push streaming

Why it fails: Ingestion API pushes data into Data Cloud storage, which introduces storage duplication.

Amazon S3 Cloud File Storage batch connector

Why it fails: S3 connector copies and stages data into Data Cloud storage, failing the requirement to avoid storage duplication.

Marketing Cloud Engagement Journey Builder API integration

Why it fails: Journey Builder API is used for marketing orchestration, not for rendering Data Cloud insights on Sales Cloud page layouts.

Direct SOQL query from Sales Cloud triggers

Why it fails: Sales Cloud triggers cannot natively execute direct SOQL queries against the Data Cloud data lakehouse storage layer.

Batch CSV export imported nightly via Data Loader

Why it fails: Batch CSV exports introduce high latency and manual overhead, violating real-time CRM visibility best practices.

The data streams were not refreshed

Why it fails: While possible, mapping errors are more common during initial setup.

The identity rule is set to 'Manual'

Why it fails: Rulesets don't have a 'manual' toggle that prevents unification.

The Data Space was not set to active

Why it fails: If a Data Space is inactive, ingestion wouldn't occur at all.

Custom API calls

Why it fails: Custom API calls require bespoke development and authentication handling, and they do not render Data Cloud calculated insights natively on a Lightning record page. They are tempting because APIs do expose Data Cloud data programmatically, which suits external systems or middleware integrations rather than embedded record-page display.

Visualforce Page

Why it fails: Visualforce renders custom pages using Apex controllers, so displaying Data Cloud insights demands bespoke controller code and offers no standard Data Cloud record-page component. It is tempting because Visualforce can embed on record pages, but it is legacy UI technology rather than the supported integration for calculated insights.

Salesforce Flow

Why it fails: Salesforce Flow automates records and business processes but has no native component that surfaces Data Cloud calculated insights on a Lightning record page. It is tempting because Flow can call external services, yet that requires custom Apex or HTTP callouts rather than the purpose-built Data Cloud record-page component.

JSON

Why it fails: Raw JSON files are not directly supported for batch ingestion.

XML

Why it fails: XML is not a supported format for S3 ingestion.

Excel (XLSX)

Why it fails: Excel files must be converted to CSV first.

Apex Trigger

Why it fails: Apex is not used for Data Cloud ingestion.

Data Space exclusion

Why it fails: Excluding data from a Data Space does not prevent API stress.

Formula fields

Why it fails: Formula fields are for data transformation, not ingestion optimization.