PL-300 Model the data Practice Question
Which TWO of the following are valid reasons to use a calculated table instead of a calculated column in Power BI?
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 summary table that is not present in the source.
Option A is correct because a calculated table is created with DAX table expressions (for example, SUMMARIZE, SUMMARIZECOLUMNS, or DISTINCT) and can materialize a new summary table that does not exist in the source system, which is exactly what calculated tables are designed for. Option C is correct because a calculated table can be generated with CALENDAR or CALENDARAUTO to produce a continuous, unbroken date range, which is the standard way to build a dedicated date table for time intelligence functions like TOTALYTD or SAMEPERIODLASTYEAR. Option B is not correct because calculated tables are computed at refresh and stored in the model, so they do not inherently reduce model size by storing only aggregated data; aggregation reduction is achieved through Import mode aggregations, DirectQuery, or composite models, not by the mere choice of a calculated table. Option D is not correct because a column that depends on other columns in the same row is precisely the definition of a calculated column, which is evaluated row by row in the table, whereas a calculated table produces a whole table and cannot serve that row-level purpose.
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 create a summary table that is not present in the source.
Why this is correct
Calculated tables let you use DAX table functions such as SUMMARIZE, GROUPBY, or UNION to build a genuinely new analytical table from existing model data. The result is stored as a physical table in the Data pane, so it can participate in relationships, support measures, and be referenced in reports even when the source system does not contain that exact aggregation. Because it is fully materialized at refresh time, it persists as a reusable, pre-aggregated view.
- ✗
To reduce model size by storing only aggregated data.
Why it's wrong here
Every calculated table, regardless of how few rows it returns, is materialized in the VertiPaq in-memory column store, increasing both model size and RAM consumption. Even an aggregation expressed in DAX is stored as a new table, so you are duplicating rather than reducing data. To actually shrink a model, you would filter or shape data in Power Query, remove unneeded columns and rows, or redesign how data is loaded.
- ✓
To create a date table with a continuous range of dates.
Why this is correct
A calculated table is the recommended way to generate a date dimension covering a continuous range of dates, typically using CALENDAR(DATE(2019,1,1), DATE(2024,12,31)) or CALENDAR AUTO(). Time-intelligence functions such as TOTALYTD and DATESBETWEEN require a contiguous date table with no missing dates, and creating one as a calculated table guarantees that every day from the start to the end date exists regardless of source data gaps. This avoids having to rely on an external calendar table and makes it easy to append calculated columns for year, month, quarter, and relative date filters.
- ✗
To create a column that depends on other columns in the same row.
Why it's wrong here
A calculated column, not a calculated table, is the correct tool when you need a value that depends on other columns in the same row. Calculated columns are added to an existing table and evaluate under row context, so a statement like [SalesAmount] * [ExchangeRate] can reference columns from that same table. A calculated table, on the other hand, creates an entirely new table and cannot be used to simply extend an existing table with a per-row column; using it for such a requirement would be an architectural mismatch and would force you to create a separate table and then join it through a relationship.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-300 question from scratch — 524 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.