HOTSPOT -
You have a Microsoft Power BI report and a semantic model that uses Direct Lake mode.
From Power BI Desktop, you open Performance analyzer as shown in the following exhibit.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
The answer is Automatic and Direct Lake, actually the picture comes from https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-analyze-qp In this article you can see there are table1 and view1, performance analyser shows: • First card is linked to Table1 so direct lake is used • Second card is linked to View1 so it does direct query As the model can use direct lake and direct query you can conclude that the fallback behavior is automatic. For direct lake behavior you can read this: https://powerbi.microsoft.com/en-us/blog/leveraging-pure-direct-lake-mode-for-maximum-query-performance
In the article mentioned, it is written "If the semantic model falls back to DirectQuery mode to process the visual’s DAX query, you see a Direct query performance metric, as shown in the following image:". So in my opinion, it should be Automatic and DirectQuery
There is no table visual in this image.
The table visual is on the bottom of the link, it says "processed in Direct Lake Mode." on top of the table.
Asnwer: Automatic - DirectLake. the image is cut bad. if you follow this link: https://learn.microsoft.com/en-us/fabric/get-started/direct-lake-analyze-query-processing you can see that in Data section of Power BI they are using two different tables
In the link provided says: If the semantic model falls back to DirectQuery mode to process the visual’s DAX query, you see a "Direct query" performance metric, as shown in the following image (the image of question). Is that correct?
Automatic, DirectLake IMO, as the fallback method is not explicitly mentioned, by default any DirectLake query falls. back to DirectQuery, hence, it is automatic. After the changes have been made, the query method has fallen back to DirectQuery, hence, I would choose DirectQuery. Would be great to know further opinion into this.
I think automatic and direct lake : we have fallback direct query for card and no informations about table visual so its direct lake.
The final block of card shows Direct Query. I think the wording was wrong as there are no tables shown. So I suggest automatic and Direct query as noted by others.
The question itself is uniquely confusing and ambiguous and at times simply wrong, but I would go with Automatic and DirectQuery bc DAX falls back to DirectQuery always (it is a known shortcoming --> all explained here: https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-overview)
Additionally, this link (https://learn.microsoft.com/en-us/power-bi/enterprise/directlake-analyze-qp) explicitly says the following: If the dataset falls back to DirectQuery mode to process the visual’s DAX query, you see a Direct query performance metric, as shown in the following image --> and the image is the exact same as in the question.
IMHO, Automatic & DirectQuery
sorry, Automatic & Direct Lake
https://learn.microsoft.com/en-us/fabric/get-started/direct-lake-analyze-query-processing Direct Lake Mode, Direct Query
1. The Direct Lake fallback behavior is set to: DirectQueryOnly The Performance analyzer shows that the query type is "Direct query". This indicates that the fallback behavior is set to only use DirectQuery and not Direct Lake. If the behavior were set to "DirectLakeOnly", the query would fail if Direct Lake could not be used. "Automatic" would use Direct Lake when possible and fall back to DirectQuery, but since it's specifically showing "Direct query", it suggests "DirectQueryOnly". 2.The query for the table visual is executed by using: Direct Query The Performance analyzer directly mentions "Direct query" as the query type for the visual. This confirms that the data is being retrieved using DirectQuery mode, not Direct Lake or any composite model.
No, the 1st card shows that Direct Lake was used. DirectQueryOnly means that only Direct Query can be used. Automatic mode - it uses Direct Lake where it can and fallbacks to Direct Query https://learn.microsoft.com/en-us/fabric/get-started/direct-lake-manage#set-the-direct-lake-behavior-property
Since the right half of the screenshot is missing I suggest visiting here (as already mentioned below): https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-analyze-query-processing There you can see that the first performance measurement was done with a table and the second one with a view. Hence the 2nd question is referring to the first performance measurement. When DirectQuery is not mentioned the model uses DirectLake - since one measure is using DirectLake and one DirectQuery the mode is set to automatic.