PL-300 Visualize and analyze the data Practice Question
You have a Power BI report that uses a calculated column to categorize sales as 'High', 'Medium', or 'Low'. You notice the column is not being refreshed when the underlying data changes. What is the most likely reason?
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
✓
Calculated columns are only refreshed when the dataset is refreshed.
Calculated columns are only refreshed when the dataset is refreshed. In Power BI, a calculated column is computed during dataset processing and its values are stored in the model, so it will not reflect underlying data changes until the dataset is refreshed (or the column is recalculated during that refresh). Option A does not fit because a measure is not stored row-by-row and would not appear as a column that simply fails to refresh. Option C does not fit because incorrect DAX syntax would typically produce an error or blank values, not a stale column. Option D does not fit because calculated columns do not dynamically update regardless of the functions used; the refresh behavior is inherent to how calculated columns are processed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The column is defined as a measure instead of a calculated column.
Why it's wrong here
A measure is evaluated at query time and cannot be placed on an axis to categorise rows, so it cannot produce the stored 'High'/'Medium'/'Low' values the scenario describes. Measures are correct when you need aggregations computed dynamically rather than row-level stored values.
- ✓
Calculated columns are only refreshed when the dataset is refreshed.
Why this is correct
Calculated columns are computed during dataset processing and stored in the model, so they only recalculate when the dataset refreshes. Because the stem describes values not updating as underlying data changes, this explains the behaviour: the column reflects the last refresh, not live source edits.
- ✗
The DAX syntax for the calculated column is incorrect.
Why it's wrong here
Incorrect DAX produces an error or blank result, not stale values that persist after the underlying data changes. Syntax errors are the cause when the column returns wrong or missing output immediately, rather than failing to update on refresh.
- ✗
The calculated column uses a function that does not support dynamic updates.
Why it's wrong here
No DAX function prevents a calculated column from recalculating during refresh; calculated columns are always recomputed from the imported table. This option is tempting when a function appears non-deterministic, but such functions still recalculate on each refresh.
Go deeper
Related to this question
About these practice questions
This PL-300 question is part of Courseiva's 524-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.