Optimize performance
9 practice questions under this official exam objective (DP-700), each with the answer key, an option-by-option explanation and instant feedback.
Questions under this objective
9 total · page 1 of 1Why Do Direct Lake Reports Fail on F32 Capacity?
This DP-700 question tests the Direct Lake per-table row limits tied to Microsoft Fabric capacity SKUs and why a 500 million-row fact table on F32 cau
Which Fabric Shortcuts Use the OneLake Cache?
OneLake shortcut caching in Microsoft Fabric applies only to GCS, S3 and S3-compatible shortcuts, and individual files larger than 1 GB are never cach
A 500-million-row fact table exceeds the F32 Direct Lake guardrail, so increase the capaci
DW1's fact table grew to 500 million rows, above the F32 Direct Lake guardrail of 300 million rows per table, so Direct Lake falls back to DirectQuery
Resolving Direct Lake Row Limits in Fabric F32 Capacity
Learn how to resolve Direct Lake performance errors and row limit violations in Microsoft Fabric F32 capacity by using views to optimize data access p
Optimizing Fabric Warehouse Query Performance with V-Order
Learn how to optimize query performance in Microsoft Fabric Warehouses by enabling V-Order, which improves data compression and retrieval speed for ad
Choosing Starter Pool vs Custom Spark Pool per Notebook
This DP-700 hotspot tests Microsoft Fabric Spark environment selection: a scheduled, cost-sensitive ingestion notebook belongs on the serverless Start
OPTIMIZE consolidates the small Parquet files of a Delta table
Running OPTIMIZE on Table1 compacts its many small Parquet files into larger ones, solving the small-file problem; VACUUM only removes files no longer
VACUUM removes lakehouse files older than seven days that are no longer in use
The VACUUM command on the lakehouse table removes files no longer referenced by the Delta log and older than the retention threshold, which defaults t
OPTIMIZE plus VACUUM minimizes query time on a table of 2,000 one-MB files
Table1's 2,000 Parquet files of 1 MB each create a small-file problem: OPTIMIZE consolidates them into fewer large files for faster scans, and VACUUM