CCNA Data Ingestion And Modeling Questions

Clickstream data only becomes useful for segmentation when events are tied to a person. Relating the event object to the Individual object lets audiences be built from behavioral criteria, such as customers who viewed a product. Without this relationship, events remain isolated and cannot contribute to customer-level audiences or analytics.

Each data stream has its own schedule configuration where the refresh interval is set, so specifying six hours there controls how often Salesforce CRM data is re-ingested. Connection-level or object-level settings do not govern refresh cadence.

OAuth 2.0 with client credentials grant is the correct authentication method when an API uses client ID and client secret to obtain an access token without user interaction. Data Cloud supports this method for external API connections. Selecting it ensures the data stream can authenticate, obtain a token, and retrieve JSON payloads as configured, matching the API's security requirements exactly.

Cardinality and relationship design in the Cloud Information Model determines how source profiles join for segmentation; without correct one-to-many or many-to-many definitions, downstream segment counts and activation audiences break. This is a core consultant responsibility in the modelling strategy.

Full Refresh treats each ingestion as a complete replacement of the data set. Because the nightly S3 files contain the full customer population, choosing Full Refresh ensures records absent from the latest snapshot are removed, satisfying the requirement that deletions propagate into the data model without manual intervention.

The mapping must honour the relationship cardinality defined between objects, such as one-to-many or one-to-one, so linked records resolve correctly. This satisfies the stem's condition by preventing invalid associations when the custom Data Source Object field feeds a standard Cloud Information Model attribute.

The Data Streams tab is where ingestion pipelines are defined: you connect sources, map and transform ingested data, and track stream health and refresh status. This satisfies the stem's requirement for creating, configuring and monitoring streams from connected sources.

DSOs ingest and persist unharmonised source data exactly as received from connected streams, before any mapping to the common data model occurs. This raw-storage role satisfies the stem's requirement, since harmonisation happens later in the Data Cloud pipeline, not within the DSO itself.

Data bundles automate both data stream creation and pre-mapping to CIM DMOs, triggering initial ingestion.

A formula transformation in the mapping step converts the incoming DD/MM/YYYY string into the YYYY-MM-DD format Data Cloud requires before ingestion. This satisfies the stem's format mismatch constraint without altering the source CSV or the target Individual DMO schema.

Data Explorer queries Data Space Objects and Data Model Objects directly, letting consultants inspect raw ingested records alongside harmonised, mapped records. This satisfies the stem's inspection requirement, since it exposes both storage layers rather than only reporting or transformation output.

Aligning DSOs to standard CIM DMOs means the data conforms to the schema those assets expect, so pre-built starter bundles, calculated insights, and segmentation templates work without custom rework. That schema conformance delivers the compatibility benefit stated.

Batch Data Streams read files landed in cloud object storage on a scheduled cadence, matching the nightly requirement. Direct connectors suit real-time or near-real-time ingestion, whereas the stem specifies a recurring overnight load from an external relational database.

Data type and length mismatches between primary and foreign keys will prevent relationship creation in the Data Model.

Auto-Mapping analyzes source field names and data types and proposes matches to standard DMO attributes, which is the recommended starting point for a standard CRM object like Account. The consultant then reviews and corrects any mismatches before activation, saving time while preserving accuracy.

API Enabled permits the integration user to authenticate and query records through the Salesforce REST and Bulk APIs, while object- and field-level read permissions ensure only the ingested data is retrievable. Together these satisfy the least-privilege requirement for a Data 360 ingestion user, avoiding unnecessary write or modify access.

Data Cloud DMOs require a single unique primary key, which the compound source fields cannot supply. A Data Streams formula field concatenating loyalty program ID and member ID produces that unique string, satisfying the DMO primary key constraint during mapping.

Transmitting timestamps as UTC or with an explicit ISO 8601 offset removes the browser's local-time ambiguity at the source, satisfying the requirement for correct chronological ordering in sequence analysis. Normalising during ingestion is unreliable because the offset is already lost, so the payload script must capture it before transmission.

Streaming ingestion with S3 event notifications lets Data 360 react as each object is written, so small files become available for downstream modeling and segmentation in minutes. It avoids repeated full-bucket scans and matches the requirement for continuous, low-latency arrival of many small JSON files. This is the intended pattern for high-frequency object storage delivery.

