Incremental Refresh Parameters: RangeStart and RangeEnd
Which TWO actions are required when configuring a Power BI dataset to use incremental refresh?
⚠ Common exam trap
A common mix-up: candidates confuse the required steps (defining parameters and setting the policy) with optional or unrelated features like query caching or storage mode changes, leading them to select options A or B.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set the incremental refresh policy in the dataset settings.
Option E is correct because incremental refresh in Power BI requires two Power Query parameters named exactly rangeStart and rangeEnd (both of type DateTime), which define the filter window applied to the table's date column so Power BI can partition and refresh only the relevant ranges. Option D is correct because, after publishing the dataset, you must configure the incremental refresh policy (via the dataset's settings in the Power BI service, or by right-clicking the table in Power BI Desktop and selecting Incremental refresh) to specify the historical and incremental periods that determine how partitions are created and refreshed. Option A is incorrect because incremental refresh works with Import mode datasets and does not require DirectQuery storage mode. Option B is incorrect because query caching is a separate performance feature and is not a prerequisite for incremental refresh. Option C is incorrect because Power BI automatically manages the refresh history and partition metadata internally; no user-created calculated table is needed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the dataset storage mode to DirectQuery.
Why it's wrong here
DirectQuery storage mode bypasses the Power Query data transformation and import pipeline entirely, so it cannot use incremental refresh. Incremental refresh partitions data into historical and new sections, which only works with an Import mode model that can store data and selectively refresh partitions. Therefore, setting DirectQuery is not a required action and would actually prevent you from configuring incremental refresh.
- ✗
Enable query caching on the dataset.
Why it's wrong here
Query caching is a dataset property that stores query results to accelerate report rendering in the Power BI service, not to manage data loading. It has no effect on the refresh schedule, partition creation, or the amount of data pulled from the source, so it is unrelated to the incremental refresh setup. Thus, enabling query caching is an optional performance optimization, not a required configuration action.
- ✗
Create a calculated table to store the refresh history.
Why it's wrong here
A calculated table that stores refresh history would only add unnecessary data to your model and increase refresh time and storage, but it does nothing to enable manual data partitioning. Incremental refresh is implemented through Power Query date parameters and a refresh policy, not through calculated tables. Therefore, creating such a table is not a configuration requirement.
- ✓
Set the incremental refresh policy in the dataset settings.
Why this is correct
Setting the incremental refresh policy in the dataset settings is the central action because it defines the refresh window (e.g., how many days of data to refresh), the date column used for filtering, and options like retaining historical data. This policy tells Power BI to create time-bounded partitions for the tables and determines which partitions are refreshed in a given run. Without this policy, Power Query parameters alone cannot trigger incremental refresh.
- ✓
Define rangeStart and rangeEnd parameters in Power Query.
Why this is correct
Power Query rangeStart and rangeEnd parameters are mandatory because the incremental refresh policy uses them to filter the source data into time-bounded sections. The parameters, which must be of DateTime type, are passed into the query so that only rows falling within the current refresh window are loaded. Defining these parameters is the second required action, alongside setting the refresh policy, to actually perform incremental extraction.
Go deeper
Related to this question
About these practice questions
One of 524 original PL-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.