Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Hello Experts,
Question DA-100
You are creating a Microsoft Power BI data model that has the tables shown in the following table.
| Table Name | Column name |
| sales | salesID |
| ProductID | |
| Datekey | |
| SaleAmount | |
| Products | ProductID |
| ProductName | |
| ProductCatagoryID | |
| ProductCatogory | ProductCatagoryID |
| CatagoryName |
The Products table is related to the ProductCatagory table through the ProductCatagotyID column.
You need to ensure that you can analyze sales by product category.
How should you configure the relationships from Products to ProductCatagory?
Solved! Go to Solution.
The Question "You need to ensure that you can analyze sales by product category."
no need to use "Both" direction
open Power BI desktop
On the Modeling tab, select Manage relationships > New.
In the Create relationship dialog box, in the first table drop-down list, select a table. Select the column you want to use in the relationship.
In the second table drop-down list, select the other table you want in the relationship. Select the other column you want to use, and then select OK.
The Answer Area is as follows in the exam !
| Cardinality | |
| one-to-many | |
| one-to-one | |
| Many-to-many | |
| Cross filter direction | |
| single | |
| both |
Cardinality: one-to-many
Cross filter direction: single
Because one product category may have many products
I think like you but please check the following link:
The Question "You need to ensure that you can analyze sales by product category."
no need to use "Both" direction
Thank you for your reply.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 22 | |
| 22 | |
| 18 | |
| 16 | |
| 13 |
| User | Count |
|---|---|
| 63 | |
| 42 | |
| 40 | |
| 40 | |
| 38 |