DA0-002 Data Acquisition and Preparation Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  DATEDIFF(year, order_date)

  Why it's wrong here

  DATEDIFF returns the count of year boundaries crossed between two dates, so it requires a start and end argument and yields an integer interval, not the year component. It is tempting because it genuinely handles year arithmetic; it would be correct for calculating age or tenure between order_date and today.

• ✗

  DATEADD(year, order_date)

  Why it's wrong here

  DATEADD adds an integer to a date and returns a new date, so passing order_date as the interval count is invalid and never extracts a component. It is tempting because it manipulates years directly; it would be correct for projecting a future date, such as order_date plus 30 days.

• ✓

  YEAR(order_date)

  Why this is correct

  YEAR(order_date) returns the year portion as an integer directly from the date value, satisfying the requirement to extract only the year. Unlike DATEPART, which needs a datepart argument, YEAR is a dedicated function that isolates that single component without additional parameters.

• ✗

  FORMAT(order_date, 'yyyy')

  Why it's wrong here

  FORMAT returns a string, not a numeric year, so it cannot feed date arithmetic or comparisons without casting. FORMAT suits locale-aware display formatting, whereas YEAR(order_date) or DATEPART extracts the integer year value the question requires.