A user has written a playbook that calls three other playbooks, one after the other. The user notices that the second playbook starts executing before the first one completes. What is the cause of…

The correct answer is A. Synchronous execution has not been configured. In Splunk SOAR, playbooks can execute actions either synchronously (waiting for one action to complete before starting the next) or asynchronously (allowing actions to run concurrently). If a playbook starts executing before the previous one has completed, it indicates that…

Developing Playbooks

Question

A user has written a playbook that calls three other playbooks, one after the other. The user notices that the second playbook starts executing before the first one completes. What is the cause of this behavior?

Options

ASynchronous execution has not been configured.
BThe first playbook is performing poorly.
CThe sleep option for the second playbook is not set to a long enough interval.
DIncorrect join configuration on the second playbook.

How the community answered

(35 responses)

A
71% (25)
B
6% (2)
C
14% (5)
D
9% (3)

Explanation

In Splunk SOAR, playbooks can execute actions either synchronously (waiting for one action to complete before starting the next) or asynchronously (allowing actions to run concurrently). If a playbook starts executing before the previous one has completed, it indicates that synchronous execution has not been properly configured between these playbooks. This is crucial when the output of one playbook is a dependency for the subsequent playbook.

Topics

#synchronous execution#playbook chaining#execution order#playbook configuration

Community Discussion

No community discussion yet for this question.

Full SPLK-2003 Practice