DP-750 · 3.1.1 · Prepare and process data
Design ingestion logic
Design logic for data ingestion and data source configuration, including extraction type and file type
Choose extraction and file handling from source behavior, freshness, change tracking, and downstream requirements.
Start with how the source changes
- No reliable change trackingFull snapshot
- Reliable increasing key or timestamp existsIncremental extraction
- Inserts, updates, and deletes must be reproducedCDC
Choose the simplest pattern that preserves the required source state and latency.
See what CDC captures
CDC carries row-level change semantics and ordering metadata instead of re-reading the complete source.
Let freshness drive cadence
Scheduled
- Latency
- Minutes to days
- Complexity
- Lower
- Best fit
- Periodic reporting
Continuous
- Latency
- Seconds to minutes
- Complexity
- Higher
- Best fit
- Event-driven workloads
Match extraction, cadence, and file format to source behavior rather than choosing the most sophisticated design by default.
Key points
- Snapshot: Reloads a complete source state
- Incremental: Reads only new or changed data
- CDC: Preserves inserts, updates, and deletes as changes
- File format: Match structure, scale, and interoperability needs
Exam trap
Do not choose full snapshots by habit when the source exposes reliable incremental changes.
Sources · 2 Microsoft Learn pages Show ▾
Checked on October 4, 2026. Report a problem
Go deeper on Microsoft Learn
Checked against Microsoft Learn on October 4, 2026. Report a problem with this card