Configuring Direct Lake Behavior in Power BI
You have a custom Direct Lake semantic model named Model1 that has one billion rows of data. You use Tabular Editor to connect to Model1 by using the XMLA endpoint. You need to ensure that when users interact with reports based on Model1, their queries always use Direct Lake mode. What should you do?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
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.
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.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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
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?
It allows fallback to DirectQuery mode if data cannot be efficiently loaded into memory, which violates the requirement for pure Direct Lake.
Can I set Direct Lake Behavior per partition?
No, Direct Lake Behavior is a model-level property. Partition settings control storage and refresh, not the global query fallback logic.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →