Courseiva
Model the data →easyMultiple Choice

DAX Measure for Counting Students in a Many-to-Many Relationship

When creating a many-to-many relationship between two tables, what is a common approach to model this in Power BI?

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

✓

Introduce a bridge table that contains the unique combinations.

The correct answer is C: introduce a bridge table that contains the unique combinations, because Power BI's recommended pattern for many-to-many relationships is to create a junction (bridge) table with one row per unique pairing of the two entity keys, then relate each original table to the bridge via one-to-many relationships. This keeps the model star-schema-like, avoids ambiguous filter paths, and lets DAX propagate filters correctly across both dimensions. Option A is wrong because CROSSJOIN in a calculated table just produces a Cartesian product of all rows and does not establish a proper relational model. Option B is wrong because merging both tables into one denormalized table destroys the separate entities and causes duplication and aggregation errors. Option D is wrong because although Power BI can technically create a direct many-to-many relationship, it is not the common or recommended modeling approach and can produce ambiguous or incorrect results.

Answer analysis

Option-by-option breakdown

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

  • ✗

    Use the CROSSJOIN DAX function in calculated tables.

    Why it's wrong here

    CROSSJOIN in a calculated table returns every possible combination of all columns from the input tables—a Cartesian product—yielding a static, often enormous table that is not linked to the source tables by any relationship metadata. A correct bridge table, by contrast, contains only the unique key combinations that actually exist and serves as a filter-propagation hub with two one-to-many relationships, whereas a CROSSJOIN table has no keys or grain and introduces massive data redundancy that degrades performance. Additionally, calculated tables are evaluated at model refresh, so a CROSSJOIN cannot respond to user filters or participate in dynamic segmentation, making it a data transformation rather than a relationship solution.

  • ✗

    Merge both tables into a single table.

    Why it's wrong here

    Merging both tables into a single physical table eliminates the many-to-many relationship by destroying the grain of each original table—duplicating rows and mixing columns from both entities into one denormalized structure. This causes measure aggregation to produce inflated or incorrect results because filters can no longer flow from one named table to another, and any change to one side of the relationship forces you to restructure the merged table. A proper model keeps the two tables separate and adds a bridge table so that each relationship is explicit and filter direction is controllable, preserving the semantic meaning of each table's grain.

  • ✓

    Introduce a bridge table that contains the unique combinations.

    Why this is correct

    Introducing a bridge table (also called a junction or associative table) is the standard way to model a many-to-many relationship in Power BI: it stores one row for each unique pair of keys from the two original tables, and then you create two one-to-many relationships with the bridge table as the 'many' side on both. This configuration allows filter context to flow from either original table through the bridge to the other, resolving the many-to-many condition without ambiguity. For correctness, the bridge table must contain distinct composite keys and may include additional attribute columns such as weight or validity dates, and you must be careful with cross-filter direction to avoid fan-out and double-counting in measures.

  • ✗

    Create a direct many-to-many relationship in the model.

    Why it's wrong here

    The Power BI Tabular engine only supports relationships with cardinality one-to-one or one-to-many between two tables; a direct many-to-many relationship is not available in the relationship editor, so you cannot simply connect two tables where both key columns contain duplicates. Even if you attempt to force it, the model will return an error or require automatic bridge-table creation behind the scenes, which is not a direct relationship but a hidden junction. The proper, explicit approach is to create your own bridge table and define two one-to-many relationships, giving you control over how filters flow and preventing the ambiguous lineage that a direct M:N mapping would introduce.

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

You might also like

Similar PL-300 questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · 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.