The answer is that calculated tables are static and do not respond to slicer selections, which is the most likely cause of the incorrect values. This occurs because Power BI evaluates calculated tables at data refresh time and stores them as static data within the model, meaning they are not recalculated in the query context when a user interacts with a slicer. Unlike measures or calculated columns, which respect report-level filters, a calculated table like 'Sales Summary = SUMMARIZE(Sales, Sales[ProductID], "Total Sales", SUM(Sales[Amount]))' remains frozen with its original aggregated values regardless of any slicer applied. On the PL-300 exam, this concept tests your understanding of Power BI’s evaluation contexts—specifically the difference between static table creation and dynamic measure calculation. A common trap is assuming all DAX expressions respond to filters, but remember: tables are built at refresh, measures are built at query time. For a memory tip, think “tables are frozen, measures are fluid”—if you need dynamic filtering, use a measure instead of a calculated table.
PL-300 Model the data Practice Question
This PL-300 practice question tests your understanding of model the data. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A Power BI developer is troubleshooting a report that uses a calculated table. The calculated table is defined as: 'Sales Summary = SUMMARIZE(Sales, Sales[ProductID], "Total Sales", SUM(Sales[Amount]))'. Users report that the 'Total Sales' column shows incorrect values when slicers are applied to the report. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Calculated tables are static and do not respond to slicer selections.
Calculated tables in Power BI are evaluated at data refresh time and stored in the model as static data. They do not respond to slicer selections or any other report-level filters because they are not recalculated in the query context. Therefore, the 'Total Sales' column in the 'Sales Summary' table will always show the same aggregated values regardless of slicer interactions, which is why users see incorrect values when applying slicers.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 calculated table lacks a relationship to the Sales table.
Why it's wrong here
Calculated tables do not require relationships; they are static copies.
✓
Calculated tables are static and do not respond to slicer selections.
Why this is correct
Calculated tables are evaluated once at refresh and are not dynamic with slicers.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The SUMMARIZE function syntax is incorrect.
Why it's wrong here
The syntax is correct for creating a calculated table.
✗
The calculated table is not marked as a date table.
Why it's wrong here
Date table marking is irrelevant here.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse calculated tables with calculated columns or measures, assuming that all DAX expressions are dynamic and respond to slicers, but calculated tables are static and only evaluated at refresh time.
Detailed technical explanation
How to think about this question
Calculated tables are materialized during the refresh process using the VertiPaq engine, which stores the result as a physical table in the model. Unlike calculated columns or measures, calculated tables are not evaluated in the filter context of a report; they are computed once and remain unchanged until the next refresh. This means any dynamic filtering via slicers, which operates on the query context, has no effect on the pre-computed rows in a calculated table.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Model the data — This question tests Model the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Calculated tables are static and do not respond to slicer selections. — Calculated tables in Power BI are evaluated at data refresh time and stored in the model as static data. They do not respond to slicer selections or any other report-level filters because they are not recalculated in the query context. Therefore, the 'Total Sales' column in the 'Sales Summary' table will always show the same aggregated values regardless of slicer interactions, which is why users see incorrect values when applying slicers.
What should I do if I get this PL-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.