Exam DP-600 Topic 2 Question 29 Discussion
Actual exam question for Microsoft's DP-600 exam
Question #: 29
Topic #: 2
Question #: 29
Topic #: 2
You have a Fabric tenant that contains a semantic model named model1. The two largest columns in model1 are shown in the following table.

You need to optimize model 1. The solution must meet the following requirements:
* Reduce the model size.
* Increase refresh performance when using Import mode.
* Ensure that the datetime value for each sales transaction is available in the model.
What should you do on each column? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.


You need to optimize model 1. The solution must meet the following requirements:
* Reduce the model size.
* Increase refresh performance when using Import mode.
* Ensure that the datetime value for each sales transaction is available in the model.
What should you do on each column? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Suggested Answer:

Explanation:

We are optimizing model1 in Fabric with two very large columns:
TransactionKey
Cardinality: 2.5 billion
Size: 160 GB
Description: surrogate key for SalesTransaction fact table.
SaleDateTime
Cardinality: 6.8 million
Size: 120 GB
Description: datetime (to the second) of when a sale occurred.
Goal:
Reduce model size.
Improve refresh performance (Import mode).
Ensure datetime values remain available.
Analysis per column
1. TransactionKey (very high cardinality)
Surrogate keys with extremely high cardinality do not add analytical value in a semantic model because they are not used in measures or grouping.
They take a lot of memory and reduce refresh performance.
Best practice: remove the column from the model.
2. SaleDateTime
Needed to analyze transactions by date and time.
However, storing the full datetime at second-level cardinality causes huge memory usage.
To optimize: split the column into Date and Time columns.
Reduces cardinality significantly.
Preserves full datetime information (can recombine if needed).
Improves compression and refresh speed.
Final Answer:
TransactionKey: Remove the column.
SaleDateTime: Split the column.
References:
Microsoft Fabric optimization guidance - reduce cardinality
Best practices for datetime optimization in semantic models
# Answer Selection:
TransactionKey # Remove the column
SaleDateTime # Split the column
by Harry at Jun 12, 2026, 12:28 AM
0
0
0
10
Comments
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.
Report Comment
Commenting
You can sign-up / login (it's free).