Pass the Paloalto Networks PSE-Cortex Professional PSE-Cortex-Pro-24 Questions and answers with ValidTests

phishing

either

ServiceNow

neither

incorrect instance name

incorrect Username and Password

incorrect appliance port

incorrect server URL

Gather information about the word processing applications and run them on a Windows XP SP3 VM Determine if any of the applications are vulnerable and run the exploit with an exploitation tool

Run word processing exploits in a latest version of Windows VM in a controlled and isolated environment. Document indicators of compromise and compare to Traps protection capabilities

Run a known 2015 flash exploit on a Windows XP SP3 VM. and run an exploitation tool that acts as a listener Use the results to demonstrate Traps capabilities

Prepare the latest version of Windows VM Gather information about the word processing applications, determine if some of them are vulnerable and prepare a working exploit for at least one of them Execute with an exploitation tool

Must be in a Load-Balancing group with at least another 3 members

It must have port 443 open to allow the Demisto Server to establish a connection

Can be used separately as an engine, only if connected to the Demisto Server directly

Cannot be used separately and does not appear in the in the engines drop-down menu when configuring an integration instance

Create two instances of the email integration and classify one instance as ingesting incidents of type phishing and the other as ingesting incidents of type onboarding.

Use an incident classifier based on a field in each type of email to classify those containing "Phish Alert" in the subject as phishing and those containing "Onboard Request" as onboarding.

Create a playbook to process and determine incident type based on content of the email.

Use machine learning (ML) to determine incident type.

Threat, Config, System, Data

Threat, Config, System, Analytic

Threat, Monitor. System, Analytic

Threat, Config, Authentication, Analytic

Uncommon Local Scheduled Task Creation

Malware

New Administrative Behavior

DNS Tunneling

The modified scnpt was run in the wrong Docker image

The modified script required a different parameter to run successfully.

The dictionary was defined incorrectly in the second script.

The modified script attempted to access a dictionary key that did not exist in the dictionary named "data”

Playbook triggers

Correlation rules

Incident scoring

Data model rules

When set to private, task outputs do not automatically get written to the root context

When set to private, task outputs automatically get written to the root context

When set to global, allows parallel task execution.

When set to global, sub-playbook tasks do not have access to the root context