When no primary key uniquely identifies a line item, repeated ingestion runs cannot recognize existing rows, so new copies accumulate instead of updating in place. That produces inflated counts in segmentation. Defining a composite or surrogate key that combines order number and product SKU, or a dedicated line item identifier, gives the platform the identity it needs to upsert correctly.

The Starter Bundle for Marketing provisions pre-built Data Streams and Data Model Objects already mapped to the Customer 360 Data Model, giving a working schema out of the box rather than requiring manual mapping of raw sources to CIM entities.

Reviewing the Data Stream run history and error logs in the Data Cloud UI exposes the exact ingestion failure, such as authentication errors, schema mismatches or malformed records, satisfying the need to diagnose why the external cloud storage bucket stream is failing before attempting remediation.

A Data Source Object ingests and stores data in its original, unharmonised form as received from the source system, acting as the raw landing layer before mapping and harmonisation into the Data Cloud data model. This preserves source fidelity for downstream transformation.

The Data Model canvas provides a visual workspace for creating and relating Data Model Objects, letting consultants map entities and their relationships. This satisfies the need to manage the semantic data model underpinning Data Cloud.

Identity Resolution rulesets match and reconcile records across the Salesforce CRM CDC, Marketing Cloud Engagement, and Ingestion API streams, merging them into unified profiles. This directly satisfies the stem's constraint of preventing duplicate customer profiles from bloating downstream segments, which must occur after data modelling and before segmentation.

Contact points are modelled as separate DMOs linked to Individual, so the phone must land in Contact Point Phone and be associated by foreign key. Mapping it directly onto Individual would break the harmonised data model.

CSV, JSON and Parquet are the three formats Data Cloud ingests natively for batch streams, satisfying the stem's "natively supported" constraint without transformation or custom parsing. Parquet's columnar encoding suits large analytical loads, while CSV and JSON cover delimited and semi-structured sources respectively.

Custom DMOs can be linked to standard CIM DMOs via foreign key relationships.

Timestamps lacking timezone offset indicators or not expressed in UTC are interpreted against the platform's default offset, shifting stored values by several hours. Supplying explicit offsets or UTC-normalised timestamps in the JSON payload corrects the discrepancy in the DSO.

Data Model Canvas, also called Data Landscape, renders a visual map of data streams, data source objects, data model objects and the relationships linking them. This graphical view directly satisfies the requirement to see all components and their connections.

In Data Cloud, a Data Lake Object stores the raw ingested data, while a Data Model Object provides the semantic model used for segmentation, analytics, and activation. Mapping creates that semantic layer over the DLO, and the DLO remains the physical storage, so both objects persist and serve distinct roles in the ingestion-to-modeling pipeline.

Correctly mapping primary and foreign keys preserves the relationships between mapped DMOs, satisfying the stem's best-practise requirement. Without accurate key mapping, Data Cloud cannot resolve identities or join records across source objects, so relational integrity breaks and downstream segmentation and activation produce unreliable results.

Schema drift breaks batch ingestion: renamed columns or dropped fields cause mapping failures, so the stream aborts on every run. Confirming the source schema still matches the configured object model isolates whether the recurring failure stems from upstream structural change rather than credentials or volume.

Data Explorer queries and displays raw records stored within a Data Source Object, letting the consultant confirm ingestion succeeded before any mapping or transformation. It reads the DSO directly, which is exactly the pre-mapping verification step the scenario demands.

Batch ingestion loads data in scheduled, bounded intervals, introducing latency between arrival and availability. Streaming ingestion continuously consumes events as they occur, making data available in near real-time. This latency-versus-continuity axis is the defining difference between the two ingestion patterns in Data Cloud.

Parquet is columnar and compressed, so Data Cloud reads only needed columns during batch ingestion, cutting transfer volume and accelerating query performance. This satisfies the requirement to optimise ingestion of 500 million daily records from cloud storage.

The Data Streams tab provides the dedicated interface for creating and managing data streams, directly satisfying the stem's requirement. It centralises stream configuration, including connector selection and field mapping, within Data Cloud's Data Manager. No other area offers this specific functionality, making it the precise location for stream administration tasks.

