Automatic page refresh cannot cut gateway traffic for Import-mode models
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an on-premises data gateway. You need to reduce the amount of data sent through the gateway by semantic models that run in import storage mode. Solution: You increase Automatic page refresh intervals. Does this meet the goal?
Community Votes
83% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Automatic page refresh is a report-canvas feature aimed at DirectQuery sources and it drives more queries, not fewer — it neither touches Import refresh traffic nor reduces anything crossing the gateway.
Continuing the gateway scenario, the proposed solution increases Automatic page refresh intervals to reduce the data sent through an on-premises gateway by Import-mode semantic models.
Assuming longer refresh intervals mean less data transfer — increasing the page refresh frequency would if anything raise query load, and the feature is not even applicable to Import-mode models on this path.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Automatic page refresh re-queries the data source at a set interval so open report pages show near-current data; it is designed for DirectQuery connectivity and does not participate in Import-mode scheduled refresh at all. Because Import models refresh through the gateway on their own schedule regardless of what the page does, changing page refresh intervals cannot reduce gateway traffic — and shorter intervals would actually increase query volume. The solution therefore does not meet the goal.Why the Other Options Are Wrong
Answering Yes would require some mechanism by which page refresh reduces transferred bytes, which does not exist: the feature operates at the visual/query level after data has already been imported or is being fetched live. The scenario specifies Import storage mode, where Microsoft documents that automatic page refresh applies to DirectQuery sources, so the proposal is doubly inapplicable — wrong mechanism and wrong storage mode.Community Comment Notes
Commenters converge on No for two independent reasons: one notes automatic refresh is not available for Import mode in this scenario, and another links the official automatic page refresh page stating it can be used with DirectQuery storage mode only. Both lines of reasoning support rejecting the solution.Official Reference
Exam Strategy
Check the storage mode first; if the question specifies 'Import', any solution involving 'page refresh' is incorrect because that feature is exclusive to DirectQuery. Focus on scheduled refresh settings or model optimizations for reducing gateway traffic in Import scenarios.
Frequently Asked Questions
Does automatic page refresh work with Import mode?
No, automatic page refresh applies only to DirectQuery storage mode and does not affect data imported via the gateway.
How to reduce on-premises gateway data volume?
Reduce query frequency by optimizing DAX measures or using incremental refresh instead of frequent full imports.
Related Analysis
Practice All PL-300 Questions
Access 116 questions with complete answers and detailed explanations.
View Full PL-300 Practice Test →