CCNA Data Cloud Overview Questions

Fuzzy matching rules, including match rules and reconciliation thresholds, are configured within the Identity Resolution Ruleset, which governs how Data 360 compares and unifies profiles. This satisfies the stem's requirement that the fuzzy-match logic be defined there rather than in data streams or segments.

Data streams first land data in a Data Lake Object, and a separate mapping step harmonizes fields into the target Data Model Object. If the mapping for the order total field was not saved or was left incomplete, the raw values remain available in the DLO while the DMO field stays empty. Verifying the stream's success does not confirm the mapping, which is a distinct configuration step.

Meta Custom Audiences is a native Data Cloud activation target, satisfying the requirement to activate segments across digital advertising channels. Data Cloud connects directly to Meta's Marketing API, syncing segment membership to Custom Audiences without middleware. This removes the need for manual CSV exports or third-party integration tooling.

Zero-copy architecture shares CRM data through native data streams rather than ingesting and storing a duplicate copy, so Sales Cloud and Service Cloud records remain authoritative while Data Cloud unifies them. This satisfies the no-duplication constraint on core CRM storage.

DLOs form the raw ingestion storage layer in Data Cloud, holding data in its source-native shape before harmonisation into Data Model Objects. Marketing Cloud, Service Cloud and Ingestion API feeds all land here first, satisfying the requirement for a foundational landing layer ahead of harmonisation.

Mismatched JSON structures or missing required fields cause ingestion failures against the target DLO schema.

Standard connectors for Salesforce CRM and Marketing Cloud Engagement ship with every Data Cloud edition, since Data Cloud's core purpose is unifying Salesforce and Marketing Cloud data. This satisfies the base-licence constraint: these connectors require no premium add-on, unlike advanced or external connectors.

Identity Resolution evaluates match rules against Data Model Objects populated from ingested data streams, then uses reconciliation rules to determine the winning values. Matched profiles are connected through the Unified Link Object, which maps source DMOs to the Unified Individual DMO, enabling a single consolidated view of the person across Sales Cloud and Service Cloud even when identifiers differ.

A Data Stream connects to a source system and ingests its data into Data Cloud, defining the source, objects and refresh cadence. Data Model Objects then map that ingested data for harmonisation and identity resolution downstream.

Calculated Insights and Data Graphs are exposed to CRM users through Lightning components, letting Sales and Service reps view computed metrics and relationship data without leaving their record pages. This satisfies the requirement that Data Cloud insights surface directly inside existing Salesforce cloud interfaces.

Identity Resolution applies deterministic and fuzzy matching rules across Sales Cloud and Marketing Cloud Engagement source profiles, reconciling them into one Unified Individual. It is the specific Data Cloud feature that performs the merge, satisfying the unification requirement.

Calculated Insights computes and stores aggregate metrics, such as total order amount over a rolling 90-day window, directly on Data Cloud data. Those stored values then serve as attributes for audience segmentation without recalculating the aggregation at query time.

The Data Model Object is the harmonized, canonical layer in Data Cloud that holds standardized entities such as Individual, Contact Point, Sales Order, and Engagement. Source data lands first in Data Lake Objects, then is mapped and transformed into DMOs. Segmentation, calculated insights, and activation all query DMOs, so the DMO is the correct object type for the consultant to identify as the standardized model.

Data Model Objects are the harmonised, canonical schema in Data Cloud, mapping ingested source data into a unified model. They form the storage and modelling layer of the core architecture, distinct from raw Data Lake Objects.

Mapping ingested Marketing Cloud data streams to Data Model Objects such as Individual and Contact Point is essential because Data Cloud's harmonisation layer requires source fields aligned to standard DMO schemas before identity resolution and segmentation can run. Without this mapping, ingested engagement data remains unlinked and unusable for the unified profile the integration exists to build.

Salesforce Data Cloud Starter, Growth and Plus editions each bundle the foundational capabilities the scenario requires: data ingestion, data mapping and identity resolution. These tiered editions scale by data volume and advanced features, so any of them satisfies the stem's demand for core functionality without requiring separate add-on licences.

Rule evaluation tools and sample data reveal actual match volumes before deployment, exposing over-merging where unrelated individuals collapse into one profile. This directly satisfies the stem's multiple-source constraint, since overlapping identifiers across systems inflate false matches that only empirical testing exposes.

Exceeding Data Cloud's query complexity or join limits causes compilation to fail before execution, directly satisfying the stem's compile-and-execute failure scenario. Calculated Insights enforce hard caps on joins and complexity, so an over-complex definition is rejected at compile time rather than returning partial results.

