The answer is that the ShipDate column is stored as text rather than as a date. This is the most likely cause because when a date column is text, Power BI treats each unique text entry as a discrete category, not as a continuous time hierarchy. Even with a separate date table marked as such, the line chart uses the ShipDate column from the Shipments table, so without a proper date data type, Power BI cannot break revenue down over time—it simply aggregates the total revenue for each carrier across all rows, producing a flat, constant line. On the PL-300 exam, this scenario tests your understanding of data modeling and the critical distinction between text and date data types; a common trap is assuming a separate date table automatically fixes date recognition issues. Remember the memory tip: if your line chart looks like a flat horizon, check your date column’s data type—text won’t let time flow.
PL-300 Visualize and analyze the data Practice Question
This PL-300 practice question tests your understanding of visualize and analyze the data. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 building a report for a logistics company. The dataset includes a 'Shipments' table with columns: ShipmentID, ShipDate, OriginCity, DestinationCity, Weight, Revenue, and Carrier. The company wants to analyze revenue trends by carrier over time. They have a date table marked as a date table. You create a line chart with ShipDate on the axis and Revenue as the value, with Carrier as the legend. However, the line chart shows a single line for each carrier, but the revenue values are aggregated across all dates, showing a constant line. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
There are missing relationships between Shipments and the date table.
Why wrong: Missing relationships would cause no data to appear, not constant lines.
B
The ShipDate column is of type 'Text' instead of 'Date'.
If ShipDate is text, Power BI will treat each unique date as a separate category, but if the values are dates, it may still aggregate incorrectly if not recognized.
C
The Revenue column is a measure that is not summing correctly.
Why wrong: A measure would still show variation over time if the date context changes.
D
The date table is marked as a date table but not related to Shipments.
Why wrong: This would cause no filtering, but the line chart would still show variation if the ShipDate column is used directly.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The ShipDate column is of type 'Text' instead of 'Date'.
Option B is correct because if the ShipDate column is stored as text, Power BI cannot treat it as a continuous date hierarchy. Even though a separate date table is marked as a date table, the line chart uses the ShipDate column from the Shipments table. When ShipDate is text, Power BI treats each unique text value as a separate category, and since there is no time intelligence, the revenue is aggregated across all rows for each carrier, resulting in a flat line showing the total revenue for that carrier. The chart does not break down revenue by actual dates, so it appears constant.
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.
✗
There are missing relationships between Shipments and the date table.
Why it's wrong here
Missing relationships would cause no data to appear, not constant lines.
✓
The ShipDate column is of type 'Text' instead of 'Date'.
Why this is correct
If ShipDate is text, Power BI will treat each unique date as a separate category, but if the values are dates, it may still aggregate incorrectly if not recognized.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The Revenue column is a measure that is not summing correctly.
Why it's wrong here
A measure would still show variation over time if the date context changes.
✗
The date table is marked as a date table but not related to Shipments.
Why it's wrong here
This would cause no filtering, but the line chart would still show variation if the ShipDate column is used directly.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume a separate date table automatically resolves date-related issues, but the root cause is the data type of the column used on the axis, not the presence or absence of a date table relationship.
Trap categories for this question
Command / output trap
A measure would still show variation over time if the date context changes.
Detailed technical explanation
How to think about this question
In Power BI, when a column is of type Text, the visual treats each unique string as a discrete category, and the axis does not support a continuous date scale. This means that even if the underlying data contains date-like strings, Power BI will not apply date hierarchy or time intelligence functions. The line chart will group all rows with the same text value together, and since each carrier has only one text value (e.g., '2023-01-01'), the revenue is summed across all rows for that carrier, producing a flat line. To fix this, the ShipDate column must be converted to Date/Time data type using Power Query or the modeling tab.
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.
Visualize and analyze the data — This question tests Visualize and analyze the data — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The ShipDate column is of type 'Text' instead of 'Date'. — Option B is correct because if the ShipDate column is stored as text, Power BI cannot treat it as a continuous date hierarchy. Even though a separate date table is marked as a date table, the line chart uses the ShipDate column from the Shipments table. When ShipDate is text, Power BI treats each unique text value as a separate category, and since there is no time intelligence, the revenue is aggregated across all rows for each carrier, resulting in a flat line showing the total revenue for that carrier. The chart does not break down revenue by actual dates, so it appears constant.
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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.