Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft PL-300 Exam - Topic 1 Question 58 Discussion

Actual exam question for Microsoft's PL-300 exam
Question #: 58
Topic #: 1
[All PL-300 Questions]

You are creating a report in Power BI Desktop.

You load a data extract that includes a free text field named coll.

You need to analyze the frequency distribution of the string lengths in col1. The solution must not affect the size of the model.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

0/2000 characters
Casey
4 months ago
Wait, can we really analyze string lengths without affecting the model size?
upvoted 0 times
...
Leana
4 months ago
B is just calculating average, not frequency distribution.
upvoted 0 times
...
Man
4 months ago
D sounds interesting, but can you really group by length in Power Query?
upvoted 0 times
...
Deangelo
4 months ago
I think C is the best choice, keeps the model size down!
upvoted 0 times
...
Marleen
5 months ago
Option A adds a calculated column, but it might increase model size.
upvoted 0 times
...
Rosamond
5 months ago
I recall that calculating averages isn't the same as analyzing frequency distribution, so option B seems off to me.
upvoted 0 times
...
Elouise
5 months ago
I think option D sounds familiar, but I'm not clear on how grouping by length would work in Power Query.
upvoted 0 times
...
Carlton
5 months ago
I feel like option C is what we practiced in class, but I'm not entirely sure if it would affect the model size.
upvoted 0 times
...
Brande
5 months ago
I remember we discussed how calculated columns can increase the model size, so I think option A might not be the best choice.
upvoted 0 times
...
Huey
5 months ago
Hmm, I'm not sure which option is the best here. I'm torn between C and D. I think I'll try C first, since adding a column in Power Query seems like the most straightforward solution. If that doesn't work, I'll switch to option D.
upvoted 0 times
...
Ramonita
5 months ago
I've got this! Option C is the way to go. Adding a column in the Power Query Editor is the best approach to get the string length information without impacting the model size. I feel confident about this one.
upvoted 0 times
...
Zana
5 months ago
I'm a bit confused here. Should I be using a DAX calculated column or a Power Query function? I'm not sure which one would be better for this scenario. Maybe I'll start with option A and see if that works.
upvoted 0 times
...
Sharen
5 months ago
Okay, let's think this through. I'm leaning towards option D - changing the distribution for the Column profile to group by length for col1. That seems like the most efficient way to get the frequency distribution without adding any extra columns.
upvoted 0 times
...
Halina
5 months ago
Hmm, this looks like a tricky one. I think I'll go with option C - adding a column in the Power Query Editor to calculate the length of col1. That way, I can analyze the frequency distribution without affecting the size of the model.
upvoted 0 times
...
Broderick
10 months ago
If the data is too long, you can always just shorten the column. Problem solved!
upvoted 0 times
Yuki
9 months ago
That's a good idea, it will help us analyze the frequency distribution without affecting the model size.
upvoted 0 times
...
Albina
10 months ago
C) From Power Query Editor, add a column that calculates the length of col1
upvoted 0 times
...
Arlette
10 months ago
A) In the report, add a DAX calculated column that calculates the length of col1
upvoted 0 times
...
...
Leanora
11 months ago
I heard Power BI can also calculate the length of your hair. Gotta keep that model lean and mean!
upvoted 0 times
Paulina
10 months ago
That's interesting! Power BI can do a lot of things, but I don't think it can calculate hair length.
upvoted 0 times
...
Mabel
10 months ago
C) From Power Query Editor, add a column that calculates the length of col1
upvoted 0 times
...
Sol
10 months ago
A) In the report, add a DAX calculated column that calculates the length of col1
upvoted 0 times
...
...
Tuyet
11 months ago
Option D? Seriously? Grouping by length? That's like trying to catch a fish with your bare hands. Power Query is the obvious choice here.
upvoted 0 times
...
Carin
11 months ago
Hmm, I was thinking of using a DAX calculated column, but you're right, that might increase the model size. Power Query is definitely the way to go!
upvoted 0 times
Mirta
10 months ago
C) From Power Query Editor, add a column that calculates the length of col1
upvoted 0 times
...
Claudia
10 months ago
A) In the report, add a DAX calculated column that calculates the length of col1
upvoted 0 times
...
...
Gilbert
11 months ago
I agree with Tasia. Power Query is the right place to handle this data transformation without impacting the model.
upvoted 0 times
...
Tasia
11 months ago
Option C is the way to go! Adding a column in Power Query is the best solution to avoid bloating the model size.
upvoted 0 times
Clarinda
10 months ago
User4: Let's go with option C then. From Power Query Editor, add a column that calculates the length of col1.
upvoted 0 times
...
Michel
10 months ago
User3: Agreed. It's the best solution for analyzing the frequency distribution of string lengths.
upvoted 0 times
...
Tamra
11 months ago
User2: That's a good idea. It won't affect the size of the model.
upvoted 0 times
...
Kallie
11 months ago
User1: I think we should add a column in Power Query to calculate the length of col1.
upvoted 0 times
...
...
Valentin
11 months ago
I prefer option A) In the report, add a DAX calculated column that calculates the length of col1. It gives more flexibility in the report.
upvoted 0 times
...
Dortha
12 months ago
I agree with Doretha. Adding a column in Power Query Editor is the most efficient way to analyze the frequency distribution.
upvoted 0 times
...
Doretha
12 months ago
I think the best option is C) From Power Query Editor, add a column that calculates the length of col1.
upvoted 0 times
...

Save Cancel