New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Palo Alto Networks PCDRA Exam - Topic 6 Question 80 Discussion

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

What functionality of the Broker VM would you use to ingest third-party firewall logs to the Cortex Data Lake?

Show Suggested Answer Hide Answer
Suggested Answer: B

The Broker VM is a virtual machine that acts as a data broker between third-party data sources and the Cortex Data Lake. It can ingest different types of data, such as syslog, netflow, database, and pathfinder. The Syslog Collector functionality of the Broker VM allows it to receive syslog messages from third-party devices, such as firewalls, routers, switches, and servers, and forward them to the Cortex Data Lake. The Syslog Collector can be configured to filter, parse, and enrich the syslog messages before sending them to the Cortex Data Lake. The Syslog Collector can also be used to ingest logs from third-party firewall vendors, such as Cisco, Fortinet, and Check Point, to the Cortex Data Lake. This enables Cortex XDR to analyze the firewall logs and provide visibility and threat detection across the network perimeter.Reference:

Cortex XDR Data Broker VM

Syslog Collector

Supported Third-Party Firewall Vendors


by Roy at Jul 13, 2025, 02:45 PM

Limited Time Offer

25%

Off

Get Premium PCDRA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Idella
2 months ago
Not sure about that, I thought DB Collector was for databases only.
upvoted 0 times
...
Elden
2 months ago
Wait, can Pathfinder even handle firewall logs?
upvoted 0 times
...
Kimbery
3 months ago
Syslog is the standard for firewall logs, makes sense.
upvoted 0 times
...
Shayne
3 months ago
I thought Netflow Collector was the way to go?
upvoted 0 times
...
Stephania
3 months ago
Definitely using the Syslog Collector for that.
upvoted 0 times
...
Anisha
3 months ago
Pathfinder sounds familiar, but I don't think it's used for log ingestion like the Syslog Collector is.
upvoted 0 times
...
Glenna
4 months ago
I feel like the DB Collector might be used for databases, but I can't recall if it applies here.
upvoted 0 times
...
Gail
4 months ago
I remember practicing a similar question, and I think the Netflow Collector is more for network traffic rather than logs.
upvoted 0 times
...
Isaac
4 months ago
I think the Syslog Collector is the right choice for ingesting firewall logs, but I'm not entirely sure.
upvoted 0 times
...
Anika
4 months ago
I'm a bit confused on this one. I'll need to double-check the documentation to see which Broker VM functionality is best suited for this task.
upvoted 0 times
...
Thersa
4 months ago
The Syslog Collector sounds like the logical choice here. It's specifically made for ingesting log data, which is what we need to do with the firewall logs.
upvoted 0 times
...
Cory
5 months ago
Hmm, I'm not sure about this one. I'll have to review the Broker VM capabilities more closely to determine the right tool for ingesting firewall logs.
upvoted 0 times
...
Alishia
5 months ago
I think the Syslog Collector would be the best option to ingest the firewall logs. It's designed to handle log data from various sources.
upvoted 0 times
...
Tanja
6 months ago
Syslog Collector, for sure. Unless, of course, this is all just a ruse and the correct answer is 'Bake a cake and hope the firewall logs magically appear in the Cortex Data Lake'. You know how these certification exams can be.
upvoted 0 times
Madelyn
5 months ago
Syslog Collector is the correct functionality to use for ingesting third-party firewall logs.
upvoted 0 times
...
...
Freeman
6 months ago
I believe Syslog Collector is the best option because it is commonly used for collecting log data.
upvoted 0 times
...
Janine
6 months ago
Netflow Collector, huh? I don't know, that sounds more like something you'd use to monitor network traffic, not ingest firewall logs. I'm sticking with Syslog Collector.
upvoted 0 times
Nicolette
5 months ago
Yeah, I agree. Netflow Collector seems more for monitoring network traffic.
upvoted 0 times
...
Kris
5 months ago
I think Syslog Collector is the way to go for ingesting firewall logs.
upvoted 0 times
...
...
Quentin
7 months ago
I'm not sure, but I think A) Netflow Collector could also be used for this purpose.
upvoted 0 times
...
Mireya
7 months ago
Pathfinder? Really? What is this, a treasure hunt? Syslog Collector all the way, folks.
upvoted 0 times
...
Glory
7 months ago
Ooh, this is a good one. I'm going to go with the DB Collector, just to shake things up a bit. Who knows, maybe they're trying to trick us.
upvoted 0 times
...
Virgie
7 months ago
I agree with Vivan, Syslog Collector makes sense for ingesting firewall logs.
upvoted 0 times
...
Ty
7 months ago
Definitely the Syslog Collector. I mean, it's right there in the name, isn't it? Ingesting firewall logs seems like a no-brainer.
upvoted 0 times
Benedict
7 months ago
User 2: Absolutely, it's specifically designed for that purpose.
upvoted 0 times
...
Lanie
7 months ago
User 1: I agree, the Syslog Collector is the way to go for ingesting firewall logs.
upvoted 0 times
...
...
Garry
7 months ago
Hmm, this seems like a tricky one. I'm thinking the Syslog Collector might be the way to go, but I'm not 100% sure.
upvoted 0 times
Ciara
6 months ago
Yeah, I agree. That's the functionality you would use to ingest third-party firewall logs to the Cortex Data Lake.
upvoted 0 times
...
Lemuel
7 months ago
I think you're on the right track with the Syslog Collector.
upvoted 0 times
...
...
Vivan
7 months ago
I think the answer is B) Syslog Collector.
upvoted 0 times
...

Save Cancel