How is the change of local time due to daylight savings time handled in Snowflake tasks? (Choose two.)

Question

Options

• AA task scheduled in a UTC-based schedule will have no issues with the time changes.
• BTask schedules can be designed to follow specified or local time zones to accommodate the time
• CA task will move to a suspended state during the daylight savings time change.
• DA frequent task execution schedule like minutes may not cause a problem, but will affect the task
• EA task schedule will follow only the specified time and will fail to handle lost or duplicated hours.

• A
  89% (16)
• C
  6% (1)
• D
  6% (1)

Explanation

Snowflake provides two reliable approaches for handling DST in task scheduling. First, scheduling tasks using UTC (A) completely avoids DST issues because UTC never shifts - a task set for 02:00 UTC will always fire at exactly that moment regardless of local clock changes. Second, Snowflake allows task schedules to be defined using cron syntax with an explicit time zone (B), which means Snowflake is aware of the DST rules for that zone and can correctly handle the 'spring forward' (skipped hour) and 'fall back' (repeated hour) transitions. Tasks do not enter a suspended state during DST changes (C). While frequent minute-based schedules are less affected, they can still experience DST edge cases (D is imprecise). Option E is incorrect - Snowflake's CRON-based scheduling with time zones is specifically designed to handle lost or duplicated hours.

No community discussion yet for this question.