CCNA Data Ingestion And Modeling Questions

A data stream only ingests records; without field-level mapping from the Data Source Object to the Data Model Object, ingested data cannot populate DMO fields, leaving the object empty. Mapping is the required transformation step that satisfies the stem's missing-link constraint.

The nested line items require the stream to preserve parent-child relationships rather than flattening them. Declaring object and array data types in a hierarchical schema lets the configuration parse each transaction with its embedded line-item array intact, enabling correct downstream processing.

Mapping both source fields to the same identifier attribute in the Individual DMO consolidates the disparate legacy keys into one harmonised identity, ensuring records from all systems resolve to a unified individual rather than fragmenting.

Streaming ingestion via the Ingestion API or Interaction SDK accepts continuous, high-volume event streams with low latency, satisfying the stem's constant-update and near-real-time requirements. Batch or bulk mechanisms buffer data, so they cannot meet the clickstream latency constraint.

Correcting the mapping does not retroactively process failed records; a manual refresh forces re-ingestion immediately, while the scheduled run resumes flow automatically. This satisfies the stem's requirement to resume data flow after the mapping fix.

When a stable, unique source identifier is mapped to the primary key, each nightly snapshot updates existing records rather than adding new ones. Unchanged customers are simply rewritten with the same values, and changed customers are refreshed. This is the standard way to handle full-snapshot feeds and prevents duplicate individuals from accumulating over time.

Customer feedback ratings from 1 to 5 are discrete numeric values, so mapping to a Number attribute (Integer or Decimal) preserves their quantitative meaning for aggregation and analysis. Text or Boolean types would prevent correct numeric calculation in Data 360.

The Interaction SDK streams engagement events from web and mobile apps straight into Data Cloud as they occur, satisfying the near real-time constraint. Unlike batch or file-based ingestion, it pushes each interaction immediately, so data lands within seconds of the user action.

Marketing Cloud Engagement data streams synchronise on a default batch schedule of every 24 hours once established. Consultants needing fresher data must adjust this frequency, since the default is daily rather than hourly or near real-time.

Data Cloud's file format configuration accepts a custom delimiter field. Because the source emits pipe-separated values rather than commas, setting the delimiter to the pipe character ensures the CSV parser splits columns correctly during ingestion.

CIM supplies a canonical, industry-standard schema so disparate sources map to shared entities and relationships. This satisfies the stem's harmonisation goal by giving Data Cloud a common vocabulary, enabling identity resolution and unified reporting across systems without bespoke per-source modelling.

Mapping both the amount and its ISO code satisfies Data Cloud's requirement that currency values retain their denomination context. Data 360 stores currency as a compound pair: the numeric amount plus the ISO 4217 code, so splitting them or mapping only the amount would lose the currency identity needed for correct multi-currency aggregation and conversion.

Mapping order attributes to the Order DMO and relating it to Individual through Party Identification follows the Cloud Information Model. The Order DMO holds transaction details, and the relationship via Party Identification connects it to the correct person. This structure supports identity resolution and allows segmentation on order history, such as total spend or recency, while keeping the model standard and scalable.

The natural workflow is to configure ingestion first, then inspect the modeled results. Data Explorer lets a consultant browse data model objects and their fields, so it is the right place to confirm that mappings populated the intended attributes. It validates the outcome of the mapping work without requiring a separate reporting tool or query language.

Mapping both Salesforce orgs' records to standard CIM Data Model Objects gives them a common schema, then Identity Resolution matches overlapping emails into one unified profile. This satisfies the stem's requirement that separate records from two orgs harmonise under a single customer profile.

The Data Cloud Admin or Data Cloud Consultant permission set grants the object and setup permissions needed to create and configure data streams and data models. Without these, users can view Data Cloud but cannot perform the configuration tasks the scenario requires.

Exponential backoff with retry logic handles the Ingestion API's rate limits gracefully, spacing retried requests instead of hammering the endpoint. This avoids 429 throttling errors and dropped batches during peak streaming volume, preserving delivery of every record.

Web events are best modeled as Engagement DMO records, which capture interactions. The Engagement DMO relates to Individual through the resolved Individual ID, which is the unified identifier produced by identity resolution. This standard relationship allows web events to be associated with the correct person even when the event initially carries an anonymous ID, enabling accurate segmentation and activation based on web behavior.

Formula transformations execute per record during mapping, so each additional or complex formula adds processing overhead that directly slows batch ingestion. This satisfies the stem's performance-factor criterion by naming mapping-time computation as a throughput constraint.

Data Cloud's batch ingestion connectors natively support Google Cloud Storage as a file source, allowing objects to be ingested without custom middleware. This satisfies the stem's requirement for natively supported providers, enabling scheduled batch streams directly from GCS buckets.

Data streams map source columns to the Data Source Object schema by header name, so varying headers break field mapping and cause ingestion failures. Keeping a consistent header row across daily CSV files ensures each column resolves to its defined field without manual remapping.

A master data stream ingests and harmonises core reference objects such as Products, Stores or Locations, creating the unified profile-adjacent foundation used across Data Cloud. This satisfies the stem's requirement for managing core reference data rather than transactional or engagement event data.

The Interaction Ingestion API accepts real-time event data, including clickstream interactions from mobile apps, streaming them directly into Data Cloud. Batch or bulk mechanisms cannot satisfy the real-time requirement, so this API is the appropriate ingestion mechanism for continuous event capture.

Data Stream Formula Fields apply declarative expressions during ingestion, concatenating first and last names or reformatting dates without Apex or custom code. This satisfies the requirement to transform field values at ingestion time using point-and-click configuration rather than programmatic scripting.

Defining a unique primary key in the Ingestion API schema lets Data Cloud match incoming records to existing ones and upsert rather than insert, preventing duplicate transaction IDs from creating separate DSO records. Without it, each submission is treated as new.

Amounts in USD, EUR and GBP cannot be summed directly. Mapping both the monetary value and its ISO currency code to standard Data Model Object attributes lets Calculated Insights normalise each order to a common currency before aggregation, satisfying the accurate total purchase value requirement.