Which component enables a playbook to run on a regular schedule with minimal overhead by generating cases for the operator to handle?

• A. Use a VM to host a script that runs a playbook via an API call.
• B. Create a SOAR request and a playbook trigger matching the request.
• C. Write a custom SOAR job in the IDE using code from playbook actions.
• D. Create a Cron Scheduled Connector and configure a playbook trigger to match cases created by the connector.

Answer: (B)

Scheduling a playbook in SOAR with minimal overhead is achieved by turning the schedule into a SOAR request and using a playbook trigger that matches that request. This lets the platform handle timing and orchestration, automatically generating a new case for the operator to act on each scheduled run. The operator workflow remains streamlined because the trigger-and-request mechanism directly ties the scheduled event to a ready-to-work case.

Other approaches add extra layers of maintenance or infrastructure, such as running a script on a VM, building a custom SOAR job, or using a Cron-like connector to generate cases. Those options increase overhead and integration work compared to the clean, built-in scheduling and triggering path.