Q: 1
What is a primary use case of lookup tables in Cortex XDR?
Options
Discussion
A. Lookup tables are for correlating outside info with internal XDR data, not for creating datasets or auto reports.
Option A Not B-lookup tables aren’t for auto-dataset creation, mostly used for enrichment.
Its A, helps you correlate external data sources with what XDR ingests. Saw similar questions covered in the official training guide and a couple practice exams.
Be respectful. No spam.
Q: 2
Which Cortex XDR feature allows hunting queries to be repeated automatically?
Options
Discussion
Its A, but if the question meant only saving queries instead of running them automatically, would it be B?
A tbh. Scheduled queries let you set XQL hunts to run over and over, none of the others automate it.
A Scheduled queries do the automation for hunting in Cortex XDR, not B. Pretty sure on this one.
Be respectful. No spam.
Q: 3
Remediation suggestions in XDR often include:
Options
Discussion
A imo, because XDR generally recommends vendor-neutral patching steps when dealing with vulnerabilities. The other options are too broad or risky for standard remediation advice. I’ve seen this style question on some practice sets, chime in if you disagree.
A
Be respectful. No spam.
Q: 4
What does “starring” an alert signify in the Cortex XDR console?
Options
Discussion
Yeah, it's B. Starring just signals it's important, doesn't do anything else automatically.
B , had something like this in a mock exam and it just flags the alert as important.
Option D
Be respectful. No spam.
Q: 5
Which of the following alert sources can provide identity-based alerts?
Options
Discussion
Option A, Saw a similar question in some exam practice, directory services is the only thing here that gives real user identity info for alerts.
A tbh
A imo. Only directory services integration (like AD) lets Cortex XDR tie alerts to specific user identities, which is what you need for true identity-based alerts. DNS or AV logs don’t map directly to user objects. Anyone see this differently?
A, Directory services integration
Be respectful. No spam.
Q: 6
What is the primary purpose of the Cortex XDR “Featured fields”?
Options
Discussion
B imo, featured fields just bubble up the most critical details for an alert or incident so analysts can spot what's important fast. Not about automating or escalating, just making triage easier. Pretty sure that's right but open to other takes if I missed something.
B tbh, had something like this in a mock. Featured fields in Cortex XDR are for fast triage highlights.
C
Be respectful. No spam.
Q: 7
When reviewing alert evidence, which of the following provides the clearest insight into the root cause of
an attack?
Options
Discussion
A tbh, since ITDR logs can sometimes reveal identity-based attack paths or compromised credentials, which could expose the initial vector. I know forensic host data (B) is solid for direct evidence, but if user creds are abused via SSO or federation, logs might be clearer on root cause in those edge cases. Disagree?
I don’t think it’s A here. Forensic data from affected hosts (B) actually shows what happened on the machine, like process trees and artifacts, so you can trace cause directly. The question wants root cause, not just detection logs.
Why does Palo Alto keep throwing random options like C into these? Its A
D imo. Clarity in the question is great, cool to see straightforward wording.
Be respectful. No spam.
Q: 8
Which two activities fall under forensic investigation in Cortex XDR? (Choose two)
Options
Discussion
Option D here. Adjusting incident scores feels like part of the investigation to me, not sure why it wouldn't count.
B and A tbh. Both are classic forensic moves in XDR since you're digging into what actually changed on endpoints and looking for signs of active threats. C and D feel more like response/tuning stuff. Not totally sure, but that's how I read it.
Does the question say "best forensic activities" or just any that apply? Official guide examples would help clarify.
Be respectful. No spam.
Q: 9
Which two benefits come from using the Query Library in Cortex XDR? (Choose two)
Options
Discussion
B , but only if the environment allows query sharing. Some setups might restrict that, so check your org's permissions.
Option A and B make sense, since Query Library is all about storing your go-to queries and letting the team reuse them. Pretty sure C and D aren't features in that part of Cortex XDR. Open to other thoughts if someone's seen different.
Don’t think it’s C or D here. A and B based on how Query Library lets you save and share XQL for teamwork.
Be respectful. No spam.
Q: 10
Why is integrating dashboards, reports, and Host Insights valuable for SOCs?
Options
Discussion
Option A matches what I've seen in similar questions. Really clear distinction in the options here.
Probably A. Integrating dashboards, reports, and Host Insights gives SOC teams full visibility of current detections, asset status, and vulnerabilities all in one place. This helps analysts correlate data faster and prioritize issues based on real risk. I’m pretty sure that’s what most official material and lab walk-throughs emphasize for Cortex XDR, but if anyone has seen something different on official practice tests or guides, let me know.
C/D? I don't think C makes sense since XQL is still needed for custom stuff, but D feels like a distractor. A is the only one that really fits for holistic SOC visibility.
Be respectful. No spam.
Question 1 of 20 · Page 1 / 2