Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Palo Alto Networks Exam PCDRA Topic 9 Question 58 Discussion

Actual exam question for Palo Alto Networks's PCDRA exam
Question #: 58
Topic #: 9
[All PCDRA Questions]

What are two purposes of ''Respond to Malicious Causality Chains'' in a Cortex XDR Windows Malware profile? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: C

The Wildfire analysis file size limit for Windows PE files is 100MB. Windows PE files are executable files that run on the Windows operating system, such as .exe, .dll, .sys, or .scr files. Wildfire is a cloud-based service that analyzes files and URLs for malicious behavior and generates signatures and protections for them. Wildfire can analyze various file types, such as PE, APK, PDF, MS Office, and others, but each file type has a different file size limit. The file size limit determines the maximum size of the file that can be uploaded or forwarded to Wildfire for analysis. If the file size exceeds the limit, Wildfire will not analyze the file and will return an error message.

According to the Wildfire documentation1, the file size limit for Windows PE files is 100MB. This means that any PE file that is larger than 100MB will not be analyzed by Wildfire. However, the firewall can still apply other security features, such as antivirus, anti-spyware, vulnerability protection, and file blocking, to the PE file based on the security policy settings.The firewall can also perform local analysis on the PE file using the Cortex XDR agent, which uses machine learning models to assess the file and assign it a verdict2.


WildFire File Size Limits: This document provides the file size limits for different file types that can be analyzed by Wildfire.

Local Analysis: This document explains how the Cortex XDR agent performs local analysis on files that cannot be sent to Wildfire for analysis.

Contribute your Thoughts:

Lashaunda
2 days ago
Ooh, this is a tricky one. I'm going to go with A and D, but I'm not totally confident. Maybe I should have spent more time studying the Cortex XDR documentation instead of binge-watching that new TV show...
upvoted 0 times
...
Ezekiel
5 days ago
Haha, I love how these options are all about 'automatically' doing something. I guess the Cortex XDR team really wants this to be a hands-off kind of deal. 'Malicious activity? No problem, we'll just take care of it!'
upvoted 0 times
...
Hubert
6 days ago
I'm torn between B and C. Killing processes and terminating threads could also be effective in disrupting the malicious activity. But I'm not sure if those are the primary purposes of this feature.
upvoted 0 times
...
Rodolfo
8 days ago
I'm not sure about killing processes, but I think terminating threads and blocking IP addresses are important for stopping the malware.
upvoted 0 times
...
Desmond
10 days ago
A and D seem like the most logical options here. Automatically closing connections and blocking IP addresses involved in malicious traffic seems like a good way to respond to these malicious chains.
upvoted 0 times
...
Ciara
11 days ago
I agree with Denna. It helps stop the malicious activity by cutting off communication and blocking the source.
upvoted 0 times
...
Denna
13 days ago
I think the purpose is to automatically close connections and block IP addresses.
upvoted 0 times
...

Save Cancel