In a star schema, which table acts as the main table that connects to all other tables?
Think about which table holds the measurable data like sales or quantities.
The fact table is the central table in a star schema. It contains the numeric data and keys that link to dimension tables.
What type of relationship typically exists between the fact table and each dimension table in a star schema?
Consider which table has unique keys and which has repeated keys.
Dimension tables have unique keys and connect to many rows in the fact table, so the relationship is one-to-many from dimension to fact.
Given a star schema with a fact table 'Sales' and a dimension table 'Product' with a 'Category' column, which DAX measure correctly calculates total sales amount by product category?
Total Sales by Category = CALCULATE(SUM(Sales[Amount]), ALLEXCEPT(Product, Product[Category]))
Think about keeping the filter on category while removing other filters.
Option A uses ALLEXCEPT to keep the filter on Product[Category] while summing sales amount, correctly calculating total sales by category.
You have sales data in a star schema with dimensions for Product, Date, and Store. Which visualization best shows total sales trends over time by product category?
Think about showing changes over time and comparing categories.
A stacked area chart with Date on the X-axis and sales stacked by product category clearly shows trends over time and category comparisons.
You created relationships in Power BI star schema: fact table 'Sales' linked to 'Product' dimension on ProductID, and to 'Date' dimension on DateKey. But your sales by product report shows incorrect totals. What is the most likely cause?
Check uniqueness of keys in dimension tables.
Duplicate keys in the Product dimension break the one-to-many relationship, causing incorrect aggregation in reports.