CCNA Data Cloud Overview Questions — Page 2 of 2

MCQhard

An enterprise customer has deployed Data Cloud and is utilizing Marketing Cloud Engagement as an activation target. The marketing team notices that serialized custom attributes from a Data Cloud Calculated Insight are not appearing in Marketing Cloud Engagement Data Extensions. Upon troubleshooting, the consultant finds that the Calculated Insight is scheduled correctly. What is the most likely root cause?

A.Marketing Cloud Engagement requires Real-Time Data Graph activation for all Calculated Insights.

B.The Calculated Insight output has not been mapped to an Activation-enabled Data Model Object.

C.Calculated Insights cannot be exported to Marketing Cloud Engagement due to API limits.

D.Activation targets only support streaming data streams, not batch-based Calculated Insights.

AnswerB

Activation only streams fields from an Activation-enabled Data Model Object, so a Calculated Insight feeding an unmapped DMO cannot reach Marketing Cloud Engagement Data Extensions. Mapping the insight output to that DMO satisfies the activation constraint.

Why this answer

The most likely root cause is that the Calculated Insight output has not been mapped to an Activation-enabled Data Model Object. Calculated Insights produce metrics that are stored in a Data Model Object (DMO), but for those metrics to be activated to Marketing Cloud, the DMO must be marked as activation-enabled and the specific fields must be included in the activation. If the mapping is missing, the attributes won't appear in Data Extensions.

Exam trap

The trap is assuming that scheduling the Calculated Insight is enough for activation; candidates might overlook the need to map the insight output to an activation-enabled DMO and include it in the activation.

How to eliminate wrong answers

Option A is wrong because Marketing Cloud Engagement does not require Real-Time Data Graph activation for all Calculated Insights; activation can be batch or streaming depending on the setup. Option C is wrong because Calculated Insights can be exported to Marketing Cloud Engagement; API limits are not the primary cause of missing attributes. Option D is wrong because activation targets support both streaming and batch data, including Calculated Insights; the issue is not the data type but the mapping.

Practice this question →

MCQmedium

A consultant is setting up a new Data Cloud org for a retail company. The company's data engineering team needs to understand how Data Cloud stores and unifies data. Which statement accurately describes the role of the Individual Data Model Object (DMO) in Data Cloud?

A.It is a raw data stream that ingests data directly from external sources without transformation.

B.It is a configuration object that defines the mapping between source fields and target fields during data stream creation.

C.It is a standardized data model that represents a unified individual and is used for identity resolution and segmentation.

D.It is a temporary storage area for data that is being processed by data transforms before being written to a DLO.

AnswerC

The Individual DMO is a pre-defined, harmonized data model that consolidates identity information from multiple sources. It serves as the foundation for identity resolution, creating unified profiles used in segmentation and activation. For a retail company, this DMO enables a single view of each customer across channels, which is exactly what the data engineering team needs to understand.

Why this answer

The Individual DMO is a core harmonized data model in Data Cloud that represents a person and consolidates identity data from multiple sources. It supports identity resolution, segmentation, and activation by providing a unified profile. The other options describe ingestion or configuration components, not the standardized model used for unification.

Exam trap

The trap here is confusing the Individual DMO with raw ingestion objects like DLOs or with mapping configurations, which are separate layers in the Data Cloud architecture.

Practice this question →

Multi-Selectmedium

A Data Cloud Consultant is configuring real-time data ingestion using the Ingestion API. Which THREE technical requirements must be met to ensure successful API ingestion? (Choose three.)

Select 3 answers

A.Valid OAuth 2.0 authentication token generated via connected app

B.Manual CSV file upload via the CRM Data Loader

C.Correct regional endpoint URL for the Data Cloud instance

D.Payload structured to match the expected schema of the target Data Stream / DLO

E.Installation of a managed package on all customer mobile devices

AnswersA, C, D

Ingestion API calls must carry a valid OAuth 2.0 access token issued through a connected app with the appropriate scopes. Without this token the request is unauthenticated and rejected, so valid OAuth 2.0 authentication is a hard requirement for ingestion.

Why this answer

Option A is correct because the Ingestion API requires OAuth 2.0 authentication, and the token must be generated through a connected app configured with the appropriate scopes for Data Cloud ingestion. Option C is correct because requests must be sent to the correct regional endpoint URL for the specific Data Cloud instance; using the wrong region or endpoint will cause the API call to fail. Option D is correct because the JSON payload must conform to the schema defined for the target Data Stream and its underlying Data Lake Object (DLO), including required fields and correct data types, or ingestion will be rejected.

Option B is incorrect because manual CSV upload via CRM Data Loader is a batch/file-based ingestion method, not real-time Ingestion API usage. Option E is incorrect because installing a managed package on customer mobile devices is unrelated to server-side API ingestion into Data Cloud.

Exam trap

