Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 38 of 134
Free Preview · 134 of 444 · questions 1–134 of 444 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
B. No Adding an index key and normalizing casing in the data source doesn't address the underlying case-sensitivity mismatch issue in DirectQuery mode. Since DirectQuery passes queries directly to the source rather than caching data locally, the comparisons and relationships still rely on the source's native case sensitivity behavior — an index key doesn't change how text comparisons or DAX evaluates string matching. This is still not the correct fix for this scenario.
You must configure the data source to use a case‑insensitive collation or change the column collation so DirectQuery queries behave consistently.
* Answer: Yes * Explanation: Adding an index key and normalizing casing in the data source ensures: - Consistency in case-sensitive data: Normalizing case prevents mismatches in joins, filters, and comparisons. - Improved query performance and stability: An index key helps optimize lookups and reduce errors caused by ambiguous or duplicate values. This approach directly addresses the root cause of undefined values and errors in DirectQuery mode, so it meets the goal.