The answer is that the many-to-many relationship is causing ambiguity in measure evaluation, which leads to incorrect totals. This occurs because Power BI’s engine cannot determine a unique path for aggregating values across the bridge table, so measures like SUM or COUNT may double-count or misattribute rows when multiple related fields are used in the same visual. On the Microsoft Power BI Data Analyst PL-300 exam, this scenario tests your understanding of relationship modeling and the limitations of many-to-many cardinality, often appearing as a trap where you might blame cross-filter direction or data types instead. A common memory tip: think of a many-to-many relationship as a “crosswalk” without a traffic cop—without a clear direction, values can wander and inflate totals. Remember the mnemonic “M2M = Measure Mayhem” to recall that ambiguity, not filters or security, is the root cause.
PL-300 Visualize and analyze the data Practice Question
This PL-300 practice question tests your understanding of visualize and analyze 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 designing a Power BI report for executives. The dataset contains sales data with a many-to-many relationship between 'Sales' and 'Product' tables via a 'ProductSales' bridge table. Users complain that some measures return incorrect totals when using multiple related fields. 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
✓
The many-to-many relationship is causing ambiguity in measure evaluation
Option D is correct because many-to-many relationships in Power BI can cause ambiguity in measure evaluation, leading to incorrect totals. Option A is wrong because row-level security is not directly related to many-to-many relationships. Option B is wrong because cross-filter direction does not typically cause this issue. Option C is wrong because data types are not the root cause.
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 many-to-many relationship is causing ambiguity in measure evaluation
Why this is correct
Many-to-many relationships can lead to ambiguous filter propagation, causing incorrect totals.
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.
✗
Data type mismatches between key columns
Why it's wrong here
Data type mismatches would cause relationship errors, not incorrect totals.
✗
The cross-filter direction is set to single instead of both
Why it's wrong here
Many-to-many relationships require both directions, but this alone does not explain incorrect totals.
✗
Row-level security (RLS) is filtering out some rows
Why it's wrong here
RLS would affect all measures consistently, not just totals.
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.
Visualize and analyze the data — This question tests Visualize and analyze the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The many-to-many relationship is causing ambiguity in measure evaluation — Option D is correct because many-to-many relationships in Power BI can cause ambiguity in measure evaluation, leading to incorrect totals. Option A is wrong because row-level security is not directly related to many-to-many relationships. Option B is wrong because cross-filter direction does not typically cause this issue. Option C is wrong because data types are not the root cause.
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 →
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.