The trap is selecting options that seem plausible but are not technical requirements for the Ingestion API, such as CSV upload or mobile package installation; candidates must focus on authentication, endpoint, and schema.

Practice this question →

MCQmedium

A Data Cloud Consultant is working with a marketing team that wants to activate a segment to Google Ads. The team needs to ensure that the audience is updated daily. Which feature should the consultant use to automate this process?

A.Data Action

B.Activation Schedule

C.Calculated Insight

D.Data Stream Refresh

AnswerB

Activation schedules in Data Cloud allow you to define how often a segment is published to an activation target, such as Google Ads. You can set a daily schedule to ensure the audience is refreshed regularly. This is the standard method for automating segment activation to external platforms.

Why this answer

Activation schedules define the frequency at which a segment is published to a connected activation target. By setting a daily schedule, the marketing team can ensure Google Ads receives updated audiences automatically. Other features like Data Actions or Calculated Insights serve different purposes and do not provide the required scheduling for activation.

Exam trap

The trap here is confusing data ingestion refresh with activation scheduling; they are separate processes, and only activation schedules control outbound segment publishing.

Practice this question →

MCQmedium

A consultant is mapping an ingested Data Lake Object that contains customer email addresses into the Data Cloud data model. The goal is to prepare the data so identity resolution can match individuals by email. Which type of Data Model Object should the email addresses be mapped into to support this matching?

A.Contact Point Email DMO

B.Party Identification DMO

C.Account DMO

D.Individual DMO

AnswerA

The Contact Point Email DMO is the standardized object for email address values that link to an individual. Identity resolution uses match rules against contact point DMOs such as this one to find and unify individuals sharing the same email. Mapping the ingested emails here is exactly what enables email-based matching during identity resolution.

Why this answer

Email addresses are contact points, so they belong in the Contact Point Email DMO, which links email values back to the individual. Identity resolution match rules then compare these contact points to find and unify individuals who share an email. The Individual DMO holds the person, the Party Identification DMO holds identifiers like loyalty numbers, and the Account DMO represents organizations, so none of those is the correct target for email data.

Exam trap

The trap here is mapping email addresses directly into the Individual DMO, when email values must live in the Contact Point Email DMO for identity resolution match rules to use them.

Practice this question →

MCQmedium

A marketing team wants to target customers who have made a purchase in the last 30 days but have not opened an email in the last 7 days. Where should the marketer build this audience criteria?

A.Sales Cloud Report Builder with joined reports

B.Data Cloud Segmentation canvas

C.Calculated Insights SQL editor

D.Marketing Cloud Engagement Journey Builder decision splits only

AnswerB

The Segmentation canvas in Data Cloud builds multi-dimensional audiences by combining purchase and engagement data streams. It lets the marketer express the two conditions — purchase within 30 days AND no email open within 7 days — as related attributes, producing the required unified profile segment.

Why this answer

Audience segments in Data Cloud are created in the Segmentation canvas using harmonized data model objects and attribute operators.

Practice this question →

Multi-Selecthard

A consultant is explaining the primary capabilities that Data Cloud provides as a platform to a customer's architecture review board. Which two statements accurately describe core Data Cloud platform capabilities? (Choose two.)

Select 2 answers

A.It guarantees sub-second real-time identity resolution across every ingested source automatically.

B.It ingests and harmonizes data from multiple sources into a unified customer profile.

C.It replaces the need for a CRM by storing all transactional sales records natively.

D.It provides a full extract, transform, load engine that permanently copies all source data into Salesforce storage.

E.It activates unified data to external and internal destinations such as Marketing Cloud and ad platforms.

AnswersB, E

A foundational Data Cloud capability is bringing in data from many sources through data streams, harmonizing it into DMOs via mappings, and reconciling it into a unified individual profile using identity resolution. This zero-copy style ingestion and unification is central to the platform's purpose and is exactly what the architecture board needs to understand as the core value.

Why this answer

Data Cloud's defining capabilities are ingesting and harmonizing multi-source data into a unified customer profile and activating that unified data to internal and external destinations. These two together describe the platform's core purpose. It does not replace CRM systems of record, it is not a permanent bulk-copy ETL engine, and identity resolution is scheduled rather than guaranteed sub-second, so those statements misrepresent how the platform actually works.

Exam trap

The trap here is conflating Data Cloud's harmonize-and-activate role with being a system of record or a continuous real-time engine, when unification actually runs on a schedule.

Practice this question →

Multi-Selectmedium

Which TWO statements accurately describe the role and function of Calculated Insights in Data Cloud? (Choose two.)

Select 2 answers

A.They are used exclusively for raw data stream parsing before data mapping.

B.They can be utilized as attributes during audience segmentation.

C.They enable the creation of aggregated metrics and KPIs across unified profiles using SQL or builder interfaces.

