To handle daylight savings in scheduling, which approach is recommended?

• A. Use fixed UTC offsets
• B. Use locale IDs
• C. Use city names
• D. Use short codes

Answer: (C)

Handling daylight saving in scheduling hinges on using a time zone identifier that encodes DST rules. Using city names as time zone identifiers ties a timestamp to a specific region’s rules in the IANA tz database, so converting to local time automatically applies the correct offset for any date, including DST transitions and historical changes. Fixed UTC offsets don’t adjust for DST, so they go wrong during the summer when clocks move forward. Locale IDs cover language/formatting, not time zones, and short codes like EST/EDT are ambiguous and can mislead about the current offset. City-based time zone identifiers provide the precise, rule-based way to compute local times across DST changes.