DP-500 · Question #86
The IoT GUID and IoT ID columns are unique to each row in the query. You need to analyze IoT events by the hour and day of the year. The solution must improve dataset performance. Solution: You…
The correct answer is B. No. Changing the IoT DateTime column to a date data type does not meet the goal of analyzing IoT events by the hour and day of the year while improving performance.
Question
Exhibit
Options
- AYes
- BNo
How the community answered
(48 responses)- A27% (13)
- B73% (35)
Why each option
Changing the IoT DateTime column to a date data type does not meet the goal of analyzing IoT events by the hour and day of the year while improving performance.
Changing the column to a date data type removes the time component, preventing any analysis by the hour, which is explicitly required by the question.
Changing the 'IoT DateTime' column to a 'date' data type discards the time component, which makes analysis by the hour impossible. While it might reduce storage slightly, it fundamentally compromises the ability to perform the required granular temporal analysis, thus failing to meet the analytical goal, even if performance were improved for other aspects.
Concept tested: Data type selection, temporal granularity, analytical requirements
Source: https://learn.microsoft.com/en-us/sql/t-sql/data-types/date-transact-sql
Topics
Community Discussion
No community discussion yet for this question.