D.They automatically update source systems in Salesforce CRM via real-time webhooks.

E.They replace the need for Identity Resolution rulesets entirely.

AnswersB, C

Because Calculated Insights materialise computed measures onto unified individual profiles, those values become available as profile attributes. Segmentation can then filter on them, letting audiences target members by computed metrics rather than only source-data fields.

Why this answer

Calculated Insights allow users to aggregate metrics using SQL or a builder, and these metrics become available as attributes in segmentation.

Practice this question →

MCQeasy

Universal Containers wants to implement Data Cloud to unify customer data from multiple sources across Sales Cloud, Marketing Cloud Engagement, and an external legacy order management system. Which architectural component should the consultant recommend as the foundational layer to ingest and normalize this data?

A.Activation Targets

B.Data Streams

C.Data Spaces

D.Calculated Insights

AnswerB

Data Streams provide the foundational ingestion layer that connects to Sales Cloud, Marketing Cloud Engagement and the external order management system, then maps and normalises each source's schema into the Data Cloud data model before harmonisation, making them the correct starting component for unifying this multi-source customer data.

Why this answer

Data Streams are the foundational ingestion layer in Data Cloud. They connect to source systems (Sales Cloud, Marketing Cloud Engagement, external systems via S3, Snowflake, etc.) and bring raw data into Data Lake Objects (DLOs), which are then mapped and transformed into Data Model Objects (DMOs). Without Data Streams, no data enters Data Cloud, so they are the correct foundational component for ingesting and normalizing multi-source data.

Exam trap

The trap is confusing ingestion with organization or activation — candidates pick Data Spaces because they sound foundational, but Data Spaces only partition data after Data Streams have already ingested it.

How to eliminate wrong answers

Option A is wrong because Activation Targets are the outbound layer — they publish segments to destinations like Marketing Cloud or S3, not ingest data. Option C is wrong because Data Spaces are logical partitions that isolate data by brand, region, or business unit; they organize data after ingestion but do not perform ingestion or normalization themselves. Option D is wrong because Calculated Insights are derived metrics computed from DMOs (e.g., lifetime value, engagement score) and run after data is already ingested and modeled, not as the foundational ingestion layer.

Practice this question →

MCQhard

An enterprise customer using Data Cloud wants to calculate the total lifetime value (LTV) of a customer using a complex SQL query that joins multiple Data Model Objects (Individual, Order__c, and Invoice__c). Which feature should the consultant use to build this metric?

A.Identity Resolution Ruleset

B.Data Model Mapping

C.Calculated Insights

D.Segmentation Builder

AnswerC

Calculated Insights run multi-dimensional SQL across Data Model Objects such as Individual, Order__c and Invoice__c, materialising the aggregated LTV metric for reuse in segmentation and analytics. This satisfies the requirement for a complex joined SQL calculation rather than a simple streaming transformation.

Why this answer

Calculated Insights in Data Cloud are purpose-built for computing aggregate metrics (sums, counts, averages, complex joins) across DMOs and storing the results as a Calculated Insight DMO that can be used in segments, activations, and personalization. A complex SQL query joining Individual, Order__c, and Invoice__c to compute lifetime value is exactly the Calculated Insight use case. The resulting metric is materialized and refreshed on a schedule, making it queryable at scale.

Exam trap

The trap is confusing Calculated Insights (compute metrics) with Segmentation (filter profiles) — candidates pick Segmentation Builder because LTV sounds like a targeting criterion, but the computation itself requires Calculated Insights.

How to eliminate wrong answers

Option A is wrong because Identity Resolution Rulesets unify records into profiles — they do not compute aggregate metrics like LTV. Option B is wrong because Data Model Mapping maps source fields to DMO fields during ingestion; it has no aggregation or SQL computation capability. Option D is wrong because Segmentation Builder filters unified profiles based on criteria — it can consume a Calculated Insight as an attribute but cannot itself perform multi-object SQL joins to compute LTV.

Practice this question →

MCQmedium

A Data Cloud Consultant is configuring real-time data ingestion using the Ingestion API. Which artifact must be created and published in Data Cloud before sending payload data from an external web application?

A.A Salesforce CRM Custom Object with Change Data Capture enabled

B.An Inbound Streaming Data Source and associated Data Stream schema

C.A standard Marketing Cloud Data Extension

D.A Tableau Hyper file upload definition

AnswerB

The Ingestion API writes into an Inbound Streaming Data Source, whose Data Stream schema defines the accepted object and fields. Publishing both first gives the external web application a valid endpoint and contract, so payloads are accepted rather than rejected.

Why this answer

The Ingestion API requires a pre-configured Inbound Streaming Data Source and its associated Data Stream schema to define the endpoint and structure for incoming real-time payloads. This artifact acts as the contract that validates and maps the JSON data sent from the external web application into Data Cloud. Without it, the API has no target schema or connection point to accept the data.

Exam trap

Data 360 Consultant often tests the confusion between batch and streaming ingestion artifacts, leading candidates to select CRM-based options like Change Data Capture instead of the required Inbound Streaming Data Source and Data Stream schema.

How to eliminate wrong answers

Option A is wrong because Change Data Capture on a CRM Custom Object is for replicating Salesforce internal record changes, not for external real-time ingestion via the Ingestion API. Option C is wrong because a Marketing Cloud Data Extension is a storage table within Marketing Cloud, not a Data Cloud ingestion artifact, and it does not provide an API endpoint for streaming. Option D is wrong because a Tableau Hyper file upload definition is used for batch file ingestion into Tableau, not for real-time streaming into Data Cloud.

Practice this question →

MCQmedium

During the data harmonization phase in Salesforce Data Cloud, a consultant notices that incoming contact records from Sales Cloud and Commerce Cloud use different field names for email addresses. Where should the consultant map these disparate source fields to a unified enterprise data model field?

A.Identity Resolution Ruleset configuration

B.Data Stream Field Mapping canvas

C.Calculated Insights SQL editor

D.Activation Target configuration panel

AnswerB

The Data Stream Field Mapping canvas maps each source field, such as the differing email names from Sales Cloud and Commerce Cloud, to the corresponding Data Cloud Data Model Object field, harmonising them into one unified enterprise schema.

Why this answer

The Data Stream Field Mapping canvas is where source fields from ingested DLOs are mapped to target DMO fields in the Customer 360 data model. This is the harmonization step that unifies disparate source schemas (e.g., Sales Cloud's Email vs. Commerce Cloud's EmailAddress) into a single canonical field like Contact Point Email.

Mapping happens after ingestion and before Identity Resolution or segmentation.

Exam trap

Data 360 Consultant often tests whether candidates know that harmonization (field mapping) is a distinct step from Identity Resolution — the trap is selecting Identity Resolution for a mapping question because both involve unifying data.

How to eliminate wrong answers

Option A is wrong because Identity Resolution Rulesets operate on already-mapped DMO fields to match and reconcile profiles — they do not perform source-to-target field mapping. Option C is wrong because Calculated Insights SQL editor is used to compute metrics and derived attributes, not to map source fields to the data model. Option D is wrong because Activation Target configuration defines where segments are sent (e.g., ad platforms), not how source fields are harmonized into the model.

Practice this question →

MCQeasy

Which of the following describes the 'Cloud Information Model' (CIM) in Data Cloud?

A.A standard object framework for data mapping

B.A marketing automation tool

C.A tool for generating reports

D.An open-source database

AnswerA

The Cloud Information Model provides a standardised object framework and schema for mapping source data into Data Cloud. It supplies common definitions so disparate systems' data can be harmonised consistently, satisfying the need for a shared mapping structure.

Why this answer

The Cloud Information Model (CIM) is a standard object framework and data model that provides a common set of objects, attributes, and relationships for mapping data into Data Cloud. It enables interoperability and consistency across different data sources by aligning them to a shared schema.

Exam trap

The trap is confusing CIM with a specific tool or database, when it is actually a standardized data model framework used for mapping and harmonization.

How to eliminate wrong answers

Option B is wrong because CIM is not a marketing automation tool; it is a data model. Option C is wrong because CIM is not a reporting tool; reporting is handled by CRM Analytics or Data Cloud reports. Option D is wrong because CIM is not an open-source database; it is a conceptual model, not a database engine.

Practice this question →

MCQmedium

A Data Cloud Consultant is designing an integration where external clickstream events must be ingested into Data Cloud with sub-second latency. Which ingestion method is architecturally designed for this use case?

A.Amazon S3 Batch Connector

B.Salesforce CRM Standard Connector

C.Scheduled CSV Data Import wizard

D.Data Cloud Ingestion API

AnswerD

The Ingestion API streams records in near real time through REST endpoints, supporting the sub-second latency the clickstream scenario demands. Unlike batch connectors or bulk imports, it accepts continuous event payloads immediately, making it the architecturally intended path for high-velocity external event data.

Why this answer

The Data Cloud Ingestion API is designed for real-time, sub-second latency ingestion of external data, including clickstream events. It supports high-throughput streaming and is optimized for low-latency use cases. Other methods like batch connectors or scheduled imports are not suitable for sub-second latency.

Exam trap

The trap is assuming that any connector can achieve sub-second latency, but only the Ingestion API is architected for real-time streaming.

How to eliminate wrong answers

Option A is wrong because Amazon S3 Batch Connector is for batch data loads, not real-time streaming. Option B is wrong because Salesforce CRM Standard Connector is for CRM data, not external clickstream, and may not provide sub-second latency. Option C is wrong because Scheduled CSV Data Import is a batch process with delays, not real-time.

Practice this question →