nerdexam
Microsoft

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.

Query and transform data

Question

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 change the IoT DateTime column to the date data type. Does this meet the goal?

Exhibit

DP-500 question #86 exhibit

Options

  • AYes
  • BNo

How the community answered

(48 responses)
  • A
    27% (13)
  • B
    73% (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.

AYes

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.

BNoCorrect

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

#Data Types#Data Transformation#Date and Time Analysis#Dataset Performance

Community Discussion

No community discussion yet for this question.

Full DP-500 Practice