Identity resolution profile scale and matching compute complexity directly govern Data Cloud's processing limits, since match rules execute against every profile during runs. Evaluating these during discovery satisfies the stem's architectural-limits constraint, exposing whether volume and rule complexity exceed supported thresholds before design commits to a matching strategy.

Change Data Capture streams record changes from Sales Cloud as they occur, delivering near real-time updates rather than batch extracts. A CRM Data Stream configured with CDC therefore satisfies the near real-time ingestion requirement for customer profile updates.

The Customer 360 Data Model supplies a standardised, prebuilt schema of objects and relationships, letting data from disparate sources be mapped and harmonised into consistent customer profiles. This standardisation is its primary function within Data Cloud.

Consent Management and Privacy Preferences mapping stores each individual's consent and privacy choices against the unified profile, so Data Cloud enforces GDPR obligations when processing customer data. It directly addresses the requirement to manage consent across unified profiles.

Data Spaces partition a single Data Cloud org into isolated segments, letting each business unit's data, users and permissions stay logically separated. This satisfies the requirement for strict governance and regional separation between North America and Europe without deploying separate instances.

Data Spaces partition data and metadata into isolated virtual segments, and Data Space-aware permission sets restrict user access within each segment. This enforces row-level isolation for the high-net-worth accounts, blocking standard regional business units from querying that data even inside Calculated Insights.

Data Model Objects (DMOs) are the layer where ingested data is mapped to the standard Customer 360 data model, satisfying the stem's requirement for the layer holding harmonised, model-aligned data. DMOs sit above raw ingestion and below semantic/calculated insights, forming the foundational harmonised representation in Data Cloud.

Streaming or frequent scheduling is required because the marketing team needs activation every 15 minutes. Standard batch activation runs on longer intervals, so configuring the schedule to the most frequent cadence the advertising platform supports meets the 15-minute refresh requirement.

The standard Salesforce CRM Connector with streaming enabled pushes Service Cloud case changes into Data Cloud near real time, satisfying the stem's requirement for immediate triggering. It uses the native connector rather than batch ingestion, so latency stays low.

Identity Resolution compares every incoming record against existing profiles, so a larger profile store directly increases the number of pairwise match evaluations performed. The stem's performance constraint is therefore satisfied: higher total record volume lengthens processing time and raises compute consumption during graph construction.

Match rule order determines precedence: the first rule producing a match links records, so sequencing controls which identifiers pair before later rules run. Misordering causes false merges or missed links across e-commerce, POS and loyalty sources, directly shaping reconciliation outcomes.

Cloud File Storage such as Amazon S3 is a native Activation Target, letting Data Cloud segments be written directly to a customer-owned bucket for downstream processing. It satisfies the multi-channel requirement by covering file-based delivery alongside the other supported destination types.

Data Cloud supports ingesting flat files placed on an SFTP location through a file-based data stream. Because the loyalty system is not a native connector and delivers a nightly batch file, SFTP ingestion matches the delivery method exactly. The consultant configures the stream against the SFTP path and schedules it, so each nightly file is picked up and loaded for downstream mapping into Data Model Objects.

Data Spaces partition a Data Cloud org into logical, region-scoped containers, so each space holds its own data streams, segments and metadata. Assigning users to the APAC or EMEA space enforces the required administrative visibility boundaries and restricts ingestion per region, satisfying the strict regional isolation constraint.

Identity resolution jobs and segmentation runs consume Data Cloud credits because each reconciles profiles and evaluates segment membership across the dataset. These processing operations are metered separately from ingestion, satisfying the architect's need to identify direct credit consumption components.

Data Spaces partition data and metadata so users only see and act on permitted segments, activations, and calculated insights. This satisfies the stem's requirement for granular, scoped access control rather than tenant-wide visibility, enforcing least-privilege boundaries across those specific Data Cloud artefacts.

The Amazon S3 Connector in Data Cloud supports ingesting data from S3 buckets and can be configured for incremental refresh. It allows scheduling of data streams to run at specified intervals, such as hourly. This connector is specifically designed for S3, making it the correct choice for this scenario.

The Calculated Insights Builder is the dedicated interface where aggregation logic for metrics such as Lifetime Value is defined. It lets consultants author the SQL-like expressions and dimensional relationships that compute LTV across Data 360 data streams, satisfying the requirement to build the aggregation logic itself.

