A "Direct Lake" "semantic model" reads tables from a "Lakehouse". A report author adds a transformation that the "Direct Lake" engine cannot serve from the Delta files, and the model is configured so queries still return correct results. What happens to the affected queries, and what is the cost of this behaviour?
- AThe queries fail and return an error until the author rewrites the report, because "Direct Lake" cannot fall back and every query must be served entirely from the Delta files in memory.
- BThe queries are silently dropped from the report and show blank visuals, because "Direct Lake" skips any query it cannot serve from memory rather than sending it elsewhere.
- CThe affected queries fall back to DirectQuery against the "SQL analytics endpoint" of the "Lakehouse", returning correct results but losing the in-memory performance of "Direct Lake" for those queries. Correct
- DThe affected queries fall back to import mode by loading the whole table into the model, returning correct results but consuming model memory until the next scheduled refresh clears the cache.
Why A is wrong: Direct Lake does not simply error on unsupported queries when fallback is allowed; it has a defined fallback path, so claiming an outright failure misstates the engine's behaviour.
Why B is wrong: Direct Lake does not blank out unsupported visuals; it routes them through a fallback rather than dropping them, so blank visuals is not the documented outcome.
Why C is correct: When a query cannot be served from the Delta files, Direct Lake falls back to DirectQuery over the Lakehouse SQL analytics endpoint, so results stay correct but those queries run slower than the in-memory path.
Why D is wrong: Direct Lake does not fall back by importing entire tables on a refresh schedule; its fallback is a live DirectQuery to the SQL endpoint, not a cached import load.