Exam DA-100 topic 2 question 11 discussion

I think that should be many-to-one and single. Because one category have multiple products, but one product it's in one category.

One to many and single ?

https://www.youtube.com/watch?v=30OrlrKbXsw

the question productcat to product and vice versa has been reversed.. check PL 300 exam topic question https://www.examtopics.com/discussions/microsoft/view/84214-exam-pl-300-topic-2-question-27-discussion/

Should be One-To-Many and Single. One-To-Many (same as Many-to-One but that's not an option here so you use this) Single - Generally always use Single but if you're trying to filter Sales from a field within the Products table, then you'd use both because filtering is like a pathway but because product category is a separate table then you can still filter sales by it without having to use anything from the Products Table. The only way this wouldn't work is if for some reason you linked both fact tables (Sales and Products) and Sales had no direct relationship to Product Categories but in general, you never link fact tables together. Instead, you link them both by common Dimension (Lookup) tables like the Product Category

One-to-many and both. If you set "single" you can't count how many products per categories you have sold see: https://docs.microsoft.com/en-us/dax/crossfilter-function

It is obviously many-to-many. The direction is from Products to ProductCategory. Each product category can obviously have more than one product. So it must be many-to-many or many-to-one. Since the latter is not an option, many-to-many is correct.

One to Many and Both because you are asked to analyse sales by product category. So product category has to slice the sales which means you are going against the flow so you have to set up the filter to "both".

One to Many & Single, It's Snowflake schema filter flows down to analyse data.

one to many relationship from Product Category to product and one to many relationshiop from products to sales, so the answer is one to many relationship and single direction in order to analyze from product category

Stupid donkeys gave the answers for this question. Both and Single - works both, but you should add both-directional links only if you really need it, but it isn't required here. So one-to-many, single.

It is FROM products to product category, therefore the answer MUST be "Many to Many" since "Many to One" is not an option.

"Many to Many" and "Both" A product can fall into multiple category and a category can have multiple products. For example a product called "Surface Pro" can be in two categories- "Windows Device" and "Tablet PC". Also "Windows Device" category can have multiple products.

In my opinion Several products can belong to the same category, (eg. apples, bananas, oranges belong to the fruit category). So the relationship between ProductCategory and Product is one-to-many. As filter propagation is always done one-to-many, ProductCategory filter propagated trough Products which in turn will filter Sales. That said... Carnality: One-to-Many Cross-filter direction: Single

Since we only have these options, what makes sense is one-to-many and both. The reason is the question, which is to get sales by product category. You need to filter data from sales to Product and from ProductCategory to Product. At least this is how I understood. Thanks @Markar

I go over this question and can't think of correct solution given the answers given. So I declare this questions as broken. If there was N:1 for Products to Categories, then the direction shall be Single, since Sales is likely to be the many sales to one product. The direction will allow it to be Single.

After testing most of us confirmed that "many to one" is correct but the request clearly says "configure the relationships from Products to ProductCategory" and in the available options we do not have "many to one". I believe it would be wrong to choose "one to many" instead since that one is not valid relationship.