Exam PL-300 All Questions

View all questions & answers for the PL-300 exam

Exam PL-300 topic 2 question 32 discussion

Actual exam question from Microsoft's PL-300

Question #: 32
Topic #: 2

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have a Power BI report that imports a date table and a sales table from an Azure SQL database data source. The sales table has the following date foreign keys:
✑ Due Date
✑ Order Date
✑ Delivery Date
You need to support the analysis of sales over time based on all the date foreign keys.
Solution: From Power Query Editor, you rename the date query as Due Date. You reference the Due Date query twice to make the queries for Order Date and
Delivery Date.
Does this meet the goal?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: A 🗳️

by legionairemax at Sept. 17, 2022, 3:54 a.m.

Comments

Submit Cancel

junaid2107

Highly Voted 1 year, 12 months ago

I dont understand What micorsoft hopes to achieve with trick questions. If questions leave so much to the analysts assumptions then the questions isnt testing the candidates knowledge

upvoted 129 times

MoxieTT

1 year, 11 months ago

I keep reading "trick" questions when reading peoples' experiences recently of PL-300.

upvoted 8 times

...

cs3122

1 year, 3 months ago

100% agree. There is so much ambiguity in the questions, and can easily be interpreted ways.

upvoted 3 times

...

legionairemax

Highly Voted 2 years, 7 months ago

The answer is correct. However, I believe the alternate solution given is wrong. I would say that 3 relationships for each date respectively would be made from the Date table to the Sales table. One being active and the other two inactive. Thus, allowing to filter by a specific date column The solution suggested is not required, as the report does not require any output that involves all 3 dates. It requires only sales over one date column at a time. Moreover, being date tables, they can significantly increase the size of the model (considering that the table is sales related).

upvoted 23 times

...

b2775a4

Most Recent 2 months, 3 weeks ago

Selected Answer: A

• Power BI only allows one active relationship between two tables. By creating separate date tables, you can create active relationships for all three date keys. • Each date table filters the sales table independently, allowing accurate analysis based on • Referencing the date table avoids duplicating the table manually and keeps the solution efficient.

upvoted 1 times

...

jaume

5 months, 1 week ago

Selected Answer: B

I think even referencing two queries to the first one is not ensuring the import of just a sample of the data, this only can be achieved by filtering the data in the query retrieving the data into our model. If first query is not set in the right way to get only sample of the data, other two queries would retrieve same dataset and it would be not just a sample. My vote here is for B.No

upvoted 2 times

jaume

5 months, 1 week ago

Dismiss my previous comments, I though this is still series initiated in Q29 but Q29 is a single question despite what it mentions at the beginning. Spliting the date table in three tables would allow us to set three ACTIVE relationships in the data model to support the analysis but there is nothing related to the relationships mentioned in the question so I would vote for B.No

upvoted 1 times

...

8b7b763

6 months, 2 weeks ago

A. Yes. You can only have 1 active relationship at a time. Userelationship places processing on the report layer via dax. Use powerquery to add the dimension date tables. Do your regular Dax calculations after.

upvoted 1 times

...

rcaliandro

8 months, 1 week ago

Selected Answer: B

I would say No

upvoted 1 times

...

agelee

9 months, 2 weeks ago

I think B. Nothing said about USERELATIONSHIP. Without mentioning it I think the answer is NO.

upvoted 1 times

...

bc23451

10 months, 2 weeks ago

I think it's B because Due Date come after Order Date so if we reference with the Due Date, you may not have all date for Order Date. That's my point of view.

upvoted 1 times

...

jsav1

11 months, 3 weeks ago

Selected Answer: A

It gives you three separate date tables but without having to import the date data 3 times.

upvoted 1 times

...

GowthamMupparapu

1 year, 1 month ago

Selected Answer: A

Please suggest if my thought process is not aligned with the question's constraints. As it is said in the proposed solution cant we reference the initial date table 2 more times to obtain other date tables ?? (By renaming the tables and deleting other two irrelevant columns)

upvoted 2 times

...

Dsbuff

1 year, 4 months ago

Selected Answer: A

A is correct. ChatGPT's response: Creating separate queries in Power Query for each date (Due Date, Order Date, and Delivery Date) by referencing a base date query is a recommended way to deal with role-playing dimensions. This method involves creating separate date tables for each date role you need to analyze. In Power BI, each of these tables will be related to the sales table using the respective date foreign key. This approach allows for creating active relationships between the sales table and each of the date tables, which enables the use of these dates in filters, slicers, and visuals without the need for DAX measures to handle inactive relationships. It is a common and efficient way to support analysis by different date roles within the same model.

upvoted 3 times

...

burto

1 year, 5 months ago

wouldnt it be that since they are imported datasets it would be more productive to use DAX to transform the data?

upvoted 2 times

...

WRTopics

1 year, 6 months ago

Selected Answer: B

I'll select B.

upvoted 2 times

...

Igetmyrole

1 year, 7 months ago

B is the correct answer. No, this solution does not meet the goal of supporting the analysis of sales over time based on all the date foreign keys. Renaming the date query as "Due Date" and referencing it twice in Power Query Editor does not create relationships between the sales table and the date table based on the difference date foreign keys (Due Date, Order Date, and Delivery Date).

upvoted 7 times

...

rgabage

1 year, 7 months ago

Selected Answer: A

A. This was in the learning path.

upvoted 4 times

Elektrolite

1 year, 1 month ago

link, or gtfo

upvoted 10 times

...

Badadadiiii

1 year, 8 months ago

Selected Answer: A

The key to answering this question correct, is this sentence "You need to support the analysis of sales over time based on all the date foreign keys." You cannot achieve this without 3 date tables, which is created in Power Query. 1 is loaded from Azure, the other two are created by reference to the first. If you have one date table with 1 active and 2 inactive relationships, then you won't be able to use all 3 dates in the same analysis.

upvoted 3 times

...

MEG_Florida

1 year, 8 months ago

Selected Answer: B

I am going with B and here is why. It says they renamed it. Then they said they used it for 2 of the dates, not all 3. So technically there isn't 3 queries being run just 2... Thoughts?

upvoted 3 times

og44

1 year, 5 months ago

I gues whwn you reference twice, it means you are adding two aditional copies, hence you have 3 tables. But as the question does not talk about relationship, that is the source of ambiguity.

upvoted 7 times

...

Load full discussion...

Exam PL-300 All Questions

View all questions & answers for the PL-300 exam

Exam PL-300 topic 2 question 32 discussion

Comments

junaid2107

MoxieTT

cs3122

legionairemax

b2775a4

jaume

jaume

8b7b763

rcaliandro

agelee

bc23451

jsav1

GowthamMupparapu

Dsbuff

burto

WRTopics

Igetmyrole

rgabage

Elektrolite

Badadadiiii

MEG_Florida

og44

SY0-701