Which Components Can You Add to a Live-Connection Power BI Report?

PL-300 By islever Editorial Last updated

Create reports Create model calculations by using DAX

Short answer

ABC In RPT1's live connection to the Power BI semantic model, add report measures, calculated columns, and calculated tables, not new model columns or tables.

Question

You have a semantic model that uses a live connection to a semantic model in the Power BI service.
You need to create a Power BI report named RPT1 that only uses the live connection.
Which three components can you add to RPT1? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
  1. a report measure Correct Answer
  2. a calculated column Correct Answer
  3. a calculated table Correct Answer
  4. a new column
  5. a new table

Key Takeaways

The question tests live-connection scope: report-level DAX objects are allowed, while schema changes to the shared Power BI semantic model are not; the trap is assuming only a report measure is permitted.

A Power BI report using only a live connection to a Power BI semantic model can add report measures, calculated columns, and calculated tables without importing data or editing the source model. This page confirms A, B, and C and explains why new columns and new tables are blocked.

Common mistake: Many learners select only A because they treat every calculated column or table as a model change; the exam distinguishes allowed report-level calculations from adding a new column or new table to the source semantic model.

Expert Analysis

Why the Answer Is Correct

In a report that is connected live to a Power BI semantic model, the shared model is read-only, so RPT1 cannot add physical schema objects to it. The exam's allowed report-level additions are a report measure, a calculated column, and a calculated table: these are DAX calculations that belong to the report authoring layer rather than new source-model columns or tables. That makes A, B, and C the three components that satisfy the live-connection constraint. The key is the distinction the question draws between calculated objects and new model columns/tables.

Why the Other Options Are Wrong

A new column (D) would add a column to the shared semantic model, and a new table (E) would add a table to that model; both are schema changes that a live connection cannot perform. They are not report-level calculations, so they fail the only-uses-the-live-connection requirement. This is why D and E are excluded even though they look similar to calculated columns and calculated tables.

Community Comment Notes

Idaresit correctly observes that the live-connected model is locked and that schema changes are blocked, but reads that as allowing only a report measure; the question's three-component wording points to the broader report-level calculation set. malpa.kokos cites documentation that live connection mode blocks new columns and tables while allowing report measures, calculated columns, and calculated tables, which aligns with A, B, C. Sana92's position that only report measures are allowed is the common over-restriction trap: it conflates calculated columns and calculated tables with new model columns and tables.

Exam Strategy

Read live connection as a read-only shared model: eliminate any option that adds a physical column or table to the source semantic model. Then map the remaining DAX objects to report-level calculations and select all three, not just the report measure.

Frequently Asked Questions

Why can RPT1 add calculated columns and calculated tables in a live connection?

The exam treats them as report-level DAX calculations that do not add a new source-model column or table. RPT1 can use them while the shared Power BI semantic model remains unchanged.

Why are a new column and a new table not allowed in RPT1?

Adding a new column or table would change the schema of the live-connected semantic model, which is read-only in this scenario. Only report-level calculations are permitted.

More PL-300 FAQ →

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. Idaresit 👍 2 Answered A
    When you connect live to a dataset in the Power BI service, the model is locked. You cannot change its structure. That means you cannot create anything that modifies the model schema (tables or columns inside the dataset). However, I do not understand if I will be penalized for making only one selection.
  2. Sana92 👍 1 Answered A
    The truth: When you connect to a semantic model using a live connection, you cannot add: calculated columns calculated tables new columns new tables You can only add: report measures That’s it. This is not optional, not version‑dependent, not “chained composite,” not “derived vs new.” It’s a hard architectural rule.
  3. malpa.kokos 👍 1
    From documentation: "In live connection mode, you can't modify the data model itself (for example, you can't add new columns or tables). You can only create measures (Report Measures), calculated columns, visual calculations, and calculated tables."

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

PREVIOUSYEAR returns the full previous year, not the same day of last year

S-grade

Shrinking a Power BI model for monthly transaction totals with a star schema

S-grade

Northwind Traders semantic model: choosing Import storage mode for the Power BI tables

S-grade

Connecting Power BI Desktop to Azure DevOps Analytics views with the OData Feed connector

S-grade

Practice All PL-300 Questions

Access 116 questions with complete answers and detailed explanations.

View Full PL-300 Practice Test →

← Back to PL-300 Study Guide