Configuring Direct Lake Behavior in Power BI
Short answer
D From Model, configure the Direct Lake Behavior option to enforce exclusive Direct Lake mode.
Question
Key Takeaways
The question tests knowledge of the specific property that controls query mode enforcement; the trap is confusing it with partition-level settings or default modes that allow fallback.
This page explains how to enforce Direct Lake mode exclusively for a semantic model in Power BI using the Direct Lake Behavior property. It clarifies that this setting prevents fallback to DirectQuery, ensuring consistent query performance.
Common mistake: Many users select 'Default Mode' (A) or 'Storage Location' (C), assuming they control the query execution path. However, these do not strictly prevent fallback to DirectQuery when memory constraints occur.
Expert Analysis
Why the Answer Is Correct
The correct action is to configure the Direct Lake Behavior option at the model level. This property specifically dictates how the engine handles query execution. Setting it to "Direct Lake only" ensures that queries will fail if they cannot be served directly from the lakehouse storage in compressed columnar format, thereby preventing any fallback to DirectQuery mode. This is the definitive way to guarantee exclusive Direct Lake usage as requested.
Why the Other Options Are Wrong
Option A (Default Mode) is incorrect because it typically refers to the connection mode used when creating new partitions or datasets, but it does not enforce strict behavior for existing queries against a Direct Lake model. Option B (Partitions) allows you to set the mode for individual data segments, but it does not control the global fallback logic for the entire model. Option C (Storage Location) determines where data resides (e.g., Import vs. DirectLake) but does not dictate the runtime query behavior or fallback policies.
Community Comment Notes
Community consensus strongly supports D. One user noted that while Tabular Editor v2 might lack certain UI elements, the underlying TOM property exists and is the correct technical solution. Another comment highlighted that "Automatic" is the default, which allows fallback, whereas "Direct Lake only" is required for strict enforcement. Users confirmed that partition settings manage data refresh and storage, not the global query execution strategy.
Official Reference
https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-overview#fallback-behavior
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked about enforcing a specific query mode without fallback, look for properties related to 'Behavior' or 'Fallback' rather than general 'Mode' settings. Remember that 'Direct Lake only' is a strict constraint, unlike 'Automatic' which prioritizes speed over consistency.
Frequently Asked Questions
What happens if Direct Lake Behavior is set to Automatic?
Can I set Direct Lake Behavior per partition?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
neoverma 👍 9https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-overview#fallback-behavior The DirectLakeBehavior property can be configured by using Tabular Object Model (TOM) or Tabular Model Scripting Language (TMSL). The following example specifies all queries use Direct Lake mode only: C# Copy // Disable fallback to DirectQuery mode. // database.Model.DirectLakeBehavior = DirectLakeBehavior.DirectLakeOnly = 1; database.Model.SaveChanges();
-
554b579 👍 6Click on Semantic model. In the Properties pane, choose the Direct Lake behavior for your custom Direct Lake semantic model: Automatic: This is the default behavior. It allows Direct Lake with fallback to DirectQuery mode if data can’t be efficiently loaded into memory. Direct Lake only: This option ensures no fallback to DirectQuery mode https://powerbi.microsoft.com/en-au/blog/leveraging-pure-direct-lake-mode-for-maximum-query-performance/
-
Ous01 👍 2In Tabular Editor version 3, it is possible to change the Default Mode to Direct Lake and it will be the right answer. Now I am confused with this question as TE version 2.5 does not allow the Default Mode of Direct Lake, so the only option is the Direct Lake Behavior.
-
stilferx 👍 2 Answered DIMHO, D, Because: Direct Lake models include the DirectLakeBehavior property, which has three options: ...
-
FSCH_111 👍 1 Answered DThe correct option to ensure queries use Direct Lake mode in Tabular Editor is: D. From Model, configure the Direct Lake Behavior option. Here's why the other options are incorrect: A. Default Mode: This option doesn't exist specifically for Direct Lake mode. It might be related to a different setting within the model. B. Partitions: Partitions are used to manage data refresh in large models, not to define the overall query mode. C. Storage Location: This option specifies where the model metadata is stored, not the data retrieval method.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →