The correct answer is to create a bridge table containing ProductID and CustomerID, then establish one-to-many relationships from both the Product and Customer tables to this bridge. This resolves the many-to-many relationship by breaking it into two manageable one-to-many links, a core principle of dimensional modeling that ensures accurate cross-filtering between the two tables. On the PL-300 exam, this scenario tests your understanding of composite models and relationship cardinality, often appearing as a trap where candidates mistakenly try to create a direct many-to-many relationship—which Power BI does not natively support without a bridge. The key insight is that the bridge table acts as an intermediary, storing every valid combination of ProductID and CustomerID, so filters propagate correctly from one table to the other. Remember the mnemonic: “Bridge the gap, don’t map the many”—if you see two dimension tables needing a direct link, always insert a fact-like bridge table to avoid ambiguity.
PL-300 Model the data Practice Question
This PL-300 practice question tests your understanding of model the data. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 creating a Power BI report that requires a many-to-many relationship between 'Product' and 'Customer' tables. What is the recommended way to implement this?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a bridge table with ProductID and CustomerID and create relationships to both tables
Option B is correct because in Power BI, a many-to-many relationship between two tables (e.g., Product and Customer) is best implemented using a bridge table that contains the foreign keys (ProductID and CustomerID) from both tables. This bridge table resolves the many-to-many cardinality by creating two one-to-many relationships: one from Product to the bridge table and one from Customer to the bridge table. This approach ensures proper filtering and avoids ambiguity in the data model, which is a standard best practice in dimensional modeling.
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.
✗
Combine Product and Customer into a single table
Why it's wrong here
This denormalizes the model and leads to data duplication.
✓
Create a bridge table with ProductID and CustomerID and create relationships to both tables
Why this is correct
This resolves the many-to-many relationship correctly.
Related concept
Read the scenario before looking for a memorised answer.
✗
Create a direct many-to-many relationship using the 'many-to-many' cardinality option in Power BI
Why it's wrong here
Direct many-to-many can cause ambiguous filter propagation.
✗
Use a calculated column to concatenate IDs
Why it's wrong here
This does not create a proper relationship.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Power BI has a built-in 'many-to-many' cardinality option that can be applied directly between two tables, but in reality, Power BI requires an intermediary bridge table to properly model such relationships.
Detailed technical explanation
How to think about this question
Under the hood, the bridge table acts as an intermediate factless fact table that stores the association pairs. When you create one-to-many relationships from Product to Bridge and Customer to Bridge, Power BI's VertiPaq engine can traverse these relationships to apply filters correctly, even though the original tables have a many-to-many relationship. A real-world scenario is a sales database where a product can be sold to multiple customers and a customer can buy multiple products; the bridge table (e.g., SalesTransaction) with ProductID and CustomerID enables accurate cross-filtering and aggregation without double-counting.
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: Create a bridge table with ProductID and CustomerID and create relationships to both tables — Option B is correct because in Power BI, a many-to-many relationship between two tables (e.g., Product and Customer) is best implemented using a bridge table that contains the foreign keys (ProductID and CustomerID) from both tables. This bridge table resolves the many-to-many cardinality by creating two one-to-many relationships: one from Product to the bridge table and one from Customer to the bridge table. This approach ensures proper filtering and avoids ambiguity in the data model, which is a standard best practice in dimensional modeling.
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.
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.