A. The ability to ingest Splunk notable events into SOAR.

B. The ability to display results as Splunk dashboards within SOAR.

C. The ability to run more complex reports on SOAR activities.

D. The ability to automate Splunk searches within SOAR.

A. Add an action block to a playbook canvas area.

B. From the Apps menu, click the supported actions dropdown for each app.

C. Search the Apps category in the global search field.

D. In the visual playbook editor, click Active and click the Available App Actions dropdown.

A. Content that existed before configuring external search must be backed up on SOAR and restored on the Splunk search head.

B. The user configured on the SOAR side with Phantomsearch capability is not enabled on Splunk.

C. The existing content indexes on the SOAR server need to be re-indexed to migrate them to Splunk.

D. The remote Splunk search head is currently offline.

A. Easier playbook maintenance.

B. Eliminates any need to use Python code.

C. The Visual Playbook Editor is the only way to generate user prompts.

D. Supports Python or Javascript.

A. Amount of storage.

B. Amount of memory.

C. Number of processors.

D. Bandwidth of network.

A. Place restricted playbooks in a second source repository that has restricted access.

B. Add a filter block to al restricted playbooks that Titters for runRole - "Admin''.

C. Make sure the Execute Playbook capability is removed from al roles except admin.

D. Add a tag with restricted access to the restricted playbooks.