Microsoft Certified: Fabric Analytics Engineer AssociateImplement and manage semantic models (30-35%)Easy
A data engineer is working with a semantic model in Microsoft Fabric that includes a 'Sales' table and a 'Products' table. There is a one-to-many relationship between 'Products' (one) and 'Sales' (many) based on a 'ProductID' column. The engineer needs to calculate the total sales amount for each product. Which cross-filter direction should be configured for the relationship to correctly filter sales by product?
- ANone
- BBoth
- CSingle (Sales to Products)
- DSingle (Products to Sales)
Show answer & explanationAnswer & explanation
Correct answer: D. Single (Products to Sales)
In a one-to-many relationship, filtering typically flows from the 'one' side (Products) to the 'many' side (Sales) to correctly aggregate values like total sales for each product.
Why the other options are wrong
- A. No cross-filter direction would prevent any filtering between the tables, making aggregations across them impossible.
- B. While 'Both' might seem flexible, it can introduce ambiguity and create circular dependencies in complex models, often making 'Single' a safer choice.
- C. Filtering from 'many' to 'one' is less common for aggregation and can lead to unexpected results.
Cross-filter Direction (One-to-Many)
The direction in which filters propagate through a relationship in a semantic model, typically from the 'one' side of a one-to-many relationship to the 'many' side.
- Determines how filters from one table affect another.
- For one-to-many, usually from 'one' to 'many' for correct aggregation.
- Incorrect direction can lead to wrong calculations or errors.
Memory trick: Filter flows from the source of truth to the detailed records.