Switching the semantic model mode does not resolve case-sensitivity undefined values

PL-300 By islever Editorial Last updated Sep 25, 2026

Profile and clean the data

Short answer

B No, the case-insensitive engine exhibits the same behavior in any mode; only fixing the casing fixes the data.

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have a data source that contains a column. The column contains case sensitive data. You have a Power BI semantic model in DirectQuery mode. You connect to the model and discover that it contains undefined values and errors. You need to resolve the issue. Solution: You change the semantic model mode. Does this meet the goal?

Yes
No Correct Answer

Key Takeaways

The Power BI engine is case-insensitive in both Import and DirectQuery storage — switching modes moves where the data lives but never reconciles case-sensitive source values, so the collision problem follows the model.

In the same case-sensitive scenario, the proposed solution changes the semantic model mode to eliminate the undefined values and errors found in the DirectQuery model.

Common mistake: Assuming Import mode fixes everything because Power Query is case-sensitive — the case sensitivity exists only in Power Query's evaluation layer; once loaded, the case-insensitive engine exhibits the same undefined-value behavior.

Expert Analysis

Why the Answer Is Correct

Microsoft documents that the Power BI engine that stores and queries data is case-insensitive, which is why case-sensitive DirectQuery sources surface undefined values and errors. Storage mode is not the cause: an imported model is stored and queried by the same case-insensitive engine, so merely changing the model's mode does not normalize casing or repair the colliding values. The undefined values and errors would persist, and the solution does not meet the goal.

Why the Other Options Are Wrong

Answering Yes rests on the idea that Import mode lets Power Query handle case sensitivity. While Power Query expressions are case-sensitive during evaluation, the question's solution only changes the model mode — it never specifies any Power Query transformation that normalizes casing or adds an index key. Without one of the documented remedies, the engine-level mismatch remains.

Community Comment Notes

Commenters voting No argue that changing the semantic mode does not solve the issue and that the data must be transformed or cleaned first. A single dissenting comment answers Yes on the strength of Power Query's case sensitivity, but that conflates a transformation-layer capability with an actual transformation, which the solution never proposes.

Official Reference

https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-data-types

This link opens the official vendor documentation in a new tab.

Community Votes

100%

100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

kenyJen 👍 3

B. I dont think changing the semantic mode will solve the issue.
Fatima300 👍 2 Answered B

B. No Changing the semantic model mode (e.g., from DirectQuery to Import) won't fix case sensitivity issues or errors in the data. You need to transform or clean the data to resolve these issues.
FraGuara 👍 1

My answer would be A. Yes: Switching from DirectQuery to Import mode would resolve the issue with case sensitivity. Power Query can handle case sensitivity effectively, but its functions are limited when operating in DirectQuery mode. By switching to Import mode, you gain full access to Power Query's data transformation capabilities, allowing you to standardize the case of your data before it is loaded into the model.
Jayaruwan 👍 1 Answered B

Given answer is correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Practice All PL-300 Questions

Access 116 questions with complete answers and detailed explanations.

View Full PL-300 Practice Test →

← Back to PL-300 Study Guide