Question 422 of 966
Model the datahardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is that the data is pre-aggregated in Power Query, so report-level filters cannot re-aggregate. This is because the GROUP BY and aggregation operations in the M code collapse the raw transactional rows into summarized totals before the data ever reaches the Power BI model; once loaded, those 10,000 rows are static aggregates with no underlying detail to recalculate. On the PL-300 exam, this scenario tests your understanding of where data shaping occurs—Power Query vs. the report layer—and it’s a common trap: candidates often assume a date table relationship or data type issue is at fault, but the real culprit is the loss of granularity during pre-aggregation. The pre-aggregated data filter issue here is that filters like OrderDate can only slice the existing aggregated rows, not recompute totals from scratch. Remember the memory tip: “If it’s grouped in M, filters can’t re-aggregate—detail is gone, so totals stay the same.”

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.

Exhibit

Refer to the exhibit.

Exhibit: Power Query M code snippet
let
    Source = Sql.Database("Server01", "AdventureWorks"),
    Sales = Source{[Schema="Sales",Item="SalesOrderHeader"]}[Data],
    #"Filtered Rows" = Table.SelectRows(Sales, each [OrderDate] >= #date(2020,1,1)),
    #"Grouped Rows" = Table.Group(#"Filtered Rows", {"CustomerID"}, {{"TotalDue", each List.Sum([TotalDue]), type nullable number}}),
    #"Sorted Rows" = Table.Sort(#"Grouped Rows",{{"TotalDue", Order.Descending}})
in
    #"Sorted Rows"

After loading the data using the Power Query M code shown in the exhibit, the model contains a table with 10,000 rows. However, when users filter by OrderDate in a report, the filter does not affect the aggregated TotalDue values. What is the most likely reason?

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.

Question 1hardmultiple choice
Full question →

Exhibit

Refer to the exhibit.

Exhibit: Power Query M code snippet
let
    Source = Sql.Database("Server01", "AdventureWorks"),
    Sales = Source{[Schema="Sales",Item="SalesOrderHeader"]}[Data],
    #"Filtered Rows" = Table.SelectRows(Sales, each [OrderDate] >= #date(2020,1,1)),
    #"Grouped Rows" = Table.Group(#"Filtered Rows", {"CustomerID"}, {{"TotalDue", each List.Sum([TotalDue]), type nullable number}}),
    #"Sorted Rows" = Table.Sort(#"Grouped Rows",{{"TotalDue", Order.Descending}})
in
    #"Sorted Rows"

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 data is pre-aggregated in Power Query, so report-level filters cannot re-aggregate.

Option C is correct because the GROUP BY and aggregation happen in Power Query before loading, so the data is pre-aggregated and static. Filters applied in the report cannot re-aggregate because the underlying detail is lost. Option A is wrong because the Date table relationship is not the issue; the data is already aggregated. Option B is wrong because the data type is fine. Option D is wrong because the refresh is not related.

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 TotalDue column is not a numeric type.

    Why it's wrong here

    The data type is nullable number, which is numeric.

  • The data is pre-aggregated in Power Query, so report-level filters cannot re-aggregate.

    Why this is correct

    Pre-grouping in Power Query loses the detail rows; filters cannot re-evaluate aggregates without the underlying data.

    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 dataset is not refreshing properly.

    Why it's wrong here

    Refresh is not relevant to the filtering issue.

  • The Date table has no relationship to the Sales table.

    Why it's wrong here

    Even if there is a relationship, the pre-aggregated data cannot be filtered by date because the original OrderDate is lost.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Detailed technical explanation

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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 PL-300 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

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.

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 data is pre-aggregated in Power Query, so report-level filters cannot re-aggregate. — Option C is correct because the GROUP BY and aggregation happen in Power Query before loading, so the data is pre-aggregated and static. Filters applied in the report cannot re-aggregate because the underlying detail is lost. Option A is wrong because the Date table relationship is not the issue; the data is already aggregated. Option B is wrong because the data type is fine. Option D is wrong because the refresh is not related.

What should I do if I get this PL-300 question wrong?

Identify which PL-300 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PL-300 practice questions

Last reviewed: Jun 7, 2026

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.

Loading comments…

Sign in to join the discussion.

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.