ExamworthyExamworthy
Open the appStart free

DP-700 - Ingest and Transform Data - Section 2.3

Design and implement a loading pattern for streaming data into Microsoft Fabric.

Design a streaming ingestion pattern selecting Eventstream destinations and Eventhouse or Lakehouse targets based on latency requirements. Compare micro-batch and continuous ingestion modes, and recognise when landing streaming data to a Lakehouse table enables downstream batch processing.

streaming ingestion to an EventhouseEventstream destinationsnear-real-time loads to a Lakehousemicro-batch versus continuous ingestionlanding streaming data for downstream batch

Practice question for this objective

Free sampleIngest and Transform Datamedium

A logistics team ingests vehicle telemetry through a Microsoft Fabric Eventstream. Downstream, a nightly Spark job in a Lakehouse aggregates the day's telemetry into a Delta gold table. The streaming events do not need sub-second queries, but they must be durably landed in open Delta format so the batch job can read a full day at a time. Which Eventstream destination best lands the stream for this downstream batch?

  • ASend the Eventstream to an Eventhouse destination so the events are indexed in a KQL database, then have the nightly Spark job query the KQL database for each day.
  • BSend the Eventstream to a Lakehouse destination so events are written as Delta files in OneLake, ready for the nightly Spark job to read a full day in batch. Correct
  • CSend the Eventstream to a Microsoft Fabric Activator destination so each event triggers an action, then collect the triggered actions into the Delta gold table nightly.
  • DSend the Eventstream to a custom endpoint destination so an external service receives the events, then re-ingest them later from that service into the Delta gold table.
When streaming data only needs to land for downstream batch processing, route the Eventstream to a Lakehouse destination so events write as open Delta files. The requirement is durable open-format landing for a nightly full-day Spark read, not low-latency querying; a Lakehouse destination writes the Eventstream into OneLake as Delta, which Spark reads natively per day, whereas an Eventhouse adds query indexing the scenario does not need and Activator and custom endpoints do not durably store the stream.

Why A is wrong: An Eventhouse is the right choice when sub-second queries are needed, but the scenario explicitly does not require them; indexing the stream for low-latency querying adds cost and is a poor source shape for a full-day Spark batch read.

Why B is correct: A Lakehouse destination lands the stream as Delta files in OneLake in open format, which is exactly what a nightly Spark batch job needs to read a whole day; durability and open format are met without paying for low-latency query indexing.

Why C is wrong: Activator reacts to event conditions by firing alerts or actions; it is not a durable landing store for the raw stream, so it cannot supply a full day of telemetry in Delta format to the batch job.

Why D is wrong: A custom endpoint forwards events out of Fabric to another consumer, adding a round trip and an external dependency; it does not durably land the data in OneLake, so it is the wrong fit for a Fabric-native batch read.

See more DP-700 practice questions, answers explained.

More in this domain

Back to all Ingest and Transform Data objectives, or the DP-700 cert hub.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.