Which of the following roles is appropriate for a Splunk SOAR account that will only be used to execute automated tasks?

Question

Options

• AService Account
• BAutomation Engineer
• CNon-Human
• DAutomation

• A
  4% (1)
• B
  4% (1)
• D
  93% (25)

Explanation

Automation is the designated Splunk SOAR role built specifically for non-interactive, programmatic accounts - it grants the permissions needed to execute playbooks and automated actions without requiring human login capabilities, making it the correct fit for any account running automated tasks.

Why the others are wrong:

• A. Service Account - a generic IT/infrastructure term for non-human accounts, but it is not an actual role name within Splunk SOAR's role-based access control system.
• B. Automation Engineer - this is a job title or persona, not a Splunk SOAR platform role; it doesn't exist in SOAR's role configuration.
• C. Non-Human - descriptive of the account's purpose but not a valid Splunk SOAR role; SOAR doesn't use this label for access control.

Memory tip: Think "match the tool to the task" - Splunk SOAR names its role exactly after the function: Automation role = automated tasks. If a human logs in interactively, they get Analyst or Administrator. If code runs the account, it gets Automation.

No community discussion yet for this question.