PL-300 Model the data Practice Question
A Power BI data model includes a table 'Orders' with columns OrderID, CustomerID, OrderDate, SalesAmount. The model also has a 'Date' table and a 'Customer' table. The relationships are: Orders[CustomerID] -> Customer[CustomerID] (many-to-one, single direction) and Orders[OrderDate] -> Date[Date] (many-to-one, single direction). A user creates a measure that sums SalesAmount and then filters by a slicer on Customer[City]. The slicer works correctly. However, when the user adds another slicer on Date[Year], the measure does not respect both slicers simultaneously. What is the most likely cause?
⚠ Common exam trap
It's easy for candidates to assume filter propagation direction is the problem, but the real issue is that DAX filter removal functions like ALL or ALLEXCEPT can silently override slicer filters, making it appear as though the relationship is broken.
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
✓
The measure might be using ALL or ALLEXCEPT that removes the filter context from the Date table.
The measure likely uses ALL or ALLEXCEPT, which removes the filter context from the Date table. Even though the relationships are correctly configured and filters from the Date slicer propagate to Orders via the single-direction relationship, if the measure explicitly ignores those filters using a function like ALL(Date[Year]) or ALLEXCEPT(Orders, ...), the Date slicer will have no effect on the measure. This is a common DAX mistake where filter removal functions override slicer selections.
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 Customer and Date tables are not related to each other.
Why it's wrong here
The Customer and Date tables are both dimension tables connected to the Orders fact table, but they do not need a direct relationship to each other. In a star schema, filter context flows from one dimension to another through the fact table, so a Date slicer on Orders can propagate to Customer via the shared Orders rows. The absence of a direct Customer–Date relationship is therefore not a problem and cannot explain why the slicer is ignored.
- ✗
The relationship between Orders and Date is inactive.
Why it's wrong here
The scenario explicitly states that the relationship between Orders and Date is active, meaning the default filter propagation from Date to Orders is enabled. An inactive relationship would require the measure to use USERELATIONSHIP to activate it, which is not the case here. The real issue is not the relationship's state; rather, the measure itself may be removing the Date filter context using ALL or ALLEXCEPT, which overrides even an active relationship.
- ✗
The relationships are set to single direction, so filters from Date do not propagate to Orders.
Why it's wrong here
Single-direction relationships in Power BI allow filters to propagate from the 'one' side to the 'many' side, so a Date slicer can absolutely filter Orders in a single-direction relationship from Date to Orders. The directionality is correctly configured and does not hinder propagation of the Date year filter. The problem lies not in the relationship direction but inside the measure's filter modifiers, which can strip the Date filter context regardless of relationship direction.
- ✓
The measure might be using ALL or ALLEXCEPT that removes the filter context from the Date table.
Why this is correct
A measure that uses ALL('Date') or ALLEXCEPT('Date') inside CALCULATE explicitly removes the filter context from the entire Date table or from all Date columns except those specified. For instance, CALCULATE(SUM(Orders[Amount]), ALL('Date')) would ignore a slicer on Date[Year], because ALL('Date') clears every filter applied to the Date table, including the Year column. ALLEXCEPT('Date', 'Date'[Month]) would preserve a Month filter but still ignore Year if Year is not in the exceptions list. This is the classic cause when a measure appears unresponsive to slicer selections, even though the underlying relationships and directions are perfectly normal.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-300 question from scratch — 524 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.