- A
SUMX cannot iterate over Inventory directly because it is a table reference; you need to use VALUES or a measure.
Why wrong: SUMX can iterate over a table reference like Inventory directly.
- B
The filter condition is applied to the entire Inventory table, but the row context from SUMX is not being considered, causing the filter to apply incorrectly.
The CALCULATE function modifies the filter context, but the filter is on the Inventory table without considering the current row from SUMX. The correct approach is to use FILTER inside CALCULATE to iterate over rows.
- C
The measure needs to be written using SUM instead of SUMX because StockOnHand and UnitPrice are both numeric columns.
Why wrong: SUMX is needed to multiply per row; SUM would not work.
- D
The RELATED function fails because the relationship between Inventory and Product is inactive.
Why wrong: The relationship is likely active by default, so RELATED should work.
Quick Answer
The answer is that the filter condition is applied to the entire Inventory table, but the row context from SUMX is not being considered, causing the filter to apply incorrectly. This is a classic DAX filter context vs row context trap: SUMX creates a row context to iterate over each row, but when placed inside CALCULATE, the filter argument `Inventory[StockOnHand] < Inventory[ReorderPoint]` is evaluated as a table-level filter on the whole Inventory table, not per row. As a result, the condition is applied before the iteration, so SUMX only sees rows where the entire table satisfies the condition, rather than checking each product individually. On the PL-300 exam, this scenario tests your understanding of how CALCULATE transforms row contexts into filter contexts, a common pitfall when mixing iterators with explicit filters. A reliable memory tip: "CALCULATE eats row context for breakfast" — any row context inside CALCULATE is replaced by filter context, so always use FILTER inside CALCULATE to preserve per-row logic.
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.
You are a data analyst for a retail company. You are building a Power BI model to analyze inventory levels across multiple warehouses. The source data is a SQL Server database with two tables: Inventory (WarehouseID, ProductID, StockOnHand, ReorderPoint) and Product (ProductID, ProductName, Category, UnitPrice). The Inventory table has 500,000 rows, and Product has 10,000 rows. You import both tables into Power BI. You need to create a measure that calculates the total value of inventory (StockOnHand * UnitPrice) for products that are below their reorder point. You create the following measure:
TotalValueBelowReorder = CALCULATE( SUMX(Inventory, Inventory[StockOnHand] * RELATED(Product[UnitPrice])), Inventory[StockOnHand] < Inventory[ReorderPoint] )
However, the measure returns an incorrect total. You suspect an issue with the filter context. What is the most likely cause of the incorrect result?
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 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
The filter condition is applied to the entire Inventory table, but the row context from SUMX is not being considered, causing the filter to apply incorrectly.
Option B is correct because the filter condition `Inventory[StockOnHand] < Inventory[ReorderPoint]` is applied as a table-level filter on the entire Inventory table, not within the row context of SUMX. SUMX iterates over each row of Inventory, but the CALCULATE filter overrides the row context, causing the filter to be evaluated against the whole table rather than per row. This leads to an incorrect total because the condition is not evaluated for each individual product as intended.
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.
- ✗
SUMX cannot iterate over Inventory directly because it is a table reference; you need to use VALUES or a measure.
Why it's wrong here
SUMX can iterate over a table reference like Inventory directly.
- ✓
The filter condition is applied to the entire Inventory table, but the row context from SUMX is not being considered, causing the filter to apply incorrectly.
Why this is correct
The CALCULATE function modifies the filter context, but the filter is on the Inventory table without considering the current row from SUMX. The correct approach is to use FILTER inside CALCULATE to iterate over rows.
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 measure needs to be written using SUM instead of SUMX because StockOnHand and UnitPrice are both numeric columns.
Why it's wrong here
SUMX is needed to multiply per row; SUM would not work.
- ✗
The RELATED function fails because the relationship between Inventory and Product is inactive.
Why it's wrong here
The relationship is likely active by default, so RELATED should work.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates mistakenly think the filter inside CALCULATE is evaluated row-by-row within SUMX, but in reality, CALCULATE's filter arguments are applied as table-level filters that override the row context, causing the condition to be evaluated incorrectly.
Detailed technical explanation
How to think about this question
Under the hood, CALCULATE transforms filter arguments into a new filter context that replaces the existing row context from SUMX. This means the condition `Inventory[StockOnHand] < Inventory[ReorderPoint]` is applied as a static filter on the entire Inventory table, not per iteration row. In real-world scenarios, this often results in the measure returning the total value of all products that are below their reorder point globally, rather than summing only those rows where the condition is true per row, leading to an inflated or incorrect total.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Model the data practice questions
Targeted practice on this topic area only
- →
All PL-300 questions
966 questions across all exam domains
- →
Microsoft Power BI Data Analyst PL-300 study guide
Full concept coverage aligned to exam objectives
- →
PL-300 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PL-300 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Prepare the data practice questions
Practise PL-300 questions linked to Prepare the data.
Deploy and maintain assets practice questions
Practise PL-300 questions linked to Deploy and maintain assets.
Model the data practice questions
Practise PL-300 questions linked to Model the data.
Visualize and analyze the data practice questions
Practise PL-300 questions linked to Visualize and analyze the data.
Manage and secure Power BI practice questions
Practise PL-300 questions linked to Manage and secure Power BI.
PL-300 fundamentals practice questions
Practise PL-300 questions linked to PL-300 fundamentals.
PL-300 scenario practice questions
Practise PL-300 questions linked to PL-300 scenario.
PL-300 troubleshooting practice questions
Practise PL-300 questions linked to PL-300 troubleshooting.
Practice this exam
Start a free PL-300 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PL-300 question test?
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: The filter condition is applied to the entire Inventory table, but the row context from SUMX is not being considered, causing the filter to apply incorrectly. — Option B is correct because the filter condition `Inventory[StockOnHand] < Inventory[ReorderPoint]` is applied as a table-level filter on the entire Inventory table, not within the row context of SUMX. SUMX iterates over each row of Inventory, but the CALCULATE filter overrides the row context, causing the filter to be evaluated against the whole table rather than per row. This leads to an incorrect total because the condition is not evaluated for each individual product as intended.
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 →
Last reviewed: Jun 11, 2026
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.