Forum Discussion
DP-700 Microsoft Learn Question
- 1 year ago
Hi tan_thiamhuat ,
I’d encourage you to submit your detailed feedback and ideas via Microsoft's official feedback channels, such as the Microsoft Fabric Ideas. Feedback submitted here is often reviewed by the product teams and can lead to meaningful improvement.
Thanks,
Prashanth Are
MS Fabric community support
Your company uses Microsoft Fabric to manage a data warehouse that supports various analytical workloads. Users report slow query performance, especially during the initial execution of queries.
You need to optimize query performance for the initial execution without relying on automatic statistics.
Each correct answer presents part of the solution. Which two actions should you take?
Your Answer
- Enable query caching.
This answer is incorrect.
- Enable query parallelism.
This answer is incorrect.
Correct Answer
- Manually create statistics for frequently queried tables.
This answer is correct.
- Use Direct Lake mode in Power BI.
This answer is correct.
Manually creating statistics for frequently queried tables enhances the query optimizer's ability to select efficient execution plans, which is crucial for improving initial query performance. Using Direct Lake mode in Power BI reduces latency by allowing direct data access from the lakehouse, thus improving query performance. Enabling query parallelism might seem beneficial, but it does not specifically address the issue of initial query execution performance without relying on automatic statistics.
--> Direct Lake is a Power BI feature that enhances performance for Power BI visuals, but it doesn’t directly affect the initial execution performance of queries in the data warehouse itself, isn't it?
-->
Enable query caching
Query caching helps speed up repeated queries by storing the result set of a query so subsequent executions return faster. It also benefits initial performance if the same query is run multiple times, even by different users.