Composite models in Power BI - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Composite Models in Power BI

Which statement best describes a composite model in Power BI?

A A model that duplicates data across multiple tables to speed up queries.

B A model that only uses Import mode for all data sources to improve performance.

C A model that uses only DirectQuery mode to ensure real-time data access.

D A model that combines data from both DirectQuery and Import storage modes in a single report.

💡 Hint

Think about how Power BI can mix data storage modes.

Composite models allow combining DirectQuery and Import modes in one model, enabling flexibility and performance optimization.

❓ dax_lod_result

intermediate

DAX Measure with Composite Model Behavior

Given a composite model with a DirectQuery table 'Sales' and an Import table 'Products', what is the result of this DAX measure?

Measure = CALCULATE(SUM(Sales[Amount]), Products[Category] = "Electronics")

Assuming 'Products' is imported and 'Sales' is DirectQuery, what does this measure do?

A Calculates the sum of Sales Amount filtered by Electronics category from the imported Products table.

B Returns an error because you cannot filter DirectQuery data by an Import table column.

C Ignores the filter on Products and sums all Sales Amount.

D Calculates the sum of Sales Amount but only for categories present in the Sales table.

💡 Hint

Consider how relationships work between Import and DirectQuery tables in composite models.

In composite models, filters from Import tables can be applied to DirectQuery tables if relationships exist, so the measure sums Sales Amount filtered by Electronics category.

❓ visualization

advanced

Visualizing Performance Impact of Composite Models

You have a composite model mixing large DirectQuery sales data and small imported product data. Which visualization approach best helps identify performance bottlenecks?

A Add a card visual displaying total sales amount only.

B Create a report page with a table showing query durations and data source types for each visual.

C Build a line chart showing sales trends over time without any query diagnostics.

D Use a pie chart to show sales distribution by product category without performance metrics.

💡 Hint

Think about what helps diagnose performance issues in composite models.

A table showing query durations and data source types helps identify which visuals or queries cause slowdowns in composite models.

🔧 Formula Fix

advanced

Debugging Relationship Issues in Composite Models

You created a composite model with an Import table 'Customers' and a DirectQuery table 'Orders'. The relationship between them is inactive, causing incorrect sales totals. Which DAX expression activates the relationship temporarily to fix the measure?

Measure = ?

A SUMX(Orders, Orders[Amount]) + RELATED(Customers[CustomerID])

B CALCULATE(SUM(Orders[Amount]), ALL(Customers))

C CALCULATE(SUM(Orders[Amount]), USERELATIONSHIP(Customers[CustomerID], Orders[CustomerID]))

D SUM(Orders[Amount]) * COUNTROWS(Customers)

💡 Hint

Recall how to activate inactive relationships in DAX.

USERELATIONSHIP activates an inactive relationship temporarily within CALCULATE, fixing filtering issues in composite models.

🎯 Scenario

expert

Designing a Composite Model for Mixed Data Sources

Your company wants a Power BI report combining real-time sales data from a DirectQuery SQL database and historical sales data imported monthly. You also want to filter by product categories from an imported table. Which design approach best fits this scenario?

A Create a composite model with DirectQuery for real-time sales, Import for historical sales and products, and define relationships between tables.

B Import all data including real-time sales to ensure fast report performance.

C Use DirectQuery for all tables to keep data always current, ignoring import mode.

D Create separate reports for real-time and historical data without combining them.

💡 Hint

Consider how composite models allow mixing storage modes for best performance and freshness.

Composite models enable mixing DirectQuery for real-time data and Import for historical and dimension tables, allowing filtering and performance balance.

Practice

1.

What is the main benefit of using composite models in Power BI?

easy

A. They only work with Import mode data.

B. They allow combining data from multiple sources in one report.

C. They automatically clean data without user input.

D. They replace the need for relationships between tables.

Solution

1. Step 1: Understand composite models purpose

   Composite models let you combine data from different sources in one Power BI report.

2. Step 2: Compare options

   Only 'They allow combining data from multiple sources in one report.' correctly states this benefit; others are incorrect or unrelated.

3. Final Answer:

   They allow combining data from multiple sources in one report. -> Option B

4. Quick Check:

   Composite models = combine multiple sources [OK]

Hint: Composite models = mix data sources in one report [OK]

Common Mistakes:

