Which statement correctly describes the data refresh behavior when using DirectQuery mode compared to Import mode in Power BI?
Think about how data is accessed in real-time versus stored locally.
DirectQuery mode sends queries directly to the data source every time you interact with the report, so data is always current. Import mode loads data into Power BI's memory and needs refreshes to update.
You have a very large dataset that cannot fit into Power BI's memory. You want to build reports that always show the latest data without waiting for scheduled refreshes. Which mode should you choose?
Consider how each mode handles data size and freshness.
DirectQuery mode is designed to work with large datasets by querying the source live, avoiding memory limits. Import mode loads data into memory, which can be problematic for very large datasets.
Consider a Power BI report using DirectQuery mode connected to a SQL database. You create this DAX measure:
Sales Amount = SUM(Sales[Amount])
What happens when you interact with a slicer filtering by Product Category?
Think about how DirectQuery mode handles filtering and queries.
In DirectQuery mode, Power BI translates DAX filters into SQL queries with WHERE clauses, so only filtered data is retrieved from the source.
A report using DirectQuery mode is very slow when filtering on a date column. Which of the following is the most likely cause?
Think about what affects query speed in the source database.
In DirectQuery mode, queries run on the source database. If columns used for filtering are not indexed, queries can be slow.
You want to create a dashboard that clearly shows users the difference in data freshness between Import mode and DirectQuery mode. Which visualization approach best communicates this difference?
Think about how to show data freshness clearly and simply.
A gauge showing last refresh time for Import mode and a live clock for DirectQuery mode visually communicates how current the data is in each mode.