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.
Microsoft Certified: Power BI Data Analyst Associate · Microsoft
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Yes even if it doesn't needed to have an hierarchy, but we can remove hours and remove duplicates afterwards
Splitting the IoT DateTime column into separate Date and Time columns might help slightly with usability, but it doesn't inherently improve dataset performance — especially if the goal is analysis by hour and day of year. Instead, for performance and usability, a better solution would be to: Create calculated columns such as: DayOfYear = DAY('IoTEvents'[DateTime]) + (MONTH('IoTEvents'[DateTime]) - 1) * 30 (or use FORMAT(...,"DDD") for actual day of year) Hour = HOUR('IoTEvents'[DateTime]) Or use Power Query to extract Hour and DayOfYear from the original datetime — which is even better, because: It reduces model size (by storing smaller integer/text columns) It allows in-memory compression to work more efficiently than high-cardinality datetime fields
yes it meets the goal