Which statement best captures the difference between a scheduled job and an event-driven trigger?

• A. A scheduled job runs at defined times or intervals; an event-driven trigger runs in response to a data event.
• B. A scheduled job runs at fixed times.
• C. An event-driven trigger runs in response to a data event.
• D. They are the same mechanism.

Answer: (A)

Time-based scheduling versus data-event triggers is what this item is testing. A scheduled job runs at defined times or intervals—you set it to run every night at 2 a.m., or every hour, regardless of what data is present. An event-driven trigger, on the other hand, activates in response to a data event—such as a new record arriving, a file being dropped, or a message being published—so the work starts when that event occurs.

This distinction matters because it shapes when and how work happens. If you need regular, predictable processing, a scheduled job is the fit. If you want processing to begin as soon as new data comes in, an event-driven trigger is the right choice. The other options are incomplete because they omit either the timing aspect of scheduled jobs or the data-event focus of event-driven triggers, and one option incorrectly claims they are the same mechanism.