An enterprise "semantic model" must report over billions of Delta rows held in a "Lakehouse" in "OneLake". The team needs near real-time freshness without scheduled refreshes, in-memory query speed for reports, and no duplication of the data into the model. Which storage mode should they choose for these tables?
- AImport mode, because it loads the Delta tables into the model for fast in-memory queries and refreshes them on a schedule so reports stay close to the source data.
- BDirectQuery mode, because it queries the Delta tables in place for near real-time freshness and answers report queries from memory without copying any data into the model.
- CDual storage mode, because it both imports the Delta tables for in-memory speed and queries them live for freshness while avoiding any copy of the data into the model.
- D"Direct Lake" mode, because it reads the Delta tables directly from "OneLake" with in-memory speed and reflects source changes without copying data or running scheduled refreshes. Correct
Why A is wrong: Import mode copies the Delta tables into the model and depends on scheduled refresh, which both duplicates the data and breaks the near real-time requirement, so it does not fit.
Why B is wrong: DirectQuery avoids duplication and stays fresh, but it sends each query to the source rather than serving results from memory, so it cannot deliver the in-memory query speed required.
Why C is wrong: Dual mode lets a table behave as import or DirectQuery per query, but its import side still caches a copy of the data, so it does not avoid duplication the way the requirement demands.
Why D is correct: "Direct Lake" loads Delta data from OneLake into memory on demand and tracks source changes, delivering import-like speed with near real-time freshness and no data duplication, which meets every stated need.