PL-300 · Question #393
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…
The correct answer is B. No. While normalizing casing in the data source is beneficial, simply adding an index key without addressing the undefined values directly does not fully resolve the issue.
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 add an index key and normalize casing in the data source. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(67 responses)- A28% (19)
- B72% (48)
Why each option
While normalizing casing in the data source is beneficial, simply adding an index key without addressing the undefined values directly does not fully resolve the issue.
Adding an index key improves data retrieval efficiency but does not by itself resolve issues of undefined values or errors in the data content, even if casing is normalized.
While normalizing casing in the source is a correct step to address case sensitivity, adding an index key primarily improves query performance for lookups and joins; it does not inherently fix "undefined values and errors" which indicate corrupted or missing data. An index key ensures faster retrieval but does not modify the data content to resolve quality issues.
Concept tested: Data quality vs. database indexing
Community Discussion
No community discussion yet for this question.