If you want your incremental data loads to handle daylight savings, what does Oracle recommend you do when specifying time zones?

• A. When you specify time zones, Oracle recommends you use city names to handle daylight savings.
• B. Use fixed UTC offsets to account for DST.
• C. Disable daylight savings in the scheduling.
• D. Use region codes only.

Answer: (B)

When you want incremental loads to remain reliable across daylight saving changes, use a fixed UTC offset for time zones. This keeps the actual moment in time constant, so the boundaries you define for each incremental window don’t shift when DST starts or ends. If you used city names or region-based identifiers, the DST rules could vary over time or between environments, causing offsets to change and potentially creating gaps or duplicates in the load window. Disabling DST or relying only on region codes would avoid or mishandle DST altogether, which isn’t desirable. By sticking to a fixed UTC offset, you maintain a stable, DST-independent basis for scheduling and can convert to local time later for presentation if needed.