Dashboard tile cache frequency has no bearing on gateway data transfer
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 decrease the dashboard cache update frequency. Does this meet the goal?
Community Votes
80% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Dashboard tile caching happens inside the Power BI service between datasets and dashboard visuals — it neither pulls from on-premises sources nor participates in Import refresh traffic, so its frequency cannot change gateway volume.
In the same gateway scenario, the proposed solution decreases the dashboard cache update frequency to reduce the data sent through the gateway by Import-mode semantic models.
Assuming anything named 'refresh' touches the gateway — the tile cache is a service-side rendering layer fed from the already-loaded dataset, entirely downstream of the on-premises connection.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Dashboard tiles are served from a cache that Power BI service updates periodically by querying the underlying (already imported) dataset — a process wholly inside the cloud service. The on-premises data gateway is only exercised during dataset refresh or live DirectQuery connections. Changing how often tile caches update therefore alters service-internal query load against the dataset, but the amount of data crossing the gateway during Import refreshes remains exactly the same. The solution does not meet the goal.Why the Other Options Are Wrong
Answering Yes would require the tile cache pipeline to reach back through the gateway to the on-premises source, which it does not: tiles read from the imported dataset, not the source. Even reducing cache updates only changes how often the service reads from its own dataset — no bytes on the on-premises-to-cloud path are saved either way.Community Comment Notes
A commenter notes that adjusting dashboard cache frequency does not directly reduce data sent through the gateway by Import-mode semantic models, matching the documented separation between tile caching and gateway refresh. The Yes camp's reasoning asserts a gateway connection during cache updates that does not exist.Official Reference
Related Analysis
Practice All PL-300 Questions
Access 116 questions with complete answers and detailed explanations.
View Full PL-300 Practice Test →