Which statement best describes an event-driven trigger?

Which statement best describes an event-driven trigger?

• A. It runs in response to a data event or external signal.
• B. It runs at fixed times.
• C. It is deprecated.
• D. It is used for data backup.

Answer: (A)

Event-driven triggers start automatically when something happens—typically a data event or an external signal. This reactive behavior means the action fires only in response to a relevant event, such as new data arriving or a specific update being detected, rather than on a predetermined schedule. In Foundry and similar systems, you configure tasks to run when a dataset is ingested, updated, or when an external message arrives, which is the core idea of being event-driven. Fixed-time triggers, by contrast, run at set intervals regardless of data changes, so they aren’t event-driven. Statements about deprecation or using triggers for backups describe status or use cases, not the fundamental behavior of how an event-driven trigger activates.

Event-driven triggers start automatically when something happens—typically a data event or an external signal. This reactive behavior means the action fires only in response to a relevant event, such as new data arriving or a specific update being detected, rather than on a predetermined schedule. In Foundry and similar systems, you configure tasks to run when a dataset is ingested, updated, or when an external message arrives, which is the core idea of being event-driven.

Fixed-time triggers, by contrast, run at set intervals regardless of data changes, so they aren’t event-driven. Statements about deprecation or using triggers for backups describe status or use cases, not the fundamental behavior of how an event-driven trigger activates.