PL-300 Prepare the data Practice Question
You have a table with a column 'Date' in text format (e.g., '2024-01-15'). You need to convert it to a date type. In Power Query, what is the best approach?
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
✓
Change the column data type to Date in Power Query Editor.
Power Query's Change Type > Date (or the Date.From/Table.TransformColumnTypes operation) natively parses ISO-formatted text like '2024-01-15' into a true date type using the locale's date-parsing rules, which is the intended, one-step approach for this scenario. Splitting into year, month, and day (A) is unnecessary and error-prone when the text is already in a recognizable date format. Using the Excel Power Query add-in (B) is irrelevant since Power Query is already the tool in use, and creating a DAX calculated column with DATEVALUE (C) works in the data model rather than transforming the column at query time, which is less efficient and doesn't change the underlying column type.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Split the column into year, month, day and then combine.
Why it's wrong here
Splitting the column into year, month, and day components is an unnecessarily convoluted approach; while it can work, it requires writing custom logic to detect the separator and pad values, and then recombining them with DATE or a similar function. This manual parsing is prone to error with varying formats (e.g., 'MM/dd/yyyy' vs 'dd-MM-yyyy') and locale differences, whereas changing the data type to Date in the Power Query Editor uses the built-in parser, which already handles these cases automatically. It also adds multiple transformation steps that complicate your query rather than solving the problem in one direct action.
- ✗
Use the Excel Power Query add-in.
Why it's wrong here
This option is invalid because Power Query is fully integrated into Power BI Desktop as its native data transformation environment; there is no separate 'Excel Power Query add-in' for Power BI, and even if you were thinking of the Excel add-in, it is irrelevant to a Power BI solution. In Power BI Desktop, you access Power Query via the 'Transform Data' button, which opens the Power Query Editor where you can directly change the column data type. Invoking an external add-in would be unnecessary, unsupported, and inefficient for a task that is a single built-in step.
- ✗
Create a calculated column in DAX using DATEVALUE.
Why it's wrong here
Calculated columns in DAX are executed in the analysis services engine after the data has been loaded into the model, not during the extraction/transformation phase; therefore, using DATEVALUE in a calculated column addresses the symptom after the fact, and it would still leave the column as text in the data model unless you also change the data type of the new column. Moreover, DATEVALUE is locale-sensitive and might fail on dates like '31/12/2023' in certain contexts. The correct action is to fix the column during transformation using Power Query's 'Change Type' feature, which ensures the data is correctly typed before it ever enters the model.
- ✓
Change the column data type to Date in Power Query Editor.
Why this is correct
Changing the column data type to Date in the Power Query Editor is the correct and most efficient approach because it leverages Power Query's built-in type conversion system, which parses the text representation into a true date value using the designated locale and format. To do this, you select the column, go to the Transform tab (or Home tab), and choose Data Type > Date; Power Query automatically inserts a 'Changed Type' step that records this transformation. This method is straightforward, requires no custom code, and ensures the data is correctly typed for all downstream operations like modeling, DAX calculations, and visual date hierarchies.
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.