The correct approach is to create a one-to-many relationship from Date[FiscalYear] to Sales[FiscalYear], assuming the Sales table already contains a FiscalYear column. This works because the Date table has one row per fiscal year, while the Sales table has many rows per fiscal year, making a standard one-to-many relationship the proper modeling technique to filter sales by fiscal year. On the PL-300 exam, this scenario tests your understanding of star schema design and how to handle fiscal calendars—a common trap is trying to create a relationship directly on the OrderDate column, which would require a daily granularity in the Date table rather than yearly. To implement this, you may need to add a calculated column in the Sales table using DAX like `FiscalYear = "FY" & YEAR(OrderDate) + IF(MONTH(OrderDate) > 6, 1, 0)` if your fiscal year starts in July. Memory tip: think "one year row, many sales rows" to always reach for a one-to-many relationship on the fiscal year key.
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.
You are a Power BI report creator. You have a dataset that includes a date table and a sales table. The date table has a column 'FiscalYear' (e.g., 'FY2025'). The sales table has a column 'OrderDate'. You need to create a relationship between the date table and the sales table based on the fiscal year. However, the date table has one row per fiscal year, and the sales table has multiple rows per fiscal year. You want to filter sales by fiscal year. What is the correct approach to model this?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a one-to-many relationship from Date[FiscalYear] to Sales[FiscalYear] (assuming Sales table has FiscalYear).
Option C is correct because it establishes a standard one-to-many relationship between the Date table (with one row per fiscal year) and the Sales table (with multiple rows per fiscal year) using a common FiscalYear column. This allows Power BI to filter sales by fiscal year through the relationship, leveraging the date table as a filter dimension. The relationship must be based on a column in the Sales table that contains the fiscal year for each order, which can be added as a calculated column if not already present.
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.
✗
Add a calculated column in Sales to extract fiscal year from OrderDate and use that for filtering without a relationship.
Why it's wrong here
No relationship means no filter propagation.
✗
Merge the Date table into the Sales table in Power Query.
Why it's wrong here
Denormalizes the model.
✓
Create a one-to-many relationship from Date[FiscalYear] to Sales[FiscalYear] (assuming Sales table has FiscalYear).
Why this is correct
Standard star schema approach.
Related concept
Read the scenario before looking for a memorised answer.
✗
Create a many-to-many relationship between Date and Sales using a bridge table.
Why it's wrong here
Unnecessarily complex.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think a many-to-many relationship or a bridge table is needed when the date table has one row per fiscal year and the sales table has multiple rows, but the correct modeling approach is a simple one-to-many relationship based on a common fiscal year column in both tables.
Detailed technical explanation
How to think about this question
In Power BI, a one-to-many relationship between a date dimension and a fact table is the foundation of a star schema. The Date table should have a unique FiscalYear column (e.g., 'FY2025') and the Sales table must have a corresponding FiscalYear column with matching values. When you create the relationship, Power BI automatically propagates filters from the Date table to the Sales table, enabling cross-filtering and time intelligence functions like TOTALYTD or SAMEPERIODLASTYEAR. A subtle behavior is that the relationship direction (single vs. both) matters: for fiscal year filtering, a single-direction filter (from Date to Sales) is sufficient and recommended to avoid ambiguity.
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 one-to-many relationship from Date[FiscalYear] to Sales[FiscalYear] (assuming Sales table has FiscalYear). — Option C is correct because it establishes a standard one-to-many relationship between the Date table (with one row per fiscal year) and the Sales table (with multiple rows per fiscal year) using a common FiscalYear column. This allows Power BI to filter sales by fiscal year through the relationship, leveraging the date table as a filter dimension. The relationship must be based on a column in the Sales table that contains the fiscal year for each order, which can be added as a calculated column if not already present.
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.
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.