• Thinking composite models only work with Import mode
• Believing composite models clean data automatically
• Assuming relationships are not needed in composite models

2.

Which of the following is the correct way to enable composite models in Power BI?

Options > Preview Features > Enable Composite Models

easy

A. Enable Composite Models under Options > Preview Features

B. Enable Composite Models under File > Export

C. Enable Composite Models under Home > Transform Data

D. Enable Composite Models under View > Themes

Solution

1. Step 1: Locate composite models setting

   Composite models are enabled via Options > Preview Features in Power BI Desktop.

2. Step 2: Verify other options

   Other options do not contain this setting, so only Enable Composite Models under Options > Preview Features is correct.

3. Final Answer:

   Enable Composite Models under Options > Preview Features -> Option A

4. Quick Check:

   Composite models setting = Options > Preview Features [OK]

Hint: Check Preview Features in Options for composite models [OK]

Common Mistakes:

• Looking for composite models in Export or Themes menus
• Confusing data transformation with enabling composite models
• Assuming composite models are enabled by default

3.

Given a composite model with two tables: Sales (Import mode) and Customers (DirectQuery mode), what happens when you create a relationship between them?

medium

A. The relationship only works if both tables are in Import mode.

B. Power BI throws an error because relationships cannot connect Import and DirectQuery tables.

C. The relationship works but disables DirectQuery mode for the Customers table.

D. Power BI allows cross-source relationships, enabling combined filtering and analysis.

Solution

1. Step 1: Understand composite model relationships

   Composite models allow relationships between Import and DirectQuery tables.

2. Step 2: Analyze options

   Only 'Power BI allows cross-source relationships, enabling combined filtering and analysis.' correctly states what happens; others are false.

3. Final Answer:

   Power BI allows cross-source relationships, enabling combined filtering and analysis. -> Option D

4. Quick Check:

   Composite models = cross-source relationships allowed [OK]

Hint: Composite models support relationships across Import and DirectQuery [OK]

Common Mistakes:

• Believing relationships cannot connect different storage modes
• Thinking DirectQuery tables lose their mode when related
• Assuming relationships only work within same storage mode

4.

You created a composite model with Import and DirectQuery tables but get an error when trying to build a relationship. What is a likely cause?

medium

A. The composite models feature is not enabled in Preview Features.

B. You used the wrong DAX syntax for the relationship.

C. Power BI does not support relationships between tables.

D. The data sources are from the same database.

Solution

1. Step 1: Check composite models feature status

   If composite models are not enabled in Preview Features, relationships between Import and DirectQuery tables cause errors.

2. Step 2: Evaluate other options

   DAX syntax is not used to create relationships; Power BI supports relationships; same database does not cause errors.

3. Final Answer:

   The composite models feature is not enabled in Preview Features. -> Option A

4. Quick Check:

   Enable composite models to allow cross-source relationships [OK]

Hint: Enable composite models in Preview Features to avoid relationship errors [OK]

Common Mistakes:

• Trying to fix relationships with DAX syntax
• Assuming relationships are unsupported in Power BI
• Thinking same database causes relationship errors

5.

You have a composite model with three tables: Orders (Import), Products (DirectQuery), and Customers (Import). You want to create a report showing total sales by product category and customer region. Which approach is best?

hard

A. Use only the Orders table and ignore others to simplify the report.

B. Import all tables to avoid composite models and relationships.

C. Create relationships between all tables, use DirectQuery for Products, and build visuals combining all data.

D. Create separate reports for each table and combine them outside Power BI.

Solution

1. Step 1: Understand composite model usage

   Composite models allow mixing Import and DirectQuery tables with relationships for combined analysis.

2. Step 2: Apply to scenario

   Creating relationships between all tables and using DirectQuery for Products enables combined sales by product category and customer region.

3. Step 3: Evaluate other options

   Importing all tables may not be possible; ignoring tables loses insights; separate reports reduce integration.

4. Final Answer:

   Create relationships between all tables, use DirectQuery for Products, and build visuals combining all data. -> Option C

5. Quick Check:

   Composite models + relationships = combined report [OK]

Hint: Use relationships to combine Import and DirectQuery tables in one report [OK]

Common Mistakes:

• Trying to avoid composite models by importing all data
• Ignoring important tables for simplicity
• Splitting data into separate reports unnecessarily