The Interaction SDK captures engagement events from web and mobile apps and streams them into Data Source Objects in near real time. It provides the client-side instrumentation that feeds behavioural data directly into Data Cloud for immediate activation.

Data Explorer lets consultants browse and inspect individual records stored within Data Model Objects, showing field-level values. This satisfies the requirement to examine the records inside a DMO, unlike setup or mapping tabs that show configuration rather than data.

Data Cloud stores DateTime values in UTC. When the source timestamp lacks an offset, the consultant must declare the source time zone in the field mapping so ingestion can convert correctly. This produces consistent, comparable event times across all regions for segmentation.

Data Explorer lets the consultant query and inspect records actually landed in the Data Source Object, confirming ingestion succeeded. It reads the persisted data directly, which is precisely the verification the stem requires for the Ingestion API stream.

Harmonization is the mapping of unharmonized Data Source Object attributes onto the standardised Cloud Information Model attributes, resolving naming and structural differences between source systems. This directly satisfies the stem's requirement for the term describing that mapping process.

Data Cloud normalises CSV headers containing spaces and special characters into valid API field names automatically during ingestion. Consultants then map these sanitised fields to target objects in the mapping canvas, so no manual renaming of source headers is required.

Data Cloud lacks a native SFTP batch connector, so files must first be landed in supported cloud storage such as Amazon S3, then ingested through a batch data stream. This staging workaround satisfies the stem's constraint of no direct SFTP connectivity.

Hourly scheduled batch refresh matches the continuous file drops in S3 without the overhead of real-time ingestion, satisfying the efficiency constraint. Data 360 batch connectors poll the source at defined intervals, so hourly scheduling captures updates promptly while avoiding excessive API calls or resource consumption.

A mapped field is a dependency for downstream metadata. Data 360 blocks deletion while field mappings, Calculated Insights, or segment filters still reference it, so those references must be removed first to avoid breaking dependent definitions.

Data Model Objects map ingested raw data into the standardised Cloud Information Model schema, harmonising disparate sources into consistent entities and relationships. This satisfies the requirement to organise raw ingested data into a standardised structure, forming the semantic layer used for identity resolution and segmentation.

The Data Stream creation wizard includes an object selection step where you choose which CRM objects to ingest, so selecting Account, Contact and Case restricts ingestion at that point. This satisfies the stem's requirement to ingest only specific objects.

Data Cloud supports N:1 and 1:1 relationships between DMOs.

Data Cloud rejects timestamps that deviate from ISO 8601, requiring the extended format with a T separator, fractional seconds, and a Z or offset suffix. Supplying values such as 2024-01-15T10:30:00.000Z satisfies the schema validation that triggered the failure.

The Marketing Cloud Engagement Data Bundle packages the required Marketing Cloud objects, schemas and ingestion configuration, so the consultant avoids hand-building individual connections and mappings. It satisfies the requirement to bring Engagement data into Data Cloud through a supported, preconfigured ingestion path.

A Data Source is the logical grouping that bundles related data streams ingested from one connector instance, such as a specific Salesforce org. Data streams sit beneath it, while Data Lake Objects and Data Model Objects represent the ingested and modelled data.

The mismatch stems from inconsistent identifier formatting, so the fix is to normalize the value before it is used in the relationship. A Data Transform can pad or standardize the identifier so it aligns with the Individual DMO key, allowing segmentation joins to match records correctly and resolving the failed matches at the source of the problem.

Identity Resolution rulesets match and reconcile records across sources using fuzzy matching on fields like name and address, then link them to a single unified profile. This directly consolidates the regionally varied Account records into one Account DMO entry.

Filtering at stream configuration applies a WHERE clause before ingestion, so closed cases never enter Data Cloud. This satisfies the stem's constraint that records be excluded entirely, rather than ingested and later removed. Post-ingestion filtering would still consume storage and processing, making pre-ingestion exclusion the precise mechanism required here.

A CASE statement within a formula transformation evaluates each integer status code and returns the corresponding text description during field mapping. This translates codes into readable values as records are harmonised, meeting the client's requirement without altering source data.

A Data Bundle packages data streams, data model mappings and insights preconfigured for a specific Salesforce application, enabling faster deployment without manual assembly. It matches the definition of a pre-packaged collection tailored to one application.

