Splunk SPLK-2003 Practice Exams
Last updated on Oct 07,2026- Exam Code: SPLK-2003
- Exam Name: Splunk SOAR Certified Automation Developer Exam
- Certification Provider: Splunk
- Latest update: Oct 07,2026
Question #51
What is the default log level for system health debug logs?
- A . INFO
- B . WARN
- C . ERROR
- D . DEBUG
Correct Answer: A
A
Explanation:
The default log level for system health debug logs in Splunk SOAR is typically set to INFO. This log level provides a balance between verbosity and relevance, offering insights into the operational status of the system without the detailed granularity of DEBUG or the limited scope of WARN and ERROR levels.
The default log level for system health debug logs is INFO. This means that only informational messages and higher severity messages (such as WARN, ERROR, or CRITICAL) are written to the log files. You can adjust the logging level for each daemon running in Splunk SOAR to help debug or troubleshoot issues. For more details, see Configure the logging levels for Splunk SOAR (On-premises) daemons.
A
Explanation:
The default log level for system health debug logs in Splunk SOAR is typically set to INFO. This log level provides a balance between verbosity and relevance, offering insights into the operational status of the system without the detailed granularity of DEBUG or the limited scope of WARN and ERROR levels.
The default log level for system health debug logs is INFO. This means that only informational messages and higher severity messages (such as WARN, ERROR, or CRITICAL) are written to the log files. You can adjust the logging level for each daemon running in Splunk SOAR to help debug or troubleshoot issues. For more details, see Configure the logging levels for Splunk SOAR (On-premises) daemons.
Question #52
Where in SOAR can a user view the JSON data for a container?
- A . In the analyst queue.
- B . On the Investigation page.
- C . In the data ingestion display.
- D . In the audit log.
Correct Answer: B
B
Explanation:
In Splunk SOAR, the Investigation page is where users can delve into the details of containers, artifacts, and actions. It provides a comprehensive view of the incident or event under investigation, including the JSON data associated with containers. This JSON data represents the structured information about the container, including its attributes, artifacts, and actions taken within the playbook. Options A, C, and D do not typically provide a direct view of the container’s JSON data, making option B the correct answer for where a user can view this information within SOAR.
A container is the top-level data structure that SOAR playbook APIs operate on. Every container is a structured JSON object which can nest more arbitrary JSON objects, that represent artifacts. A container is the top-level object against which automation is run. To view the JSON data for a container, you need to navigate to the Investigation page, which shows the details of a container, such as its name, label, owner, status, severity, and artifacts. On the Investigation page, you can click on the JSON tab, which displays the JSON representation of the container and its artifacts. Therefore, option B is the correct answer, as it states where in SOAR a user can view the JSON data for a container.
Option A is incorrect, because the analyst queue is not where a user can view the JSON data for a container, but rather where a user can view the list of containers assigned to them or their team.
Option C is incorrect, because the data ingestion display is not where a user can view the JSON data for a container, but rather where a user can view the status and configuration of the data sources that ingest data into SOAR.
Option D is incorrect, because the audit log is not where a user can view the JSON data for a container, but rather where a user can view the history of actions performed on the SOAR system, such as creating, updating, or deleting objects.
1: Understanding containers in Splunk SOAR (Cloud)
B
Explanation:
In Splunk SOAR, the Investigation page is where users can delve into the details of containers, artifacts, and actions. It provides a comprehensive view of the incident or event under investigation, including the JSON data associated with containers. This JSON data represents the structured information about the container, including its attributes, artifacts, and actions taken within the playbook. Options A, C, and D do not typically provide a direct view of the container’s JSON data, making option B the correct answer for where a user can view this information within SOAR.
A container is the top-level data structure that SOAR playbook APIs operate on. Every container is a structured JSON object which can nest more arbitrary JSON objects, that represent artifacts. A container is the top-level object against which automation is run. To view the JSON data for a container, you need to navigate to the Investigation page, which shows the details of a container, such as its name, label, owner, status, severity, and artifacts. On the Investigation page, you can click on the JSON tab, which displays the JSON representation of the container and its artifacts. Therefore, option B is the correct answer, as it states where in SOAR a user can view the JSON data for a container.
Option A is incorrect, because the analyst queue is not where a user can view the JSON data for a container, but rather where a user can view the list of containers assigned to them or their team.
Option C is incorrect, because the data ingestion display is not where a user can view the JSON data for a container, but rather where a user can view the status and configuration of the data sources that ingest data into SOAR.
Option D is incorrect, because the audit log is not where a user can view the JSON data for a container, but rather where a user can view the history of actions performed on the SOAR system, such as creating, updating, or deleting objects.
1: Understanding containers in Splunk SOAR (Cloud)
Question #53
Which of the following can the format block be used for?
- A . To generate arrays for input into other functions.
- B . To generate HTML or CSS content for output in email messages, user prompts, or comments.
- C . To generate string parameters for automated action blocks.
- D . To create text strings that merge state text with dynamic values for input or output.
Correct Answer: D
D
Explanation:
The format block in Splunk SOAR is utilized to construct text strings by merging static text with dynamic values, which can then be used for both input to other playbook blocks and output for reports, emails, or other forms of communication. This capability is essential for customizing messages, commands, or data processing tasks within a playbook, allowing for the dynamic insertion of variable data into predefined text templates. This feature enhances the playbook’s ability to present information clearly and to execute actions that require specific parameter formats.
D
Explanation:
The format block in Splunk SOAR is utilized to construct text strings by merging static text with dynamic values, which can then be used for both input to other playbook blocks and output for reports, emails, or other forms of communication. This capability is essential for customizing messages, commands, or data processing tasks within a playbook, allowing for the dynamic insertion of variable data into predefined text templates. This feature enhances the playbook’s ability to present information clearly and to execute actions that require specific parameter formats.
Question #54
Which of the following are examples of things commonly done with the Phantom REST APP
- A . Use Django queries; use curl to create a container and add artifacts to it; remove temporary lists.
- B . Use Django queries; use Docker to create a container and add artifacts to it; remove temporary lists.
- C . Use Django queries; use curl to create a container and add artifacts to it; add action blocks.
- D . Use SQL queries; use curl to create a container and add artifacts to it; remove temporary lists.
Correct Answer: C
C
Explanation:
The Phantom REST API, often interacted with through the Phantom REST APP, is a powerful tool for automating and integrating Splunk SOAR with other systems. Common uses of the Phantom REST APP include using Django queries to interact with the SOAR database, using curl commands to programmatically create containers and add artifacts to them, and configuring action blocks within playbooks for automated actions. This flexibility allows for a wide range of automation and integration possibilities, enhancing the SOAR platform’s capability to respond to security incidents and manage data.
C
Explanation:
The Phantom REST API, often interacted with through the Phantom REST APP, is a powerful tool for automating and integrating Splunk SOAR with other systems. Common uses of the Phantom REST APP include using Django queries to interact with the SOAR database, using curl commands to programmatically create containers and add artifacts to them, and configuring action blocks within playbooks for automated actions. This flexibility allows for a wide range of automation and integration possibilities, enhancing the SOAR platform’s capability to respond to security incidents and manage data.
Question #55
In addition to full backups. Phantom supports what other backup type using backup?
- A . Snapshot
- B . Incremental
- C . Partial
- D . Differential
Correct Answer: B
B
Explanation:
Splunk Phantom supports incremental backups in addition to full backups. An incremental backup is a type of backup that only copies the data that has changed since the last backup (whether that was a full backup or another incremental backup). This method is more storage-efficient than a full backup because it does not repeatedly back up the same data, reducing the amount of storage required and speeding up the backup process. Differential backups, which record the changes since the last full backup, and partial backups, which allow the selection of specific data to back up, are not standard backup types offered by Splunk Phantom according to its documentation.
B
Explanation:
Splunk Phantom supports incremental backups in addition to full backups. An incremental backup is a type of backup that only copies the data that has changed since the last backup (whether that was a full backup or another incremental backup). This method is more storage-efficient than a full backup because it does not repeatedly back up the same data, reducing the amount of storage required and speeding up the backup process. Differential backups, which record the changes since the last full backup, and partial backups, which allow the selection of specific data to back up, are not standard backup types offered by Splunk Phantom according to its documentation.
Question #56
When analyzing events, a working on a case, significant items can be marked as evidence.
Where can ail of a case’s evidence items be viewed together?
- A . Workbook page Evidence tab.
- B . Evidence report.
- C . Investigation page Evidence tab.
- D . At the bottom of the Investigation page widget panel.
Correct Answer: C
C
Explanation:
In Splunk SOAR, when working on a case and analyzing events, items marked as significant evidence are aggregated for review. These evidence items can be collectively viewed on the Investigation page under the Evidence tab. This centralized view allows analysts to easily access and review all marked evidence related to a case, facilitating a streamlined analysis process and ensuring that key information is readily available for investigation and decision-making.
C
Explanation:
In Splunk SOAR, when working on a case and analyzing events, items marked as significant evidence are aggregated for review. These evidence items can be collectively viewed on the Investigation page under the Evidence tab. This centralized view allows analysts to easily access and review all marked evidence related to a case, facilitating a streamlined analysis process and ensuring that key information is readily available for investigation and decision-making.
Question #57
Which Phantom VPE Nock S used to add information to custom lists?
- A . Action blocks
- B . Filter blocks
- C . API blocks
- D . Decision blocks
Correct Answer: C
C
Explanation:
Filter blocks are used to add information to custom lists in Phantom VPE. Filter blocks allow the user to specify a list name and a filter expression to select the data to be added to the list. Action blocks are used to execute app actions, API blocks are used to make REST API calls, and decision blocks are used to evaluate conditions and branch the playbook execution. In the Phantom Visual Playbook Editor (VPE), an API block is used to interact with various external APIs, including custom lists within Phantom. Custom lists are key-value stores that can be used to maintain state, aggregate data, or track information across multiple playbook runs. API blocks allow the playbook to make GET, POST, PUT, and DELETE requests to these lists, facilitating the addition, retrieval, update, or removal of information. This makes API blocks a versatile tool in managing custom list data within playbooks.
C
Explanation:
Filter blocks are used to add information to custom lists in Phantom VPE. Filter blocks allow the user to specify a list name and a filter expression to select the data to be added to the list. Action blocks are used to execute app actions, API blocks are used to make REST API calls, and decision blocks are used to evaluate conditions and branch the playbook execution. In the Phantom Visual Playbook Editor (VPE), an API block is used to interact with various external APIs, including custom lists within Phantom. Custom lists are key-value stores that can be used to maintain state, aggregate data, or track information across multiple playbook runs. API blocks allow the playbook to make GET, POST, PUT, and DELETE requests to these lists, facilitating the addition, retrieval, update, or removal of information. This makes API blocks a versatile tool in managing custom list data within playbooks.
Question #58
Which of the following is a reason to create a new role in SOAR?
- A . To define a set of users who have access to a special label.
- B . To define a set of users who have access to a restricted app.
- C . To define a set of users who have access to an event’s reports.
- D . To define a set of users who have access to a sensitive tag.
Correct Answer: B
B
Explanation:
In Splunk SOAR, roles serve multiple purposes, including granting users permission to access system functionality or restricting access to parts of the system1. Creating a new role is often necessary when there is a need to define a specific set of users who have access to a restricted app. This allows for granular control over who can interact with certain apps, ensuring that only authorized users can use them. While roles can also be used to manage access to labels, reports, and tags, the primary reason for creating a new role is typically related to controlling access to apps and their associated functionalities within the SOAR platform1.
Reference: Splunk SOAR documentation on managing roles and permissions1.
B
Explanation:
In Splunk SOAR, roles serve multiple purposes, including granting users permission to access system functionality or restricting access to parts of the system1. Creating a new role is often necessary when there is a need to define a specific set of users who have access to a restricted app. This allows for granular control over who can interact with certain apps, ensuring that only authorized users can use them. While roles can also be used to manage access to labels, reports, and tags, the primary reason for creating a new role is typically related to controlling access to apps and their associated functionalities within the SOAR platform1.
Reference: Splunk SOAR documentation on managing roles and permissions1.
Question #59
Which app allows a user to run Splunk queries from within Phantom?
- A . Splunk App for Phantom
- B . The Integrated Splunk/Phantom app.
- C . Phantom App for Splunk.
- D . Splunk App for Phantom Reporting.
Correct Answer: A
A
Explanation:
The Splunk App for Phantom allows users to run Splunk queries directly from within the Phantom platform. This app facilitates the integration between Splunk and Phantom, enabling users to post data to Splunk as events, update notable events, run SPL (Search Processing Language) queries, and pull events from Splunk into Phantom. By configuring the asset settings and ingest settings in the configured asset, users can leverage the full capabilities of Splunk within the Phantom environment1.
Reference: Integrating Splunk Phantom with Splunk Enterprise – TekStream Solutions
A
Explanation:
The Splunk App for Phantom allows users to run Splunk queries directly from within the Phantom platform. This app facilitates the integration between Splunk and Phantom, enabling users to post data to Splunk as events, update notable events, run SPL (Search Processing Language) queries, and pull events from Splunk into Phantom. By configuring the asset settings and ingest settings in the configured asset, users can leverage the full capabilities of Splunk within the Phantom environment1.
Reference: Integrating Splunk Phantom with Splunk Enterprise – TekStream Solutions
Question #60
How is it possible to evaluate user prompt results?
- A . Set action_result.summary. status to required.
- B . Set the user prompt to reinvoke if it times out.
- C . Set action_result. summary. response to required.
- D . Add a decision Mode
Correct Answer: C
C
Explanation:
In Splunk Phantom, user prompts are actions that require human input. To evaluate the results of a user prompt, you can set the response requirement in the action result summary. By setting action_result.summary.response to required, the playbook ensures that it captures the user’s input and can act upon it. This is critical in scenarios where subsequent actions depend on the choices made by the user in response to a prompt. Without setting this, the playbook would not have a defined way to handle the user response, which might lead to incorrect or unexpected playbook behavior.
C
Explanation:
In Splunk Phantom, user prompts are actions that require human input. To evaluate the results of a user prompt, you can set the response requirement in the action result summary. By setting action_result.summary.response to required, the playbook ensures that it captures the user’s input and can act upon it. This is critical in scenarios where subsequent actions depend on the choices made by the user in response to a prompt. Without setting this, the playbook would not have a defined way to handle the user response, which might lead to incorrect or unexpected playbook behavior.