Exam PL-300 All QuestionsBrowse all questions from this exam
Question 59

HOTSPOT -

You are creating a Microsoft Power BI data model that has the tables shown in the following table.

The Products table is related to the ProductCategory table through the ProductCategoryID column. Each product has one product category.

You need to ensure that you can analyze sales by product category.

How should you configure the relationship from ProductCategory to Products? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Hot Area:

    Correct Answer:

    Box 1: One-to-many -

    The one-to-many and many-to-one cardinality options are essentially the same, and they're also the most common cardinality types.

    Incorrect: A many-to-many relationship means both columns can contain duplicate values. This cardinality type is infrequently used. It's typically useful when designing complex model requirements. You can use it to relate many-to-many facts or to relate higher grain facts. For example, when sales target facts are stored at product category level and the product dimension table is stored at product level.

    Box 2: Single -

    Incorrect:

    Bear in mind that bi-directional relationships can impact negatively on performance. Further, attempting to configure a bi-directional relationship could result in ambiguous filter propagation paths. In this case, Power BI Desktop may fail to commit the relationship change and will alert you with an error message.

    Reference:

    https://docs.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand

Discussion
mindstemall

Silly comments here. One-to-many because several products have the same product category. Single because the performance is much better and the assignment states only that you need to be able to analyze sales by product category.

learnazureportal

Your answer is correct. however, we don't choose single, b/c it has better performance. b/c data flows from product to ProductCategory. This is the reason, we choose single.

Hoeishetmogelijk

you are both right

vivian_data

How did we figure out that the data flows from Product to Product Category and not the other way around??

vivian_data

Nevermind, here's the answer: "For one-to-many relationships, the cross filter direction is always from the "one" side, and optionally from the "many" side (bi-directional). " https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand

ZSun

This is the wrong explanation about "Single". When we choose one-to-many of "ProuctCat to Product", the default direction of single is from ProuctCat->Product. However, "analyzing sales by product category" means, information from sales->Product->ProductCat. This is the opposite direction of our single direction. Therefore, it should be Both. Keep in mind, the single direction is determined by your one-to-many design.

Bnxyl

Guys take note. This is tested and confirmed. At first, I wanted to abuse you but then something told me to first put it into practice. And yes. It is one to many and Both. Thank you for standing out

Elfmo11

But the direction is about the way the filter works. Since analysing sales by ProductCategory means you filter from ProductCategory (via Product) to Sales, the direction is one way from ProductCategory to Sales.

HamzaMJ

1 - One to many because every product category has many products 2 - Both because we need to analyze sales by product category

KobeData

Yu always filter from the one side, which in this case, is the productCategory. So one to many - single means filtering from one to the many side, which is correct. So it should be single. Hope this helps.

scotchtapebunny

you want to analyse SALE BY PRODUCT CATEGORY, you need cross filter direction single to make this work. If you do both that means you want to analyze PRODUCT CATEGORY by SALE. This doesn't make sense so there is no need for both. You're going downstream from product category to sales not the other way around. This is what I think but I'd be thankful if someone can help me if I am wrong.

Booster21

I totally agree what you said that "If you do both that means you want to analyze PRODUCT CATEGORY by SALE.", otherwise single can do the trick. I was confused when to use BOTH earlier.

Nandini_Shanthaveerappa

For example, if we want to see the sales by product(Coffee, Tea, Milk) in each region(US, UK, IN). Say we dont want show the product names in the visuals if there no sales for that product in a specific region. So we use bidirectional so that the region and product tables are filtered for only sold products.. where it will not return blank if there's no sale for product tea in US .. it shows sales values for Coffee and Milk only

SamuComqi

I passed the exam today (948/1000). My answer was: - One-to-many - Single

UlyUkr

1. One to many, because one Product Category can have many Products. 2.Single. It allows to calculate Sales by Product Category. Also the best practice as per this article https://learn.microsoft.com/en-us/power-bi/transform-model/desktop-relationships-understand Also I tested in Power BI. If you have doubts, recreate the issue in Power BI and you will get the correct answer.

Patrick666

One-to-many, both

Igetmyrole

One-to-many Singel One-to-many: Each product category can have multiple products belonging to it. Single: Because we want to analyze sales by product category.

Lavi29

It asks relationship from product category to product not vice versa. Filter will take place at many * direction. So keeping it one to many means product category to product one to many , which is wrong. As there is not an option of many to one then many to many is the best choice here. And for many to many we always need filter in both directions. So the answer is many to many and both.

bakamon

question is asking ProductCategory to Product Relation.. For sure it will be one to many.. if it was product to productcategory, then it would be one to one and cross filter : single for performance..

Shalaleh

one-to-many single

Mati_123

1 - One to Many 2- Single dirction

SumaiyaShah

We cant make a 1 to 1 cardinality relationship single directional I guess

Flix

One-to-many because several products have the same product category. Both, because the filter goes via Products and One-to-many is from product to category.

KipngenohVinnie

The answer is correct, one to many, that is from ProductCategory to Products, and direction is Single

Moin23

Each product has one product category. isn't one-to-one ? They didn't say, every Product has "atleast" one product category configure the relationship from ProductCategory to Products? One - Product Category side Many on Product side ? right

Mo2011

No, this means one category has many products so it one (category) to many (products)

MoneyStacking

For the Guys and Girls, At this page, you will no longer find any free questions from Examtopics. However, if you're hesitant about purchasing Contributor Access, don't hesitate any longer; buy it. It costs only $50 and provides a significant boost to your CV and career. I recently passed with a score of 917 out of 1000. Save yourself time by learning and memorizing all these questions, as 85% of the 50 exam questions were identical to those provided here. Cheers and good luck!

Bnxyl

After further analysis. I think there are two answers available to this Answer set A: One to many and Single Anwer SET B: One to one and both

Bnxyl

But thinking deeper, What is the, The product table and Product category table must be having a one to one cardinality otherwise this would mean that the Products table and sales table will be having a many to many relationship considering that they are related via the product ID. Thus to me the final answer should be One to one and then both directions

RazaTheLegend

1 - One to Many 2- Single direction