Your Fabric Model1 refresh fails due to resource exhaustion. Which statement explains the likely cause?

Your Fabric Model1 refresh fails due to resource exhaustion. Which statement explains the likely cause?

• A. Query folding is occurring.
• B. Only refresh complete days is selected.
• C. XMLA Endpoint is set to Read Only.
• D. Query folding is NOT occurring.

Answer: (D)

When data transformations can be pushed back to the source, that work is folded, so the Fabric service does less processing and uses fewer internal resources during a refresh. If query folding is NOT occurring, the service must load more data and perform all the transformations locally, which increases memory and CPU usage. With large datasets or complex steps, that can exhaust resources and cause the refresh to fail. Other options don’t fit the symptom: limiting the refresh to complete days would reduce the amount of data processed, not cause exhaustion. Making the XMLA Endpoint read-only would block writes and typically produce a permission error rather than a resource drain. And stating that query folding is occurring would imply less work inside Fabric, not more, which wouldn’t explain resource exhaustion.

When data transformations can be pushed back to the source, that work is folded, so the Fabric service does less processing and uses fewer internal resources during a refresh. If query folding is NOT occurring, the service must load more data and perform all the transformations locally, which increases memory and CPU usage. With large datasets or complex steps, that can exhaust resources and cause the refresh to fail.

Other options don’t fit the symptom: limiting the refresh to complete days would reduce the amount of data processed, not cause exhaustion. Making the XMLA Endpoint read-only would block writes and typically produce a permission error rather than a resource drain. And stating that query folding is occurring would imply less work inside Fabric, not more, which wouldn’t explain resource exhaustion.