Power BI Incremental Refresh Resource Failure Cause
Answer
Correct answer: D — Query folding is NOT occurring, causing all data to be loaded into memory for local transformation, leading to resource exhaustion.
You have a Fabric tenant that contains 30 CSV files in OneLake. The files are updated daily. You create a Microsoft Power BI semantic model named Model1 that uses the CSV files as a data source. You configure incremental refresh for Model1 and publish the model to a Premium capacity in the Fabric tenant. When you initiate a refresh of Model1, the refresh fails after running out of resources. What is a possible cause of the failure?
power bi incremental refresh failure
query folding one lake csv
dp-600 semantic model resources
power bi memory exhaustion
Community Votes
64% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests understanding that while CSVs traditionally don't support query folding, OneLake enables it; failure occurs when this optimization is lost or blocked, forcing full data loads into memory.
Identifies why a Power BI semantic model refresh fails due to resource exhaustion in a Fabric tenant, highlighting the critical role of query folding with OneLake.
Many learners assume CSV files inherently cannot support query folding (Option D is wrong in their view) or focus on partition schema changes (Option E), missing the performance impact of non-folded queries in OneLake.
Community Discussion (24 comments)
282b85d
👍 19
Selected: D
D. Query folding is NOT occurring. Query folding refers to the ability of Power Query to push data transformation logic back to the data source, which can perform the transformations more efficiently. When query folding does not occur, all the data is pulled into Power BI and transformations are applied locally, which can be resource-intensive and lead to running out of resources, especially with large datasets like your 30 CSV files. E. The delta type of the column used to partition the data has changed: While this could cause issues with incremental refresh accuracy, it would not typically result in "running out of resources" during the refresh.
Nefirs
👍 15
Selected: E
i don't really know. But A and D regarding query folding seem for me not to be relevant since query folding does not make sense anyway on CSV/Flatfile connections. In my understanding, query folding sends a query back to the source. And what kind of query would that be to a CSV source?
kilowd
👍 1
Selected: E
Answer is E : https://learn.microsoft.com/en-us/power-query/query-folding-examples#no-query-folding-example
sajjuh
👍 1
Selected: E
data type issue becoz PBI supports for lakehouse source
Devoteam2025
👍 2
Selected: E
The correct answer is "E." The answer is written incorrectl, they meant to say "data type" instead of "delta type," which is the reason for running out of resources.
VLADCS
👍 1
Selected: D
Answer D. If query folding is not supported, all transformations are performed in Power BI memory. This can cause excessive resource usage, especially for large data sources such as 30 CSV files. This is the most likely cause of the error. Answer E is not correct. If the partitioning column type has changed, it will cause an update error, but not a resource overload. The error will be more related to data incompatibility.
NRezgui
👍 2
Selected: E
The delta type of the column used to partition the data has changed.
rkandathil
👍 1
Selected: D
D. Query folding is NOT occurring Query folding happens when Power BI sends this list (your transformations) to the database, so it does the heavy lifting for you. If folding doesn’t happen, Power BI has to handle all the processing on its own, which is slower and less efficient.
Rakesh16
👍 1
Selected: D
Query folding is NOT occurring.
jcu614
👍 1
D. While query folding typically does not apply to CSV files, OneLake does provide some structure that can prevent loading all data into PowerBI Memory.
jass007_k
👍 2
Correct Option is D) If query folding is not occurring, it means that all 30 CSV files are likely being loaded into memory for processing, which can lead to resource exhaustion, especially if the files are large or numerous. A. Query folding is occurring: If query folding were happening, it would typically improve performance and reduce resource usage, not cause a failure. B. Only refresh complete days is selected: This option usually helps in managing the data being refreshed by only focusing on completed data, potentially alleviating resource issues rather than causing them. C. XMLA Endpoint is set to Read Only: If the XMLA Endpoint were set to read-only, it wouldn't directly cause a refresh failure due to resource issues. It would restrict write operations but not necessarily impact resource allocation during a refresh. E. The delta type of the column used to partition the data has changed: Changes in partitioning columns could cause refresh issues, but they wouldn’t inherently lead to resource exhaustion unless they also disrupt query folding.
Jons123son
👍 8
Was in exam. Scored 95% Chose D. Honestly, I was guessing. No clue. However, query folding does occur for CSV files stored IN OneLake. OneLake does the work. This different from semantic models created with files stored on a normal machine and what had been common knowledge for a Power BI user.
haran939
👍 2
Selected: D
Answer D
PiyushT
👍 5
Selected: D
For efficient data processing, Power BI aims to push as much of the filtering and calculations as possible to the source system (OneLake in this case). This is called query folding. When query folding fails, Power BI needs to pull all the raw data into the semantic model and perform operations there, increasing memory and processing strain. E This could lead to refresh errors but is less likely to cause the specific behavior of running out of resources.
stilferx
👍 3
Selected: D
IMHO, The answer is D. Link: https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot#cause-the-data-source-doesnt-support-query-folding Cause: Data source queries aren't being folded While problems with query folding can usually be determined in Power BI Desktop before publishing to the service, it's possible that model refresh queries aren't being folded, leading to excessive refresh times and query mashup engine resource utilization. This situation happens because a query is created for every partition in the model. If the queries aren't being folded, and data isn't being filtered at the data source, the engine then attempts to filter the data.
Fer079
👍 1
Selected: D
D. Query folding is NOT occurring. As described in Incremental refresh and real-time data for models - Requirements, incremental refresh is designed for data sources that support query folding. Make sure data source queries are being folded in Power BI Desktop before publishing to the service, where query folding issues can be significantly compounded. So having said this, csv files is not a data source that support query folding. https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot#cause-the-data-source-doesnt-support-query-folding
zerone72
👍 1
If you connect power bi to the datasource through the SQL endpoint , you basically use as if it was a SQL server. Therefore, you might be able to use query folding. Am I correct ?
d47320d
👍 5
Correct Answer: "E. The delta type of the column used to partition the data has changed." Explanation: Query folding is not applicable with csv files, which rules out A,D answers. The provided Microsoft link related to "problem-loading-data-takes-too-long", states two causes, one related to query folding (we've already ruled it out) and another one related to the data type, which in turn leads us to answer E.
sraakesh95
👍 2
Selected: D
Combining the references by XiltroX and Momoanwar: https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot#problem-loading-data-takes-too-long https://learn.microsoft.com/en-us/power-query/power-query-folding
XiltroX
👍 1
Selected: D
D is the right choice. Here's why: https://learn.microsoft.com/en-us/power-query/power-query-folding
estrelle2008
👍 2
Selected: B
Without considering external tooling (C), without further context I can already identify B, D and E as possible causes. Question should be: What could NOT be a cause? I add answer B to this: Resource exhaustion due to partial-day refresh, when Only refresh complete days is selected while configuring incremental refresh.
Momoanwar
👍 4
Selected: D
https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot#problem-loading-data-takes-too-long
Nicofr
👍 2
Selected: E
https://learn.microsoft.com/en-us/power-bi/connect-data/incremental-refresh-troubleshoot#problem-loading-data-takes-too-long
Fermd
👍 2
Selected: C
C. XMLA Endpoint is set to Read Only: If the XMLA endpoint for the Premium capacity is set to Read Only, any attempt to update or refresh the model through this endpoint, including incremental refresh, would fail. This configuration directly explains the resource exhaustion during a refresh operation as the read-only mode wouldn't allow the necessary updates to occur.
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is D. Query folding is NOT occurring. In a Fabric tenant using OneLake, Power BI can perform query folding against CSV files because OneLake acts as a scalable query engine. If query folding does not occur, Power BI must pull all raw data into the service memory to apply transformations locally. With 30 daily-updated CSV files, this local processing consumes excessive resources, leading to refresh failures due to out-of-memory errors.Why the Other Options Are Wrong
Option A is incorrect because if query folding were occurring, performance would improve, reducing resource usage rather than causing exhaustion. Option B describes a configuration setting for incremental refresh but does not directly cause resource exhaustion; it limits the data processed. Option C prevents updates but would likely result in an access error rather than a resource limit error. Option E refers to a 'delta type' which is not a standard term; even if interpreted as a data type mismatch, it typically causes transformation errors rather than general resource exhaustion from volume.Community Comment Notes
Community consensus strongly favors Option D. As user Nefirs noted, "query folding does not make sense anyway on CSV/Flatfile connections" based on traditional Power BI knowledge, but this overlooks OneLake's capabilities. User Jons123son clarified, "OneLake does the work," confirming that folding is possible and its absence is the bottleneck. Users like PiyushT and jass007_k correctly identified that pulling all data into memory for processing is the direct cause of the resource failure.Official Reference
Exam Strategy
When troubleshooting Power BI resource issues in Fabric, always consider whether query folding is active. Remember that OneLake extends query folding capabilities to formats like CSV that are not foldable in traditional On-Premises sources.
Frequently Asked Questions
Does query folding work with CSV files in Power BI?
Traditionally no, but in Microsoft Fabric with OneLake, yes. OneLake supports query folding for CSVs, enabling efficient filtering at the source.
What happens if query folding fails for a large dataset?
Power BI pulls all raw data into the service memory to apply transformations locally, which can quickly exhaust available resources and cause refresh failures.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →