Which Fabric Data Store Supports Dataflows and Automatic V-Order?
You have source data in a folder on a local computer. You need to create a solution that will use Fabric to populate a data store. The solution must meet the following requirements: Support the use of dataflows to load and append data to the data store. Ensure that Delta tables are V-Order optimized and compacted automatically. Which type of data store should you use?
Community Votes
58% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests which Fabric data store guarantees V-Order and automatic compaction as a fixed service behavior, versus the lakehouse where V-Order depends on the write engine and compaction must be triggered with OPTIMIZE.
Choosing the right Fabric data store for dataflow ingestion plus automatic Delta optimization is the core of this DP-600 item, where a local folder must be loaded into a store whose Delta tables are V-Order optimized and compacted without any manual OPTIMIZE. This page explains why the Fabric warehouse, rather than a lakehouse, satisfies both stated requirements.
Picking the lakehouse because "Fabric plus Delta equals lakehouse" — but lakehouse V-Order is not guaranteed for every write path and small-file compaction requires running OPTIMIZE ... VORDER yourself, so the automatic guarantee is missing.
Community Discussion (15 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirement wording — "Ensure that Delta tables are V-Order optimized and compacted automatically" — mirrors Microsoft's guidance for ingesting data into a Fabric warehouse: whatever ingestion path you use (Dataflow Gen2, pipelines, COPY INTO, T-SQL inserts), the warehouse writes V-Ordered Delta Parquet and compacts the underlying Delta tables in the background, with V-Order always on and non-disableable. Dataflow Gen2 has a Warehouse destination that supports an Append update method, so the folder on the local computer can be loaded and appended through a dataflow exactly as the first requirement demands. Warehouse tables live in OneLake as Delta tables, so the "Delta tables" clause is met literally and not by analogy. Because the question says ensure and automatically, the built-in guarantee — no scheduled OPTIMIZE job, no engine-dependent behavior — is the deciding factor and points to the warehouse. Neither of the non-Delta options (Azure SQL database, KQL database) can satisfy the second requirement under any configuration.
Why the Other Options Are Wrong
A lakehouse is the strongest distractor: V-Order is on by default for Spark writes and Optimize Write reduces file counts, so many learners assume the lakehouse "does it automatically". But V-Order is not guaranteed for every write path into a lakehouse table, and consolidating small files requires you to run OPTIMIZE... VORDER on a schedule, so the word automatically is not honored. An Azure SQL database is relational storage with no Delta table format and no V-Order concept at all; Dataflow Gen2 can write to it, but the Delta optimization requirement fails outright. A KQL database (Eventhouse) is tuned for log and telemetry ingestion and KQL queries rather than Delta V-Order and compaction, so it fails the same requirement. Only the warehouse combines a Dataflow Gen2 append destination with unconditional, automatic V-Order and compaction.
Community Comment Notes
The vote is close (58 for lakehouse, 42 for warehouse), which signals that the item turns on a subtle service guarantee rather than the word "Delta". As bvmony2294 explains, "I have recently taken the exam and this question was asked" and in that sitting it was a two-answer item, so both the lakehouse and the warehouse are defensible when the stem says "Choose two"; on a single-answer stem the automatically guarantee selects the warehouse. bigdave987 makes precisely that argument and points at the warehouse ingestion best-practices note, warning that "V-Order optimization isn't guaranteed in Lakehouse". PiotrO agrees that "lakehouse doesn't automaticly store data in delta tables while warehouse does", while XiltroX and 4b35503 counter that every Fabric engine writes V-Ordered Delta tables and a_51 notes the platform is lakehouse-centric — useful context, but not a substitute for the documented automatic compaction behavior.
Official Reference
Exam Strategy
When a DP-600 stem uses words like "ensure" or "automatically" about V-Order or compaction, map it to the store where that behavior is a fixed service property and cannot be turned off — the Fabric warehouse — instead of the store where you must run maintenance yourself. Also watch the stem for "Choose two": this scenario frequently appears as a two-answer item covering both the lakehouse and the warehouse.
Frequently Asked Questions
Why isn't a lakehouse correct if it also stores Delta tables?
Lakehouse V-Order depends on the engine that writes the table, and compaction needs you to run OPTIMIZE ... VORDER yourself, so the automatic guarantee the question demands is not assured.
Can Dataflow Gen2 load and append into a Fabric warehouse?
Yes. Dataflow Gen2 supports a Warehouse destination with the Append update method, so the folder on the local computer can be loaded and appended without pipelines.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →