Which two playbook triggers enable the use of trigger events in later tasks as trigger variables? (Choose two.)

In FortiAnalyzer playbooks, "EVENT" and "INCIDENT" triggers initiate playbooks based on specific occurrences, such as a matched event handler or a newly created incident. Because these triggers are tied to specific security data, they pass context (such as IP addresses, user names, or incident IDs) into the playbook. This allows subsequent tasks within the playbook to reference and utilize this dynamic data using trigger variables (e.g., trigger.event.ip). Schedule and On-Demand triggers lack this specific contextual data.

C: ON SCHEDULE triggers run at predefined times and do not carry specific event or incident context to use as variables.

D: ON DEMAND triggers are executed manually by an administrator and lack the automated event/incident data context required for trigger variables.

Fortinet FortiAnalyzer 7.2 Administration Guide, Section: "Playbooks" -> "Triggers and Variables".

Fortinet NSE 7 Security Operations 7.2 Courseware, Module: "Playbooks and Automation".