Q: 3
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.
From Power Query Editor, you profile the data shown in the following exhibit.
The IOT ID columns are unique to each row in query.
You need to analyze 10T events by the hour and day of the year. The solution must improve dataset
performance.
Solution: You change the IOT DateTime column to the Date data type.
Does this meet the goal?
The IOT ID columns are unique to each row in query.
You need to analyze 10T events by the hour and day of the year. The solution must improve dataset
performance.
Solution: You change the IOT DateTime column to the Date data type.
Does this meet the goal?Options
Discussion
Doesn’t seem right picking A here, since changing to Date drops the hour part you’d need. I know A looks tempting for performance, but this feels like a trick option.
I see why some pick A. Changing to Date cuts down on column cardinality, which helps performance, and if you just wanted daily summaries it’d be fine. But I think this removes the hour info you’d need for part of the analysis. So leaning toward A here but not sure if that’s enough for the goal.
Option B makes more sense but is the question really asking for analysis by both hour and day, or just by date? If they only care about day-level analysis, A could work. But if hour's needed, then turning DateTime into Date would drop too much info and break the requirement.
Be respectful. No spam.