Calculated Insights compute metrics such as lifetime value in Data Cloud, and exposing them through Lightning Web Components or related lists surfaces that real-time value directly on the Case page layout, satisfying the requirement for agents to view it without leaving Service Cloud.

Identity resolution consumes the primary processing capacity because match and reconciliation rules compare every source record against the ruleset to determine Unified Individuals. The volume of disparate records drives the compute cost, not storage or ingestion, so ruleset execution is the bottleneck during these runs.

The Data Cloud for Marketing SKU is the licensing prerequisite that provisions the Marketing Cloud Connector and enables synchronised data extensions to be used for segmentation. Without this entitlement, the connector cannot be configured regardless of other settings.

Cloud File Storage Data Stream ingests files such as JSON from cloud object stores including Amazon S3, matching the hourly raw JSON arrival pattern. This satisfies the requirement to connect to an enterprise S3 bucket without building a bespoke API integration.

Identity Resolution matches on normalised values, so case differences between uppercase and lowercase email prevent matches. Applying a lowercase transformation during data stream mapping normalises both sources before matching, resolving the case-sensitivity constraint described in the stem.

Nested AND/OR containers let you group the California-or-New York condition separately, then combine it with the purchase-amount filter using AND. A flat set of filters cannot express that mixed precedence, so nesting satisfies the stem's compound logic requirement.

Segments based on unified individuals require the Unified Individual DMO as the base, since it represents the consolidated profile linking subscriptions and support cases. This satisfies the stem's constraint of targeting unified individuals possessing both attributes simultaneously.

Data Model Objects hold the harmonized, canonical entities such as Individual and Sales Order that segmentation, calculated insights, and activation query. They are populated by mapping source data from Data Lake Objects. Because they define the standardized schema the rest of the platform relies on, they are a foundational building block alongside ingestion streams in any Data Cloud implementation.

Data Cloud requires Enterprise Edition or above because lower tiers lack the underlying platform entitlements and API allocations that Data Cloud provisioning depends on. Enterprise, Performance, Unlimited and Developer editions include the necessary Data Cloud SKU access, satisfying the stem's edition constraint directly.

Reconciliation Rules define which source field value wins when matched records disagree, so configuring the First Name rule to prefer System B's capitalised value resolves the conflict. Identity Resolution matching alone only links records; it does not decide attribute precedence, which is exactly the constraint in the stem.

Identity resolution applies match and reconciliation rules across source profiles to determine which records refer to the same person, then produces a unified Individual Data Model Object. That unified profile is the anchor for segmentation, calculated insights, and activation. Describing the outcome as a unified Individual DMO that links source profiles correctly reflects what identity resolution produces and how downstream features consume it.

Selecting the target DMO determines which Individual Data Model Object receives the mapped fields, ensuring the raw DLO's attributes land on the correct entity and its standard fields. Without a defined target DMO, field-level mapping cannot be validated against the model's schema, so this satisfies the stem's requirement for a critical mapping component.

Calculated Insights are a native Data Cloud feature that run metric definitions over harmonized and unified data, producing values such as lifetime value or engagement scores. These insights can be activated or surfaced into Salesforce experiences so that business users see them in context. This capability depends on prior ingestion, harmonization, and often identity resolution, but once configured it delivers computed metrics natively within the platform.

Exact match rules on Email and Phone Number cannot detect spelling variants. Adding a fuzzy match rule on Party Identification or Name lets the ruleset correlate similar names, merging records that share an email despite minor spelling differences.

Data Spaces partition a single Data Cloud org into logical, governed segments, letting Retail and B2B ingest, segment and activate independently. This directly satisfies the isolation and governance constraint by scoping users, data and processes per space rather than duplicating the instance.

Reconciliation rules define which source value survives per attribute when matched records conflict, producing the golden record's field-level values. This satisfies the unification requirement, complementing match rules that determine which records link together in the first place.

Streaming ingestion, through the Ingestion API or a streaming connector, is designed to bring event data into Data Cloud with low latency as events occur. It suits high-volume clickstream and page-view data where near-real-time availability matters. This is the ingestion pattern built for continuous, low-latency event feeds, making it the best fit for the stated requirement.

Data Cloud streams require an authorised source connection before ingestion. Establishing and authorising the Commerce Cloud connection in Data Cloud Setup supplies the credentials and consent the connector needs, so it must precede creating the Commerce Cloud data stream.

The Amazon S3 Cloud File Storage connector authenticates to the bucket and defines the source object, while a Data Stream applies the recurring ingestion schedule into Data Cloud. Together they satisfy the requirement to pull transactional logs on a repeating basis.

