Composite models in Power BI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable DirectQuery mode in a composite model.

Power BI

Model.EnableCompositeMode([1])

Drag options to blanks, or click blank then click option'

Aenable

Bfalse

Ctrue

Ddisable

Attempts:

3 left

💡 Hint

Common Mistakes

Using string values instead of boolean

Confusing enable/disable keywords

Setting true enables DirectQuery mode in the composite model.

2fill in blank

medium

Complete the DAX expression to create a calculated table combining DirectQuery and Import data.

Power BI

CombinedTable = UNION(ImportTable, [1])

Drag options to blanks, or click blank then click option'

ADirectQueryTable

BSUMMARIZE(ImportTable)

CFILTER(DirectQueryTable, TRUE())

DVALUES(ImportTable)

Attempts:

3 left

💡 Hint

Common Mistakes

Using aggregation functions instead of table names

Filtering unnecessarily

The UNION function combines rows from ImportTable and DirectQueryTable.

3fill in blank

hard

Fix the error in the DAX measure to calculate sales from both Import and DirectQuery tables.

Power BI

TotalSales = SUM(ImportSales[Amount]) + [1]

Drag options to blanks, or click blank then click option'

ASUM(ImportSales[Amount])

BCALCULATE(SUM(DirectSales[Amount]))

CSUMX(DirectSales, Amount)

DSUM(DirectSales[Amount])

Attempts:

3 left

💡 Hint

Common Mistakes

Using CALCULATE unnecessarily

Summing the wrong table

Duplicating ImportSales sum

Use SUM(DirectSales[Amount]) to add sales from the DirectQuery table correctly.

4fill in blank

hard

Fill both blanks to create a relationship between Import and DirectQuery tables.

Power BI

CREATE RELATIONSHIP [1] ON [2]

Drag options to blanks, or click blank then click option'

AImportTable[CustomerID] = DirectQueryTable[CustomerID]

BImportTable[Date] = DirectQueryTable[Date]

CDirectQueryTable[CustomerID]

DImportTable[CustomerID]

Attempts:

3 left

💡 Hint

Common Mistakes

Using only one side of the relationship

Mixing columns from different tables incorrectly

The relationship is created by matching CustomerID columns from both tables.

5fill in blank

hard

Fill all three blanks to write a DAX measure that filters Import data by DirectQuery date range.

Power BI

FilteredSales = CALCULATE(SUM(ImportSales[Amount]), ImportSales[Date] [1] DirectQueryDates[StartDate], ImportSales[Date] [2] DirectQueryDates[EndDate], [3])

Drag options to blanks, or click blank then click option'

A>=

B<=

CALL(ImportSales)

DFILTER(ImportSales, TRUE())

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong comparison operators

Not clearing filters properly

Using FILTER unnecessarily

The measure filters ImportSales dates between DirectQueryDates start and end dates, removing other filters with ALL.

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