Data Cloud Setup within Salesforce CRM Setup opens the Data Cloud configuration landing page directly, satisfying the stem's requirement for the menu item leading administrators there. Unlike standalone tiles or App Launcher entries, this node exposes provisioning, connectors and data space settings in one place, matching the expected navigation path.

During Data Cloud data stream creation, the wizard presents a Fields selection step where you choose which standard and custom Account fields to ingest. Selecting both there ensures the required schema is included before the stream is deployed and refreshed.

The Ingestion API rejects batches when any object lacks a populated, unique primary key, so explicit mapping in every JSON record satisfies the uniqueness constraint the stem's validation error flags. Duplicate or null key values across objects trigger exactly this failure, making per-object verification the required check.

The standard Cloud Information Model links Individuals to other DMOs through Party Identification, which holds identifiers such as email, phone, and loyalty numbers. By mapping the email to Party Identification and using the Party Identification relationship, the Order DMO connects to Individual in a way that supports identity resolution, multiple identifiers per person, and downstream segmentation and activation without custom modeling workarounds.

HTTP 400 signals a malformed request rather than authentication or throttling failure. The Ingestion API validates each payload against the stream's defined schema contract, so invalid JSON syntax or fields and types that breach that schema cause the rejection.

Formula functions support string concatenation, so separate first name and last name source fields can be joined into one full name attribute during mapping. This directly satisfies the stem's requirement for an action performed with formula functions.

Defining a batch stream requires specifying where the data lives and how to parse it, so the source bucket path plus file format details such as CSV and delimiter are mandatory. Without these, Data Cloud cannot locate or interpret the incoming files.

Nested arrays represent separate child records, so each item maps to a related child DMO. Storing the parent event's primary key as a foreign key on the child preserves the association between individual product interactions and their originating event.

Zero records with a permission-denied error indicates the service account lacks read access to the bucket, so IAM roles must be verified. Granting the Salesforce service account storage read permissions on the Google Cloud bucket satisfies the access requirement the error log identifies.

Filtering in the Salesforce CRM data stream configuration wizard excludes records older than two years before ingestion, so stale data never lands in Data 360. This satisfies the storage-conservation constraint at the earliest point, avoiding downstream filtering of already-ingested records.

Engagement is one of the three supported classification categories for Data Model Objects in Data Cloud, alongside Profile and Related. This satisfies the stem's requirement by naming a valid category that governs how the object's data is ingested and unified, distinguishing it from unsupported categories such as transactional or reference data.

Campaign tracking events travel through separate event data streams, not the subscriber stream. Enabling the tracking data bundle or its corresponding event data streams during setup is what makes opens, clicks and sends flow into Data 360, satisfying the requirement that tracking events appear.

The Marketing Cloud Account Engagement Data Bundle ships pre-built data streams and data model mappings specific to Pardot objects, letting consultants ingest Account Engagement data into Data 360 without manually authoring each stream and mapping.

Data Cloud requires the foreign key's data type and precision to match the parent DMO's primary key exactly, otherwise the N:1 relationship cannot be saved. Text with matching precision satisfies this referential integrity constraint for linking custom records to Individual.

Zero Copy Data Federation queries external relational sources such as Snowflake or Redshift in place, returning results to Data Cloud without replicating or transforming data. This satisfies the zero-ETL requirement by eliminating pipeline engineering, storage duplication and the associated latency.

Data streams capture the schema defined at setup, so fields added later in Salesforce CRM are not ingested automatically. Editing the data stream configuration lets the consultant select the new custom fields, refreshing the schema and mapping them into Data Cloud.

To make revenue values comparable, you must bring in the currency code and apply a conversion, either through a Data Cloud transformation or a formula, so all values are normalized to one currency before mapping. This ensures segmentation and analytics operate on consistent numeric values. Data Cloud does not perform automatic currency conversion, so handling it explicitly is the correct approach.

The Run History tab on the Data Stream Detail page exposes per-run ingestion telemetry, including status, records processed and failure details, satisfying the need to review ongoing runs. Data Cloud surfaces this monitoring directly against each configured stream, so consultants can diagnose ingestion without querying underlying Data Lake objects.