Task 4.3: Implement job schedules using Lakeflow Jobs with an understanding of trigger types (scheduled, file arrival, and table update).

• AIt needs a separate trigger for each subdirectory under landing/

  Incorrect

  A file arrival trigger checks for new files recursively in all subdirectories of the configured location, so one trigger covers them.

• BIt can watch the root or a subpath of a Unity Catalog volume or external location

  Correct

  The storage location must be a volume or external location in Unity Catalog, at its root or a subpath.

• CThe path can include a wildcard such as landing/*.csv to select files

  Incorrect

  The trigger path cannot contain wildcards such as * or ?.

• DIt checks for new files about once a minute on a best-effort basis

  Correct

  File arrival triggers make a best effort to check for new files every minute, depending on the storage performance.

• EIt requires the job to also have a continuous trigger

  Incorrect

  A continuous trigger cannot be combined with other triggers; a file arrival trigger works on its own.

File arrival triggers watch a Unity Catalog storage location recursively and start a run when new files appear.

• AAn advanced schedule at minute 0 of each hour, with time zone UTC

  Correct

  UTC has no daylight saving changes, and the documentation says to choose UTC when a job must run at every hour in absolute time.

• BAn advanced schedule at minute 0 of each hour, with time zone America/New_York

  Incorrect

  In a time zone that observes daylight saving time, an hourly job can be skipped or appear delayed when the change happens.

• CA simple schedule with an interval of 1 hour

  Incorrect

  A simple schedule runs at an interval from a start the scheduler chooses; you cannot pick the first run time, so runs are not on the hour.

• DA continuous trigger, with the notebook sleeping one hour before it ends

  Incorrect

  A continuous job starts a new run whenever one ends; a sleep adds cost and drift instead of a clock-based schedule.

Advanced schedules set the period, start time and time zone. Choose UTC when absolute timing matters across daylight saving transitions.

• AA simple schedule with an interval of 24 hours

  Incorrect

  A simple schedule repeats from a start the scheduler chooses and also runs on weekends.

• BA file arrival trigger on the folder where the job's input files land

  Incorrect

  File arrival starts runs when files appear, not at a fixed time on chosen days.

• CA continuous trigger with a check for the weekday at the start of the notebook

  Incorrect

  A continuous trigger starts a new run whenever the previous one ends, so the job would run all day.

• DAn advanced schedule with cron for 06:00 Mon-Fri, time zone Europe/Istanbul

  Correct

  Advanced schedules set the period, start time and time zone, and can be edited as Quartz cron expressions.

Simple schedules give an interval; advanced schedules give full calendar control through Quartz cron syntax with a time zone.

• ADelete the trigger and recreate it after the maintenance

  Incorrect

  Deleting removes the configured schedule, which then has to be rebuilt.

• BPause the trigger, then resume it after the maintenance

  Correct

  A paused trigger starts no new runs while active runs continue, and resuming restores the same schedule.

• CSet the job's maximum concurrent runs to 0

  Incorrect

  This changes a job setting that must be kept, and limiting concurrency is not how a schedule is suspended.

• DCancel each new run as soon as it starts

  Incorrect

  Manual cancellation is error-prone and still starts compute for each run.

Pausing a trigger in the Schedules & Triggers section stops new runs without changing its configuration, and resuming restores the schedule.

• AA table update trigger on main.sales.orders, with Wait after last change set to one hour

  Incorrect

  This watches orders alone; waiting after its last change does not make the run wait for customers to be updated.

• BOne trigger on both tables, with Trigger when set to Any table is updated

  Incorrect

  Any starts a run as soon as one of the tables changes.

• COne trigger on both tables, with Trigger when set to All tables are updated

  Correct

  With several tables in one trigger, All waits until each of them has been updated before starting a run.

• DA file arrival trigger on the cloud storage paths that hold the two tables

  Incorrect

  File arrival triggers cannot watch paths that contain tables; table changes are what table update triggers detect.

A table update trigger can watch up to 10 tables and start a run when any or all of them change.

• AWait after last change in seconds, set to about 60

  Correct

  The trigger waits this long after the most recent file arrives, and each new file resets the timer, so a run starts once the burst is complete.

• BMinimum time between triggers in seconds, set to about 60

  Incorrect

  This is a cooldown after a run completes; the first file of a burst can still start a run while the rest are landing.

• CMaximum concurrent runs set to 1

  Incorrect

  Concurrency caps how many runs are active at once; it does not make the trigger wait for the burst to finish.

• DA scheduled trigger each minute in addition

  Incorrect

  A schedule starts runs by time, whether or not a burst has finished.

The two advanced options of file arrival and table update triggers are a cooldown (minimum time between triggers) and debouncing (wait after last change).