How can parent and child playbooks pass information to each other?
A.
The parent can pass arguments to the child when called, and the child can return values from the end block.
B.
The parent can pass arguments to the child when called, but the child can only pass values back as new artifacts in the event.
C.
The parent must create a new artifact in the event named arg_xxx, and the child must return values by creating artifacts with the naming convention return_xxx.
D.
The parent must create a new artifact in the event named return_xxx, and the child must return values by creating artifacts with the naming convention arg_xxx.
In Splunk SOAR, parent and child playbooks can pass information between each other using arguments. The parent playbook can pass specific arguments to the child playbook when it is called, enabling the child playbook to utilize these values in its execution. Once the child playbook finishes its execution, it can return values through the end block. This mechanism allows for efficient and structured communication between parent and child playbooks, enabling complex, multi-step automation workflows.
Other options are incorrect because creating artifacts with specific naming conventions is not necessary for passing information between playbooks, and artifacts are not used for argument or result passing between playbooks in this manner.
References:
Splunk SOAR Documentation: Playbook Development Guide.
Splunk SOAR Best Practices: Parent and Child Playbooks Communication.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit