The answer is to create a separate date table in Power Query with a fiscal year column. This is the correct approach because it establishes a dedicated date dimension independent of your fact tables, adhering to star schema best practices in Power BI. By defining the fiscal year logic—starting April 1—directly in M code during data preparation, you ensure the transformation is efficient, repeatable, and maintainable, rather than relying on DAX calculated columns or tables that can degrade performance. On the PL-300 exam, this scenario tests your understanding of dimensional modeling and the distinction between data preparation (Power Query) and data modeling (DAX). A common trap is to add a fiscal year calculated column to the fact table, which violates star schema principles and creates redundancy. Instead, remember the memory tip: “Date tables are built in Query, not in DAX—prepare the year, don’t calculate it.”
PL-300 Prepare the data Practice Question
This PL-300 practice question tests your understanding of prepare the data. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A Power BI report contains a table with a column 'Date' of type date. The report users need to filter data by fiscal year, which starts on April 1. What is the best practice to support this requirement during data preparation?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a separate date table in Power Query with a fiscal year column.
Option A is correct because creating a separate date table in Power Query with a fiscal year column is the best practice for handling fiscal year filtering. This approach ensures the date dimension is independent of fact tables, supports star schema design, and allows you to define fiscal year logic (starting April 1) directly in M code during data preparation, which is more efficient and maintainable than using DAX calculated columns or tables.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Create a separate date table in Power Query with a fiscal year column.
Why this is correct
A dedicated date table is the recommended approach.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Split the date column into year, month, and day columns.
Why it's wrong here
Splitting does not create fiscal year logic.
✗
Use a DAX calculated table to generate fiscal year dates.
Why it's wrong here
DAX calculated tables are less performant for large data.
✗
Add a calculated column in the existing table using DAX.
Why it's wrong here
Calculated columns increase model size and refresh time.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think a DAX calculated column or table is acceptable for fiscal year logic, but the exam emphasizes that data preparation (Power Query) is the correct phase for such transformations to maintain performance and star schema design.
Detailed technical explanation
How to think about this question
In Power Query (M language), you can create a fiscal year column using a conditional statement like `if Date.Month([Date]) >= 4 then Date.Year([Date]) else Date.Year([Date]) - 1`, which is evaluated during data load and stored in the model. A separate date table also enables use of the 'Mark as Date Table' feature in Power BI, which automatically enables time intelligence functions like TOTALYTD with custom fiscal year end dates, ensuring consistent filtering across all visuals.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Prepare the data — This question tests Prepare the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a separate date table in Power Query with a fiscal year column. — Option A is correct because creating a separate date table in Power Query with a fiscal year column is the best practice for handling fiscal year filtering. This approach ensures the date dimension is independent of fact tables, supports star schema design, and allows you to define fiscal year logic (starting April 1) directly in M code during data preparation, which is more efficient and maintainable than using DAX calculated columns or tables.
What should I do if I get this PL-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.