PCSAE Practice Exam Questions with Answers Palo Alto Networks Certified Security Automation Engineer Certification

Lists

Jobs

Pre-processing rules

Exclusion List

Section headers

Rows

Canvas

Cards

Settings > About > Troubleshooting, in the main host account. Each host has a System Diagnostics page.

Settings > Advanced > System Diagnostics, in the main host account. Each host has a System Diagnostics page.

Settings > Account Management > Hosts, in the main host account. Each host has a System Diagnostics page.

Settings > About > System Diagnostics, in the main host account. Each host has a System Diagnostics page.

Define a task in a playbook to generate an incident report before the closure occurs

Manually create an ‘Incident Report’

Configure post-processing using a script

Create an ‘Incident Report’ from the Reports page

Create widget of type Line, check ‘Display Trend’ and define as 7 days ago

Create a custom widget using a new incident query

Create widget of type Number, check ‘Display Trend’ and define as 7 days ago

Create a custom widget using a script

/var/lib/demisto

/tmp/log/demisto

/usr/local/demisto

/var/log/demisto

The new job form changes based on the threat intel feed integration configuration

The new job form can be edited from the Indicator Feed incident type editor

The new job form for a threat intel feed job cannot be edited

The new job form can be edited from the threat intel feeds integration settings

Store incident information in JSON format

Store incident information in XML format

Pass data between playbook tasks

Pass data between to-do tasks

Add the playbook to the integration’s settings

Select ‘Run playbook automatically’ from the incident type settings

Add the !startinvestigation automation to the beginning of the playbook

Select ‘Run playbook automatically’ from the integration settings

Define input key in the subplaybook task. Map context values to pull from parent playbook.

The output of the previous task automatically becomes the input of the subplaybook.

Map inputs and outputs to the parent playbook and the subplaybook will use the same values.

Open the subplaybook and add inputs or outputs in the Playbook triggered task.

In the instance settings, enable the fetch incidents parameter and wait for one minute

Create a one task playbook with a fetch-incident command

execute !-fetch

execute !-fetch

The administrator will receive a notification that there is both a Classifier and Incident Type set for that integration instance.

The Incident Type will be ignored, and incoming incidents will be classified according to the Classifier.

The Classifier will be ignored, and incoming incidents will be classified according to the Incident Type.

Both the Classifier and Incident Type will classify incoming incidents.

Read/Write from context data

Over war room results

Input from the indicator page

Directly from a previous task

The post-processing tag must be added to the automation

Post-processing scripts must be added at the end of playbooks

Post-processing scripts must be added from the Incident Type editor

Post-processing scripts must be added from the Post-Process Rules editor

Manually directly from the War Room with the Actions drop-down

From the Notes section (mark as entry icon)

Manually from the playbook task (mark as entry icon)

Automatically from playbook tasks when the option is selected on the Advanced tab

By running the command !MarkAsEvidence

Get csvList.value where csvList.value equals test [from previous tasks]

Get csvList.value where csvList.value equals ${test} [from previous tasks]

Get csvList.value where csvList.value equals test {}[from previous tasks]

Get csvList.value where csvList.value equals test [as value]

Get csvList.value where csvList.value equals ${test} [as value]

The commands must return a proper result to the war room for the analysts to understand

The code may not be written to XSOAR standards

The integrations are locked and cannot be edited with additional commands

The custom integration will not be maintained and updated by XSOAR content team