Which of the following best describes query folding in Power Query?
Think about how Power Query optimizes data retrieval from the source.
Query folding means Power Query sends transformations as native queries to the data source, improving performance by reducing data transfer.
You apply a filter step in Power Query on a SQL Server table. Which option correctly shows how to check if query folding is still active?
Power Query provides a direct way to see the native query generated.
Right-clicking the last step and choosing 'View Native Query' shows the SQL query Power Query sends to the source, confirming folding.
Which of these Power Query functions will break query folding when applied?
Consider which function uses custom code that the data source cannot translate.
Using Table.TransformColumns with a custom M function often breaks folding because the data source cannot execute custom M code.
You have a Power Query that merges two large tables and then adds a custom column with a complex M expression. Which approach will best preserve query folding?
Think about when custom M code breaks folding and how to isolate it.
Performing the merge first preserves folding for that step. Adding the custom column after loading avoids breaking folding during the merge.
You notice your Power Query refresh is slow. You suspect query folding is broken. Which of the following observations best indicates that query folding is not happening?
Consider what disables the 'View Native Query' option and how it relates to performance.
If 'View Native Query' is disabled, it means folding is broken. This usually causes slower refresh because all data is pulled before transformations.