Data Cloud Setup and Home dashboard surfaces consumption metrics for the org, including credit usage, data storage and query volumes. It is the Setup-resident tool that aggregates these usage figures, satisfying the administrator's need to check total consumption in one place.

An Activation Target defines the destination (Marketing Cloud Engagement) and the Activation defines which segment and attributes flow to it. Together they push Data Cloud segment membership into Marketing Cloud Engagement, enabling journeys to consume those audiences directly.

Mapping transformation formulas let you parse the source's non-ISO 8601 timestamp and convert it to the expected format before ingestion, so records are no longer skipped. This directly satisfies the stem's constraint that the source timestamp format mismatches the expected ISO 8601 structure.

A Data Stream defines how the raw file schema is read and ingested, landing records into a Data Source Object that later maps to the data model. It satisfies the ingestion-and-mapping requirement by giving the file a structured target.

Ingesting engagement data into Data Lake Objects first, mapping those DLOs to the Individual and engagement DMOs, then applying Identity Resolution rules links email opens and clicks to the correct unified Individual profiles. This ordering satisfies the association requirement in the stem.

Data Spaces enable logical partitioning of data, metadata, and processes. Each space can have its own data streams, DMOs, and permissions, allowing teams to operate autonomously. For a client with multiple business units, this means marketing, sales, and service can manage their own data without cross-contamination, while still leveraging a single Data Cloud instance.

Data Spaces partition data and metadata, and Data Space-level permissions restrict users to objects, segments and insights belonging to their own space. This enforces the boundary preventing UK users from viewing French customer records or segments.

Authentication is required for secure data transfer.

The Ingestion API accepts authenticated REST calls, letting AWS compute instances stream custom event data directly into Data Cloud without intermediary storage, satisfying the requirement to ingest from external AWS services in near real time.

Data Cloud ingests data from Salesforce clouds and external systems, harmonizes it into Data Model Objects, resolves identities into Unified Individuals, and enables segmentation and activation to destinations such as Marketing Cloud or advertising platforms. This unifying, activating role across many sources is the core value proposition and the accurate high-level description for a customer workshop.

Amazon S3 is a natively supported Data Cloud connector, so ingestion occurs directly through the built-in connector framework rather than custom middleware. This satisfies the stem's constraint of direct integration without bespoke code, letting consultants pull cloud-storage objects into Data Cloud using standard configuration.

The data stream's configuration defines the file format and character encoding applied during ingestion, so encoding mismatches for special characters are resolved there. Adjusting the character encoding setting to match the source database's actual encoding (for example UTF-8) directly satisfies the stem's requirement to correct failed records.

Data Spaces logically partition data, metadata, and permissions so that users in one space cannot see another space's data unless explicitly shared. Assigning Brand A and Brand B to separate spaces isolates their unified individuals and activation targets while shared reference data can be made available across spaces. This directly satisfies the requirement to keep brands separate but still allow common data.

Data Spaces partition the Data Cloud instance so that ingested data, data model objects, and related metadata are scoped to a specific space. Users assigned to a space see only the objects and data within it. This directly supports the requirement that wealth management and retail banking analysts work with separate data in a shared instance without exposing each other's records or segment-building inputs.

The Web SDK captures clickstream events directly in the browser and streams them to Data Cloud via the Interaction API, bypassing batch ingestion schedules. This event-level, near-instant delivery satisfies the lowest-latency requirement, unlike file-based or scheduled connectors.

The Unified Profile is the reconciled golden-record representation of an individual that Data Cloud produces by running identity resolution across all mapped source DMOs. It merges duplicate and related records into a single profile with a unified ID, which is exactly what the team needs to reference when building downstream segments from all onboarded sources.

Segment Builder supports engagement-based filtering, letting marketers qualify members by prior interactions such as email opens, clicks or web activity. This satisfies the requirement to build audiences from engagement history rather than only profile or transactional attributes.

Data Spaces logically partition data, metadata, and processes so that different business units or brands remain isolated within one Data Cloud org. By placing retail banking data in one space and wealth management in another and granting analysts access only to the retail space, the consultant satisfies the security requirement. This is precisely the access-isolation use case Data Spaces are designed for.

S3 is a standard file-based activation target.

Data Cloud Setup's Data Streams Monitor and Refresh History pages expose per-run execution logs, statuses and error details for batch data streams and data refreshes, directly satisfying the requirement for operational visibility into execution history and status without external tooling.