Exam PL-300 topic 2 question 108 discussion

This are the correFirst, you should create one-to-many relationships between the tables. This aligns with best practices for building a star schema — the fact table should link to dimension tables via one-to-many relationships for optimal performance and clarity. Second, in the Transactions query, you should delete the TransactionID column. Since you're not analyzing or filtering based on TransactionID, and it's likely a high-cardinality field, removing it helps minimize model size and improves performance. Third, still within the Transactions query, you should add a new column that contains the MonthStartDate value for the TransactionDate. This helps group transactions by month and prepares your data for efficient time-based analysis, like comparing this year to last year.

I would do in this order E -> D -> A. Add MonthStartDate to Transactions query -> aggregate Transactions query by AccountID and MonthStartDate (TeansactionID will need to be excluded in this step) -> set up one-to-many relationship between Transactions and Account on AccountID column and Transactions and Date on MonthStartDate column.

Selecting D without E, makes no sense as transactions query have no MonthStartDate to aggregate on. But E indeed increase the size of the model.

I believe E is not correct because adding MonthStartDate to the Transactions table would increase the data size, and this information is already available in the Date table.

I'll go for ADE, As with out creating a start month date column we cannot group or aggregate the table: So its: 1) Create Start month date column 2) Group or aggregate 3) create relationships

A B D are the correct answers . E and F go against the requirement .

for me is ADE