Forum Discussion

amaaiia's avatar
amaaiia
Skilled Sharer
1 year ago
Solved

Help with Fabric certification question

A colleague took the Fabric Certification exam and came up with a question that he found confusing to understand. I put it to you:   You have a CSV with the following data: - SalesTransactionID -...
  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi amaaiia,

     

    Thank you for reaching out to the Microsoft fabric community forum regarding your implementation of a star schema for sales transaction analysis. 

     

    Based on the data provided in your CSV, here’s an overview of how we can categorize each of the fields:

    • CustomerCode uniquely identifies each customer and links related data in your star schema. Store this in your Customers dimension table.
    • The CustomerName field provides descriptive information about customers. Although it does not uniquely identify them like the CustomerCode, it offers valuable context. This field will also be included in your Customers dimension table.
    • The date of each sales transaction is vital for time-based analysis, allowing you to track sales trends over various time periods. In a well-structured data warehouse, it's common to create a dedicated date dimension; however, it can also be part of the fact table for some basic analyses.

    Your approach to implementing the schema seems correct, and the answers for the question align with best practices for star schema design.


    If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.

     

    Thank you.