← DP-700 study guide
Domain 3 – Monitor and Optimize an Analytics Solution (30–35%)
8 lessons, each ending with a practice scenario (Pro)
Log in to save your progress.
- ✓3.1 — Monitor Ingestion, Transformation and Semantic Model RefreshFabric offers several monitoring tools. Each answers a different question, and exam questions usually describe the question rather than name the tool.Scenario: Pro
- ✓3.2 — Configure AlertsMonitoring tells you what happened when you look. Alerts tell you without being asked. Fabric has several ways to alert, from a free failure email to rules that act on live data.Scenario: Pro
- ✓3.3 — Identify and Resolve Pipeline, Dataflow and Notebook ErrorsTroubleshooting questions describe a symptom and ask for the most likely cause or the best fix. Work through it in order: where did it fail (which activity, query or cell), what does the error say, is it transient, and is it about permission, connection, data or code?Scenario: Pro
- ✓3.4 — Identify and Resolve Eventhouse, Eventstream and T-SQL ErrorsReal-time and SQL items fail differently from batch jobs. A stream can keep running while it silently drops events, and a T-SQL statement can fail because of a concurrency rule that doesn't exist in Spark.Scenario: Pro
- ✓3.5 — Optimize a Lakehouse TableDelta tables slow down as they collect many small files, deleted rows that are still stored and old file versions. Table maintenance keeps reads fast and storage lean. Each command fixes a different problem.Scenario: Pro
- ✓3.6 — Optimize a Pipeline and a Data WarehousePipeline tuning is mostly about parallelism and how data moves. Warehouse tuning is mostly about data types, file layout and how data is loaded.Scenario: Pro
- ✓3.7 — Optimize Eventstreams and EventhousesReal-time performance has two halves. Getting events in quickly enough is about eventstream throughput and ingestion settings. Querying them quickly enough is about eventhouse policies and KQL habits.Scenario: Pro
- ✓3.8 — Optimize Spark and Query PerformanceSpark tuning on the exam has two parts. One is choosing the right compute and engine settings. The other is writing code that avoids the classic Spark bottlenecks: shuffles, skew, small files and bringing data to the driver.Scenario: Pro
Domain recapQuick overview of all lessons
- Monitor data ingestion, transformation and semantic model refresh with the Monitor hub, workspace monitoring, Query insights and the Capacity Metrics app
- Configure alerts with schedule failure emails, pipeline activities and Activator
- Identify and resolve errors in pipelines, dataflows, notebooks, eventhouses, eventstreams and T-SQL
- Optimize lakehouse tables, pipelines, warehouses, eventstreams, eventhouses, Spark and queries