Exam PL-300 All Questions

View all questions & answers for the PL-300 exam

Exam PL-300 topic 1 question 39 discussion

Actual exam question from Microsoft's PL-300

Question #: 39
Topic #: 1

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?

A. Yes
B. No

Show Suggested Answer

Suggested Answer: A 🗳️

by Tex02 at Sept. 6, 2024, 12:57 a.m.

Comments

Submit Cancel

Tex02

Highly Voted 9 months ago

I think the answer is A. adding the index key won't fix the problem by itself but you are also normalising the case which will resolve it.

upvoted 12 times

Sohang51

9 months ago

Actually i dont understand that how normalising the case will resolve the issue as undefined values and errors can also be related to missing values and unmatched data type..?

upvoted 4 times

...

dpkamalarani

Highly Voted 8 months, 4 weeks ago

A is right

upvoted 6 times

...

lechuc508

Most Recent 3 weeks, 4 days ago

Selected Answer: A

i chosen A

upvoted 1 times

...

BhavnishM

2 months ago

Selected Answer: B

The column contains case sensitive data doesn't means undefined errors can be fixed by resolving case

upvoted 1 times

...

Pitxunet

4 months ago

Selected Answer: A

The answer is "Yes". I found the following in the Microsoft documentation: "Because the engine that stores and queries data in Power BI is case insensitive, take special care when you work in DirectQuery mode with a case-sensitive source. Power BI assumes that the source has eliminated duplicate rows. Because Power BI is case insensitive, it treats two values that differ only by case as duplicate, whereas the source might not treat them as such. In such cases, the final result is undefined. To avoid this situation, if you use DirectQuery mode with a case-sensitive data source, normalize casing in the source query or in Power Query Editor." Source: https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-data-types Therefore, the solution is to normalize casing at the source.

upvoted 1 times

...

kbcity1

4 months, 2 weeks ago

Selected Answer: B

The answer is B, adding an index key and normalizing casing in the data source does not resolve the issue of undefined values and errors in the Power BI semantic model in DirectQuery mode.

upvoted 1 times

...

f133b89

4 months, 4 weeks ago

Selected Answer: A

Yes, this solution meets the goal.

upvoted 1 times

...

leela1507

5 months, 1 week ago

Selected Answer: A

Answer A

upvoted 1 times

...

7Veritas

5 months, 2 weeks ago

Selected Answer: B

Adding Index does not resolve the question, it is an unnecessary complication, hence the solution is B. While normalizing casing in the data source would help address case-sensitivity issues, adding an index key is unnecessary and doesn't contribute to solving the specific problem of undefined values and errors caused by case-sensitive data. Adding an index key: - Doesn't address case sensitivity issues - Adds unnecessary complexity - Is not relevant to resolving undefined values and errors caused by case-sensitive data - Creates additional overhead without solving the core problem

upvoted 1 times

...

shreejoshi

6 months, 1 week ago

Selected Answer: B

Adding index will not affect other column value or it's type. so error will remain the same.

upvoted 2 times

...

Andrew_17

7 months ago

Case sensitive data was resolved in data source

upvoted 2 times

...

Enuoma

7 months, 2 weeks ago

Answer is A. Yes, adding an index key can help resolve issues related to undefined values or error. Normalizing casing ensures that case-sensitive data is consistent reducing chance of mismatches or errors

upvoted 1 times

...

hsetin

8 months ago

aCCORDING TO PERPLEXITY, the answer is still NO, as this does not solve the issue of undefined values and errors, and also direct query does not really work well with normalizing teh case either.

upvoted 1 times

...

ae8a90c

8 months ago

Selected Answer: A

I believe the option A is correct

upvoted 1 times

...

leah.pring

8 months ago

According to Copilot, the answer is A. Here is the explanation I got: Yes, adding an index key and normalizing the casing in the data source can help resolve the issue of undefined values and errors in a Power BI semantic model in DirectQuery mode. Here’s why: Index Key: Adding an index key can improve query performance and ensure that each row is uniquely identifiable, which helps in avoiding errors related to duplicate or missing data1. Normalizing Casing: Normalizing the casing ensures consistency in the data, which can prevent mismatches and errors that arise from case sensitivity issues1. These steps should help in cleaning up the data and making it more reliable for analysis in Power BI. https://learn.microsoft.com/en-us/power-bi/guidance/directquery-model-guidance

upvoted 4 times

...