The correct answer is that the relationship may cause ambiguity because the granularity of the tables is different. This granularity mismatch occurs because the Sales table stores data at the day level, while the Targets table aggregates data at the month level; when you filter Sales by a specific day, Power BI cannot automatically determine how to propagate that filter to the monthly Targets table, leading to incorrect or unexpected results in your measure. On the PL-300 exam, this scenario tests your understanding of relationship cardinality and filter propagation—a common trap is assuming a many-to-one relationship always works cleanly, but the real issue is the mismatch in granularity, not the relationship type. To handle this, you must either aggregate the daily Sales data to the month level in your measure or use a separate date table to bridge the granularity gap. Memory tip: think "day-to-month mismatch equals filter ambiguity"—always align granularity before building measures.
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 have a Power BI data model with a table named 'Sales' and a table named 'Targets'. The 'Sales' table contains daily sales data, and the 'Targets' table contains monthly sales targets for each product category. You need to create a measure that calculates the percentage of target achieved for the current month. The relationship between 'Sales' and 'Targets' is on CategoryID and Month. However, the 'Sales' table has a granularity of day, while 'Targets' has month. What issue might you encounter when creating this measure?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The relationship may cause ambiguity because the granularity of the tables is different
Option A is correct because the different granularities can cause ambiguity in the relationship if not properly managed. When 'Sales' is filtered by a specific day, the relationship to 'Targets' may not filter correctly because 'Targets' is at month level. Option B is wrong because data type mismatch is not mentioned. Option C is wrong because many-to-many is not the issue; the relationship is likely many-to-one. Option D is wrong because bidirectional filtering is not necessary and could cause issues.
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 relationship requires bidirectional cross-filtering to work correctly
Why it's wrong here
Bidirectional filtering is not required and may cause performance issues.
✓
The relationship may cause ambiguity because the granularity of the tables is different
Why this is correct
Daily sales data aggregates to month level; the relationship may need special handling.
Related concept
Read the scenario before looking for a memorised answer.
✗
The relationship will create a many-to-many cardinality that slows performance
Why it's wrong here
The relationship is likely many-to-one; many-to-many is not assumed.
✗
The relationship will not work because the columns have different data types
Why it's wrong here
No data type mismatch is indicated.
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.
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 relationship may cause ambiguity because the granularity of the tables is different — Option A is correct because the different granularities can cause ambiguity in the relationship if not properly managed. When 'Sales' is filtered by a specific day, the relationship to 'Targets' may not filter correctly because 'Targets' is at month level. Option B is wrong because data type mismatch is not mentioned. Option C is wrong because many-to-many is not the issue; the relationship is likely many-to-one. Option D is wrong because bidirectional filtering is not necessary and could cause issues.
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.
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.