Courseiva
Model the data →easyMultiple Choice

Modeling Many-to-Many Relationships in Power BI

You are modeling a many-to-many relationship between 'Student' and 'Class' tables. Which approach should you use in Power BI to handle this?

⚠ Common exam trap

Test-takers frequently confuse bidirectional cross-filtering (Option B) as a direct solution for many-to-many relationships, but Power BI requires a bridge table to properly resolve the cardinality, as bidirectional filtering alone does not create the necessary intermediate structure.

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

✓

Add a bridge table with composite keys

A many-to-many relationship in Power BI requires a bridge (or junction) table that contains composite keys (e.g., StudentID and ClassID) to resolve the relationship into two one-to-many relationships. This allows Power BI to properly filter and aggregate data across both tables without ambiguity.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Merge both tables into one

    Why it's wrong here

    Merging both tables into one physically denormalizes the data, which destroys the row-level grain of the fact table and multiplies dimension attributes across every matching record. This introduces fan-out and duplicate values that make aggregate measures like SUM unreliable, because the same underlying fact is counted multiple times. A merge may work only for simple lookups, but for a true many-to-many modeling problem it eliminates the ability to independently filter each side without unintended row inflation.

  • ✗

    Use bidirectional cross-filtering

    Why it's wrong here

    Bidirectional cross-filtering only changes how filters propagate between tables that already have a defined relationship; it cannot create the missing intermediate structure required to resolve a many-to-many cardinality. In a many-to-many scenario, applying bidirectional filtering across the direct relationship causes ambiguous filter paths and can trigger circular dependency errors or unexpected row multiplication. The correct approach is to introduce an associative entity, not to force filter flow through a relationship that still logically represents the same many-to-many pairing.

  • ✓

    Add a bridge table with composite keys

    Why this is correct

    Adding a bridge table with composite keys decomposes the many-to-many relationship into two separate one-to-many relationships: each original table relates to the bridge table on its respective key, and the bridge table stores only valid combinations. This makes the relationship graph acyclic and unambiguous, so filter propagation follows clear paths from one dimension through the bridge to the other dimension without double-counting. Composite keys in the bridge ensure that the join preserves the exact pairing of rows, which is the standard star-schema pattern for resolving many-to-many cardinality in Power BI.

  • ✗

    Create a single one-to-many relationship

    Why it's wrong here

    Creating a single one-to-many relationship is impossible when the underlying tables genuinely have a many-to-many cardinality, because neither table contains a unique column that can act as the 'one' side of the join. Without a key with unique values, Power BI will either return an error or force you to treat the relationship as many-to-many, which merely replicates the original problem. A single relationship also fails to provide the necessary intermediary table that lets filters flow in a controlled, non-ambiguous way, so this option does not actually solve the modeling requirement.

Visual reference

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

About these practice questions

One of 524 original PL-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.