When to Create a Calculated Table: Date Tables, Bridge Tables, and What-If Analysis
Which THREE of the following are valid reasons to create a calculated table in Power BI?
Quick Answer
The answer is to create a summary table that pre-aggregates data for better performance, along with generating a date table and building a bridge table for many-to-many relationships. These are valid reasons because calculated tables are stored in memory via DAX, allowing you to enforce a continuous date range for time intelligence functions like TOTALYTD, or to pre-join and summarize data to reduce query load on the underlying source. On the PL-300 exam, this topic tests your understanding of when to use calculated tables versus measures or calculated columns—a common trap is thinking you need a calculated table for simple row-level calculations, which should instead be a column. Remember the three core use cases: date tables for time intelligence, bridge tables for complex relationships, and what-if tables for parameter-driven analysis. A helpful memory tip is “DBW”—Date, Bridge, What-if—to recall the three valid reasons when you see this question on the exam.
⚠ Common exam trap
Test-takers frequently confuse calculated tables with calculated columns or Power Query merges, thinking any table-like operation qualifies, but Power BI strictly distinguishes between row-level calculations (calculated columns) and table-level transformations (calculated tables).
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
To create a date table that is not available in the data source.
Calculated tables in Power BI are created using DAX and stored in memory, allowing you to generate a date table when no suitable date table exists in the data source. This is a common pattern to ensure a complete date range for time intelligence functions, as Power BI requires a continuous date table for functions like TOTALYTD or SAMEPERIODLASTYEAR.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
To add a column that computes a value based on other columns in the same table.
Why it's wrong here
A calculated column (not table) is used for row-level computations within a table.
- ✗
To combine two tables by merging columns from one table into another.
Why it's wrong here
Merging tables should be done in Power Query to avoid performance issues.
- ✓
To create a date table that is not available in the data source.
Why this is correct
CALENDAR or CALENDARAUTO can create a date table for time intelligence.
- ✓
To create a disconnected table for use in what-if analysis (e.g., parameter slicers).
Why this is correct
A disconnected table can be used with measures to simulate parameter selection.
- ✓
To create a summary table that pre-aggregates data for better performance.
Why this is correct
Pre-aggregating data in a calculated table can improve report performance for large datasets.
Go deeper
Related to this question
About these practice questions
This PL-300 question is part of Courseiva's 217-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
4 more ways this is tested on PL-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which THREE of the following are valid reasons to create a calculated table in Power BI?
hard- A.Replace incremental refresh
- ✓ B.Create a summary table that aggregates data from another table
- C.Modify the source data before loading
- ✓ D.Create a crossjoin of two dimension tables
- ✓ E.Create a date table that is not available in the source
Why B: Options B, D, and E are correct. Calculated tables can be used to create summary tables via aggregation (B), to create crossjoins of dimension tables (D), and to generate a date table not present in the source data (E). Option A is incorrect because incremental refresh is a data loading feature, not something a calculated table can replace; calculated tables are static and refreshed along with the model. Option C is incorrect because calculated tables are derived from data already loaded; they cannot modify source data before loading.
Variation 2. Which TWO DAX functions can be used to create a calculated table in Power BI?
medium- A.SELECTEDVALUE
- ✓ B.FILTER
- C.CALCULATE
- ✓ D.SUMMARIZECOLUMNS
- E.SUMX
Why B: Options B and D are correct. FILTER returns a table filtered by a condition, and SUMMARIZECOLUMNS returns a summarized table. Options A, C, and E are wrong because SELECTEDVALUE, CALCULATE, and SUMX all return scalar values, not tables.
Variation 3. Which TWO of the following are valid DAX functions for creating a calculated table?
easy- A.SUM
- B.COUNT
- ✓ C.FILTER
- ✓ D.CALENDAR
- E.SELECTEDVALUE
Why C: Options C and D are correct. FILTER returns a table. CALENDAR returns a table. Option A is wrong because SUM returns a scalar. Option B is wrong because COUNT returns a scalar. Option E is wrong because SELECTEDVALUE returns a scalar.
Variation 4. Which TWO of the following are valid reasons to use a calculated table in Power BI instead of a table from the source?
medium- ✓ A.To create a bridge table for many-to-many relationships
- B.To aggregate data from the source before loading
- ✓ C.To create a date table for time intelligence
- D.To enable incremental data refresh
- E.To reduce the overall storage size of the model
Why A: Options A and C are correct. A calculated table can be used to create a bridge table for resolving many-to-many relationships between tables. It can also be used to create a date table for time intelligence functions, which requires a continuous date range not necessarily present in the source. Option B is incorrect because aggregated data from the source is better handled with Power Query transformations that push computations to the source. Option D is incorrect because calculated tables are fully recalculated on each refresh and do not support incremental refresh. Option E is incorrect because calculated tables increase model size by storing additional data in memory.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-300 exam.