HOTSPOT You are creating a Microsoft Power BI imported data model to perform basket analysis. The goal of the analysis is to identify which products are usually bought together in the same transaction across and within sales territories. You import a fact table named Sales as shown in the exhibit. (Click the Exhibit tab.) *(refer to diagram in explanation below)* The related dimension tables are imported into the model. Sales contains the data shown in the following table (detailed in explanation below): You are evaluating how to optimize the model. For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point.
Interactive Drag & Drop Matching
Drag each configuration to its target, or tap an option then tap a target slot.
Available Configurations3 remaining
Both the OrderDateKey and OrderDate columns are necessary to perform the basket analysis: No Reas...
The SalesRowID and AuditID columns can be removed from the model without impeding the analysis go...
The TaxAmt column must retain the current number of decimal places to perform the basket analysis...
Targets & Placement
1Scenario 1
Drop configuration here
2Scenario 2
Drop configuration here
3Scenario 3
Drop configuration here
Explanation
Hotspot Solution:
Recommended Community Solution:
The SalesRowID and AuditID columns can be removed from the model without impeding the analysis goals: Yes Reason: These are technical/audit columns, not needed for basket analysis. Removing them reduces model size and improves performance. - 2. Both the OrderDateKey and OrderDate columns are necessary to perform the basket analysis: No Reason: You only need one date column for relationships (typically OrderDateKey as an integer key for the Date dimension). OrderDate (full datetime) is redundant unless required for reporting granularity beyond the date table. - 3. The TaxAmt column must retain the current number of decimal places to perform the basket analysis: No Reason: Basket analysis focuses on co-occurrence of products, not precise tax amounts. You can even remove TaxAmt if not used in reporting. Decimal precision is irrelevant for the analysis goal.
Community Discussion
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
3
- 1. The SalesRowID and AuditID columns can be removed from the model without impeding the analysis goals: Yes Reason: These are technical/audit columns, not needed for basket analysis. Removing them reduces model size and improves performance. - 2. Both the OrderDateKey and OrderDate columns are necessary to perform the basket analysis: No Reason: You only need one date column for relationships (typically OrderDateKey as an integer key for the Date dimension). OrderDate (full datetime) is redundant unless required for reporting granularity beyond the date table. - 3. The TaxAmt column must retain the current number of decimal places to perform the basket analysis: No Reason: Basket analysis focuses on co-occurrence of products, not precise tax amounts. You can even remove TaxAmt if not used in reporting. Decimal precision is irrelevant for the analysis goal.
1
Yes-No-No The SalesOrderNumber can be used to identify the sales order so the salesrowid can be removed.
1
Final Answers: SalesRowID and AuditID can be removed? → Yes Both OrderDateKey and OrderDate needed? → No TaxAmt must retain decimal precision? → No
