ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam PL-300 All Questions

View all questions & answers for the PL-300 exam
Go to Exam

Exam PL-300 topic 2 question 33 discussion

Actual exam question from Microsoft's PL-300
Question #: 33
Topic #: 2
[All PL-300 Questions]

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 the Fields pane, you rename the date table as Due Date. You use a DAX expression to create Order Date and Delivery Date as calculated tables.
Does this meet the goal?

  • A. Yes
  • B. No
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by fred92 at Oct. 21, 2022, 3:15 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
fred92
Highly Voted 2 years, 6 months ago
Selected Answer: A
Yes, that will meet the goal. It will increase the model size, but that was not the question.
upvoted 28 times
CHT1988
2 years, 5 months ago
I agree with you. The model size is not mentioned in the question, so it would meet the goal.
upvoted 3 times
...
...
poujor
Highly Voted 2 years, 6 months ago
NO is the Answer. To be able to create the calculations you need the Relationships. They are NOT stated in this suggestion.
upvoted 21 times
Tiz88
2 years, 5 months ago
These type of questions are not really clear. But agreed, you clearly need relationships. What if you have "autodetect relationship" option active?
upvoted 5 times
...
sdawn
1 year, 4 months ago
foreign keys imply having relationships in place, therefore it is absurd to assume otherwise.
upvoted 2 times
...
...
Odidepse
Most Recent 3 months, 3 weeks ago
Selected Answer: B
NO This will require relationship between the data and sales table to work, renaming the date table and using DAX expression wont be a solution without relationship.
upvoted 2 times
...
jaume
5 months, 2 weeks ago
Selected Answer: B
We are resulting in three different date tables which could allow us to set three active relationships (as in the previous question) but there is still no mention about relationships that must be required to support the requested analysis so I would answer B.No
upvoted 1 times
...
bd76d92
5 months, 3 weeks ago
If its a long solution, correct if its a short solution, incorrect
upvoted 1 times
...
rcaliandro
8 months, 2 weeks ago
Selected Answer: A
Yes, this will meet the goal
upvoted 1 times
...
agelee
9 months, 2 weeks ago
The question is if we do it in PowerQuery Editor. It's not said. In PowerQuery we can create a copy of table by DAX usage and it will work. "Create a copy of the role-playing table, providing it with a name that reflects its role. If it's an Import table, we recommend defining a calculated table. If it's a DirectQuery table, you can duplicate the Power Query query." Departure Airport = 'Arrival Airport'. "Create an active relationship to relate the new table."
upvoted 1 times
...
Moppu
1 year, 2 months ago
Selected Answer: A
Think the answer should be A, but you need the relationships. Not sure why this question is more one sided than the one above though.
upvoted 3 times
...
lukelin08
1 year, 3 months ago
A. Yes (is correct) it's not the best method but it works
upvoted 1 times
...
Ryan_042
1 year, 5 months ago
Selected Answer: B
Creating a calculated table does not keep the original table relationship. This solution is even worse than the one using Power Query to duplicate the 3 date tables. If the auto-detect relationship is enabled, at least using Power Query might not require a relationship.
upvoted 2 times
...
RMUK
1 year, 6 months ago
No, again its about how will you design the data model. Even if you can create multiple date table for each date field. Standard approach in this case should be one date table, 1 active and 2 inactive relationships.
upvoted 1 times
...
WRTopics
1 year, 6 months ago
Selected Answer: B
No, the correct answer is B.
upvoted 1 times
...
protivitiuser
1 year, 6 months ago
after you read this https://learn.microsoft.com/en-us/power-bi/guidance/relationships-active-inactive the answer should be clear
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. Remaining the date table as "Due Date" and creating calculated tables for Order Date and Delivery Date using DAX expressions does not establish relationships between the sales table and the date table based on the different date foreign keys (Due Date, Order Date, and Delivery Date).
upvoted 3 times
...
sergeyitaly
1 year, 8 months ago
Noone of those who say Yes did not mention about creation relationship in the model. And this is a key element in data analysis. So, the answer is No.
upvoted 2 times
...
bakamon
1 year, 10 months ago
Selected Answer: B
No, the reference link given in the answer shows that it needs inactive relationship
upvoted 1 times
...
PREM77
1 year, 11 months ago
Answer is No. Renaming the date table as "Due Date" and creating calculated tables for "Order Date" and "Delivery Date" will not provide the necessary functionality for analyzing sales over time. To achieve the goal, you would typically create relationships between the date table and the sales table based on the respective date foreign keys. This allows Power BI to perform time-based analysis by using the relationships to filter and aggregate data. Instead of renaming the date table, you should keep it as a separate table, typically named "Date" or "Calendar." Then, you would establish relationships between the date table and the sales table using the respective date foreign keys: Due Date, Order Date, and Delivery Date.
upvoted 4 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago