PL-300 · Question #367
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 h
The correct answer is A. Yes. Renaming a date table to align with a specific date foreign key in a sales table helps clarify its primary relationship and supports analysis for that specific date dimension.
Question
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 three dates at the same time. 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. You create active relationships between the sales table and each date table. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(25 responses)- A72% (18)
- B28% (7)
Why each option
Renaming a date table to align with a specific date foreign key in a sales table helps clarify its primary relationship and supports analysis for that specific date dimension.
Renaming the generic date table (e.g., 'Date' to 'Due Date') when it's actively related to the 'Due Date' column in the sales table makes the model clearer and explicitly supports analysis based on due dates. While it doesn't solve for *all three* date dimensions simultaneously without additional copies of the date table or DAX with inactive relationships, it's a valid step towards enabling analysis for at least one of the required date types.
The act of renaming the table to 'Due Date' establishes or clarifies its role for one of the date dimensions, which is a step in enabling analysis for that specific date field, thus partially meeting the goal of supporting analysis across multiple date dimensions.
Concept tested: Date dimension role-playing relationships
Source: https://learn.microsoft.com/en-us/power-bi/guidance/star-schema#date-table-role-playing-dimensions
Community Discussion
No community discussion yet for this question.