PL-300 Prepare the data Practice Question
You are preparing a data model that uses a date table. You need to ensure that the date table includes all dates from January 1, 2020 to December 31, 2025. What is the most efficient way to create this date table in Power Query?
⚠ Common exam trap
It's easy for candidates to confuse DAX functions (like 'CALENDAR') with Power Query M functions, assuming they can be used interchangeably in the Power Query editor, when in fact DAX functions are only available in the data modeling layer (e.g., calculated tables) and not in Power Query.
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
✓
Use the 'List.Dates' function to generate the date range.
The 'List.Dates' function in Power Query M is the most efficient way to generate a contiguous range of dates directly within the query editor, without external dependencies. It creates a list of dates from a start date to an end date using a specified step (e.g., #duration(1,0,0,0) for one day), which can then be converted into a table. This approach is lightweight, fully self-contained, and avoids the overhead of importing external files or using DAX functions that are not native to Power Query.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Import a date table from an Excel file.
Why it's wrong here
Importing a date table from an Excel file is technically possible, but it is a static, manual solution that requires refreshing the Excel source whenever new dates are needed and creates a dependency on maintaining that external file. This approach also risks gaps in the date range and reduces the automation and flexibility expected in a Power Query-driven data model, making it inefficient compared to generating dates natively.
- ✓
Use the 'List.Dates' function to generate the date range.
Why this is correct
Using the 'List.Dates' function in Power Query M is the correct approach because it dynamically generates a continuous list of dates from a specified start date, a count of dates, and a step increment, all defined as parameters. You then wrap that list with Table.FromList or convert it into a column, allowing you to create a date table that automatically adapts to your data range without manual maintenance or external file dependencies.
- ✗
Use the 'Calendar' function in Power Query M.
Why it's wrong here
There is no 'Calendar' function in Power Query M, so this option is incorrect because it confuses a DAX function name with M functions. While DAX has CALENDAR and CALENDARAUTO, M relies on List.Dates, List.Generate, or other list generators to produce a calendar table; attempting to call a nonexistent 'Calendar' function in M will result in an expression error.
- ✗
Use the 'CALENDAR' DAX function in Power Query.
Why it's wrong here
The CALENDAR function is a DAX function, not an M function, so it is unavailable in Power Query. This option is wrong because Power Query's language is M, and DAX functions can only be used in calculated tables or measures within the data model, not in the query editor; you would need to leave Power Query and create the date table using DAX in the model instead.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-300 question from scratch — 217 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.