- A
Use a single date dimension table and keep only one active relationship (e.g., to OrderDate). For other dates, create measures that filter the date table using CALCULATE and FILTER.
This is the recommended approach: keep one active relationship (e.g., to OrderDate) and use USERELATIONSHIP in DAX to activate the inactive relationships for ShipDate and DueDate when needed.
- B
Create a separate date dimension table for each date column in the Sales table and relate each to the fact table.
Why wrong: This is not recommended because it leads to multiple date tables, which is inefficient and can cause confusion.
- C
Use a single date dimension table and create multiple active relationships using bridging tables or by duplicating the dimension table for each role.
Why wrong: Actually, you cannot have multiple active relationships between the same two tables in Power BI; you need either inactive relationships or separate dimension tables. So this is not feasible as stated.
- D
Use a single date dimension table and create inactive relationships for ShipDate and DueDate. Use USERELATIONSHIP in DAX measures.
Why wrong: This is partially correct but incomplete; you should create active relationships for commonly filtered dates, and use USERELATIONSHIP for others. However, the best practice is to have only one active relationship per pair of tables, and the other dates are inactive.
Quick Answer
The recommended approach is to use a single date dimension table and keep only one active relationship (e.g., to OrderDate), then create measures for other dates using CALCULATE with FILTER or USERELATIONSHIP. This is correct because it follows star schema best practices, avoiding table duplication while allowing multiple date columns to reference one date dimension through role-playing relationships. On the PL-300 exam, this tests your understanding of modeling multiple date columns with a single date dimension, a common scenario where candidates mistakenly create separate date tables for each column. The trap is thinking you need multiple date tables; instead, Power BI’s model handles this elegantly with inactive relationships activated via DAX. For fiscal year analysis, add a calculated column in the date table for the fiscal period. Memory tip: “One table, many roles—activate with CALCULATE to reach your goals.”
PL-300 Model the data Practice Question
This PL-300 practice question tests your understanding of model 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 company has a large fact table with sales data. The Sales table contains columns: OrderDate, ShipDate, DueDate, LineTotal, ProductKey, CustomerKey, TerritoryKey. The company needs to analyze sales by fiscal year (April 1 to March 31) and by calendar year. What is the recommended approach to model the date dimension?
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 a single date dimension table and keep only one active relationship (e.g., to OrderDate). For other dates, create measures that filter the date table using CALCULATE and FILTER.
Option A is correct because it uses a single date dimension table with one active relationship (typically to OrderDate) and leverages CALCULATE with FILTER or USERELATIONSHIP for other date roles. This is the recommended star schema design in Power BI, as it avoids unnecessary table duplication and maintains model simplicity while supporting fiscal year analysis via a calculated column in the date table.
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.
- ✓
Use a single date dimension table and keep only one active relationship (e.g., to OrderDate). For other dates, create measures that filter the date table using CALCULATE and FILTER.
Why this is correct
This is the recommended approach: keep one active relationship (e.g., to OrderDate) and use USERELATIONSHIP in DAX to activate the inactive relationships for ShipDate and DueDate when needed.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Create a separate date dimension table for each date column in the Sales table and relate each to the fact table.
Why it's wrong here
This is not recommended because it leads to multiple date tables, which is inefficient and can cause confusion.
- ✗
Use a single date dimension table and create multiple active relationships using bridging tables or by duplicating the dimension table for each role.
Why it's wrong here
Actually, you cannot have multiple active relationships between the same two tables in Power BI; you need either inactive relationships or separate dimension tables. So this is not feasible as stated.
- ✗
Use a single date dimension table and create inactive relationships for ShipDate and DueDate. Use USERELATIONSHIP in DAX measures.
Why it's wrong here
This is partially correct but incomplete; you should create active relationships for commonly filtered dates, and use USERELATIONSHIP for others. However, the best practice is to have only one active relationship per pair of tables, and the other dates are inactive.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume multiple date columns require multiple date tables (Option B) or that inactive relationships alone solve all date role needs (Option D), forgetting that fiscal year logic must be explicitly modeled in the date table.
Trap categories for this question
Similar concept trap
This is not recommended because it leads to multiple date tables, which is inefficient and can cause confusion.
Detailed technical explanation
How to think about this question
In Power BI, a single date dimension table with a Mark as Date Table setting enables time intelligence functions like TOTALYTD and SAMEPERIODLASTYEAR. For fiscal year analysis, you add a calculated column such as 'Fiscal Year = IF(MONTH([Date]) >= 4, YEAR([Date]) & "-" & YEAR([Date])+1, YEAR([Date])-1 & "-" & YEAR([Date]))'. The USERELATIONSHIP function temporarily activates an inactive relationship for measures like 'Sales by Ship Date = CALCULATE(SUM(Sales[LineTotal]), USERELATIONSHIP(Sales[ShipDate], 'Date'[Date]))', allowing multiple date roles without table duplication.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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.
- →
Model the data — study guide chapter
Learn the concepts, then practise the questions
- →
Model the data practice questions
Targeted practice on this topic area only
- →
All PL-300 questions
966 questions across all exam domains
- →
Microsoft Power BI Data Analyst PL-300 study guide
Full concept coverage aligned to exam objectives
- →
PL-300 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PL-300 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Prepare the data practice questions
Practise PL-300 questions linked to Prepare the data.
Deploy and maintain assets practice questions
Practise PL-300 questions linked to Deploy and maintain assets.
Model the data practice questions
Practise PL-300 questions linked to Model the data.
Visualize and analyze the data practice questions
Practise PL-300 questions linked to Visualize and analyze the data.
Manage and secure Power BI practice questions
Practise PL-300 questions linked to Manage and secure Power BI.
PL-300 fundamentals practice questions
Practise PL-300 questions linked to PL-300 fundamentals.
PL-300 scenario practice questions
Practise PL-300 questions linked to PL-300 scenario.
PL-300 troubleshooting practice questions
Practise PL-300 questions linked to PL-300 troubleshooting.
Practice this exam
Start a free PL-300 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this PL-300 question test?
Model the data — This question tests Model the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a single date dimension table and keep only one active relationship (e.g., to OrderDate). For other dates, create measures that filter the date table using CALCULATE and FILTER. — Option A is correct because it uses a single date dimension table with one active relationship (typically to OrderDate) and leverages CALCULATE with FILTER or USERELATIONSHIP for other date roles. This is the recommended star schema design in Power BI, as it avoids unnecessary table duplication and maintains model simplicity while supporting fiscal year analysis via a calculated column in the date table.
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 →
Last reviewed: Jun 11, 2026
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.