[Aug-2026 Newly Released] XDR-Engineer Exam Questions For You To Pass
Palo Alto Networks XDR-Engineer Exam: Basic Questions With Answers
NEW QUESTION # 21
An insider compromise investigation has been requested to provide evidence of an unauthorized removable drive being mounted on a company laptop. Cortex XDR agent is installed with default prevention agent settings profile and default extension "Device Configuration" profile. Where can an engineer find the evidence?
- A. dataset = xdr_data | filter event_type = ENUM.MOUNT and event_sub_type = ENUM.MOUNT_DRIVE_MOUNT
- B. The requested data requires additional configuration to be captured
- C. preset = device_control
- D. Check Host Inventory -> Mounts
Answer: B
Explanation:
With the default prevention agent settings profile and default Device Configuration profile, Cortex XDR does not automatically capture detailed removable media mount activity needed as forensic evidence for unauthorized removable drive mounting.
To capture this type of evidence, additional configuration is typically required, such as enabling enhanced device control monitoring/logging policies.
NEW QUESTION # 22
An attacker attempts to dump credentials by accessing LSASS memory on a Windows endpoint.
Which Cortex XDR detection capability is most likely involved?
- A. Patch Assessment
- B. Inventory Synchronization
- C. Device Profiling
- D. Process Behavioral Monitoring
Answer: D
Explanation:
Credential dumping techniques often involve abnormal access to sensitive processes such as LSASS. Behavioral monitoring detects suspicious process interactions, privilege escalation attempts, and memory access patterns commonly associated with credential theft.
NEW QUESTION # 23
An analyst remotely investigates a compromised endpoint using Live Terminal. What advantage does this provide over traditional remote desktop access?
- A. Controlled and Audited Access
- B. Eliminates Authentication Requirements
- C. Disables Endpoint Logging
- D. Automatic Privilege Escalation
Answer: A
Explanation:
Live Terminal provides secure, centrally managed, and auditable access to endpoints. It reduces exposure associated with traditional remote management services while supporting investigation and remediation activities.
NEW QUESTION # 24
Which agent setting should be enabled when creating the Device Configuration profile to block all network print jobs from all Windows endpoints?
- A. Windows Security Center integration
- B. Download source P2P settings
- C. Network location configuration
- D. Agent proxy settings
Answer: C
Explanation:
Network location configuration is required so Cortex XDR can identify network context and enforce device configuration controls for network-based printing behavior. Enabling it allows the Device Configuration profile to block network print jobs from Windows endpoints.
NEW QUESTION # 25
A Custom Prevention rule that was determined to be a false positive alert needs to be tuned. The behavior was determined to be authorized and expected on the affected endpoint. Based on the image below, which two steps could be taken? (Choose two.)
[Image description: A Custom Prevention rule configuration, assumed to trigger a Behavioral Indicator of Compromise (BIOC) alert for authorized behavior]
- A. Modify the behavioral indicator of compromise (BIOC) logic
- B. Apply an alert exclusion to the XDR behavioral indicator of compromise (BIOC) alert
- C. Apply an alert exception
- D. Apply an alert exclusion to the XDR agent alert
Answer: B,C
Explanation:
In Cortex XDR, aCustom Prevention ruleoften leveragesBehavioral Indicators of Compromise (BIOCs)to detect specific patterns or behaviors on endpoints. When a rule generates a false positive alert for authorized and expected behavior, tuning is required to prevent future false alerts. The question assumes the alert is related to a BIOC triggered by the Custom Prevention rule, and the goal is to suppress or refine the alert without disrupting security.
* Correct Answer Analysis (A, B):
* A. Apply an alert exception: Analert exceptioncan be created in Cortex XDR to suppress alerts for specific conditions, such as a particular endpoint, user, or behavior. This is a quick way to prevent false positive alerts for authorized behavior without modifying the underlying rule, ensuring the behavior is ignored in future detections.
* B. Apply an alert exclusion to the XDR behavioral indicator of compromise (BIOC) alert:
Analert exclusionspecifically targets BIOC alerts, allowing administrators to exclude certain BIOCs from triggering alerts on specific endpoints or under specific conditions. This is an effective way to tune the Custom Prevention rule by suppressing the BIOC alert for the authorized behavior.
* Why not the other options?
* C. Apply an alert exclusion to the XDR agent alert: This option is incorrect because alert exclusions are applied to BIOCs or specific alert types, not to generic"XDR agent alerts." The term "XDR agent alert" is not a standard concept in Cortex XDR for exclusions, making this option invalid.
* D. Modify the behavioral indicator of compromise (BIOC) logic: While modifying the BIOC logic could prevent false positives, it risks altering the rule's effectiveness for other endpoints or scenarios. Since the behavior is authorized only on the affected endpoint, modifying the BIOC logic is less targeted than applying an exception or exclusion and is not one of the best steps in this context.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains alert tuning: "Alert exceptions suppress alerts for specific conditions, such as authorized behaviors, without modifying rules. Alert exclusions can be applied to BIOC alerts to prevent false positives on specific endpoints" (paraphrased from the Alert Management section). The EDU-262: Cortex XDR Investigation and Responsecourse covers alert tuning, stating that "exceptions and BIOC exclusions are used to handle false positives for authorized behaviors" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "detection engineering" as a key exam topic, encompassing alert tuning and BIOC management.
References:
Palo Alto Networks Cortex XDR Documentation Portal:https://docs-cortex.paloaltonetworks.com/ EDU-262: Cortex XDR Investigation and Response Course Objectives Palo Alto Networks Certified XDR Engineer Datasheet:https://www.paloaltonetworks.com/services/education
/certification#xdr-engineer
NEW QUESTION # 26
A threat hunter suspects lateral movement activity involving compromised credentials. Which telemetry combination provides the strongest evidence during investigation?
- A. Patch Levels and Software Inventory
- B. Process and Authentication Events
- C. Endpoint Naming and Tags
- D. Asset Inventory and Disk Usage
Answer: B
Explanation:
Combining authentication telemetry with process execution data helps determine whether suspicious activity originated from stolen credentials, malicious processes, or both. This provides critical context for root-cause analysis.
NEW QUESTION # 27
How long is data kept in the temporary hot storage cache after being queried from cold storage?
- A. 24 hours, re-queried to a maximum of 7 days
- B. 1 hour, re-queried to a maximum of 24 hours
- C. 24 hours, re-queried to a maximum of 14 days
- D. 1 hour, re-queried to a maximum of 12 hours
Answer: A
Explanation:
In Cortex XDR/XSIAM, querying cold storage datasets consumes Compute Units (CU) based on the timeframe, dataset size, and query complexity. To prevent unnecessary CU consumption and speed up repetitive administrative tasks or consecutive incident lookups, Palo Alto Networks utilizes a caching architecture:
Rewarmed Data Cache: When an XQL query pulls historical data from cold storage, the retrieved logs are "rewarmed" and copied into a temporary hot storage cache.
Duration and Extensions: This rewarmed data remains instantly available in the cache for 24 hours at no additional CU cost. If you or another analyst run a subsequent query covering the same time range within that window, the 24-hour expiration timer resets. This rolling extension can be repeated up to a maximum lifetime of 7 days, after which the cache expires completely, and a brand-new retrieval from cold storage is required.
NEW QUESTION # 28
Which step is required to configure a proxy for an XDR Collector?
- A. Connect the XDR Collector to the Pathfinder
- B. Configure the proxy settings on the Cortex XDR tenant
- C. Restart the XDR Collector after configuring the proxy settings
- D. Edit the YAML configuration file with the new proxy information
Answer: D
Explanation:
TheXDR Collectorin Cortex XDR is a lightweight tool for collecting logs and events from servers and endpoints. When a proxy is required for the XDR Collector to communicate with the Cortex XDR cloud, the proxy settings must be configured in the collector's configuration file. Specifically, theYAML configuration file(e.g., config.yaml) must be edited to include the proxy details, such as the proxy server's address, port, and authentication credentials (if required).
* Correct Answer Analysis (A):To configure a proxy for the XDR Collector, the engineer mustedit the YAML configuration filewith the new proxy information. This involves adding or updating the proxy settings in the file, which the collector uses to route its traffic through the specified proxy server.
* Why not the other options?
* B. Restart the XDR Collector after configuring the proxy settings: While restarting the collector may be necessary to apply changes, it is not the primary step required to configure the proxy. The YAML file must be edited first.
* C. Connect the XDR Collector to the Pathfinder: The Pathfinder is a Cortex XDR feature for discovering endpoints, not for configuring proxy settings for the XDR Collector.
* D. Configure the proxy settings on the Cortex XDR tenant: Proxy settings for the XDR Collector are configured locally on the collector, not in the Cortex XDR tenant's web interface.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains XDR Collector configuration: "To configure a proxy for the XDR Collector, edit the YAML configuration file to include the proxy server details, such as address and port" (paraphrased from the XDR Collector Configuration section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers XDR Collector setup, stating that"proxy settings are configured by editing the collector's YAML file" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "data ingestion and integration" as a key exam topic, encompassing XDR Collector configuration.
References:
Palo Alto Networks Cortex XDR Documentation Portal:https://docs-cortex.paloaltonetworks.com/ EDU-260: Cortex XDR Prevention and Deployment Course Objectives Palo Alto Networks Certified XDR Engineer Datasheet:https://www.paloaltonetworks.com/services/education
/certification#xdr-engineer
NEW QUESTION # 29
Which two steps should be considered when configuring the Cortex XDR agent for a sensitive and highly regulated environment? (Choose two.)
- A. Enable critical environment versions
- B. Create an agent settings profile where the agent upgrade scope is maintenance releases only
- C. Create an agent settings profile, enable content auto-update, and include a delay of four days
- D. Enable minor content version updates
Answer: B,C
Explanation:
Highly regulated or sensitive environments (such as banking, healthcare, or critical infrastructure) place a strict premium on predictability, uptime, and change control to prevent unexpected disruptions or compliance violations.
Allowing major or minor agent version upgrades automatically can introduce new features or architectural changes that might conflict with proprietary software or violate strict change- management policies. Limiting the upgrade scope to maintenance releases ensures endpoints only receive critical bug fixes and stability patches, keeping the environment secure without introducing operational risk.
While security content (like threat indicators and behavioral rules) needs to be updated regularly, deploying brand-new content updates instantly across a sensitive environment carries a risk of false positives or system instability. Introducing a staging delay (such as 4 days) gives your IT or security engineering team a buffer window to test the updates on a pilot group of endpoints before they deploy globally.
NEW QUESTION # 30
During a recent internal purple team exercise, the following recommendation is given to the detection engineering team: Detect and prevent command line invocation of Python on Windows endpoints by non- technical business units. Which rule type should be implemented?
- A. Analytics Behavioral Indicator of Compromise (ABIOC)
- B. Correlation
- C. Behavioral Indicator of Compromise (BIOC)
- D. Indicator of Compromise (IOC)
Answer: C
Explanation:
The recommendation requires detecting and preventing the command line invocation of Python (e.g., python.
exe or py.exe) on Windows endpoints, specifically for non-technical business units. This involves identifying a specific behavior (command line execution of Python) and enforcing a preventive action (e.g., blocking the process). In Cortex XDR,Behavioral Indicators of Compromise (BIOCs)are used to define and detect specific patterns of behavior on endpoints, such as command line activities, and can be paired with a Restriction profileto block the behavior.
* Correct Answer Analysis (B):ABehavioral Indicator of Compromise (BIOC)rule should be implemented. The BIOC can be configured to detect the command line invocation of Python by defining conditions such as the process name (python.exe or py.exe) and the command line arguments.
For example, a BIOC rule might look for process = python.exe with a command line pattern like cmd.
exe /c python*. This BIOC can then be added to a Restriction profile to prevent the execution of Python by non-technical business units, which can be targeted by applying the profile to specific endpoint groups (e.g., those assigned to non-technical units).
* Why not the other options?
* A. Analytics Behavioral Indicator of Compromise (ABIOC): ABIOCs are analytics-driven rules generated by Cortex XDR's machine learning and behavioralanalytics, not user-defined rules. They are not suitable for creating custom detection and prevention rules like the one needed here.
* C. Correlation: Correlation rules are used to generate alerts by correlating events across multiple datasets (e.g., network and endpoint data), but they do not directly prevent behaviors like command line execution.
* D. Indicator of Compromise (IOC): IOCs are used to detect specific artifacts (e.g., file hashes, IP addresses) associated with known threats, not to detect and prevent behavioral patterns like command line execution.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains BIOC rules: "Behavioral Indicators of Compromise (BIOCs) can detect specific endpoint behaviors, such as command line invocation of processes like Python, and prevent them when added to a Restriction profile" (paraphrased from the BIOC section). TheEDU-260:
Cortex XDR Prevention and Deploymentcourse covers detection engineering, stating that "BIOCs are used to detect and block specific behaviors, such as command line executions, on Windows endpoints" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes
"detection engineering" as a key exam topic, encompassing BIOC rule creation.
References:
Palo Alto Networks Cortex XDR Documentation Portal:https://docs-cortex.paloaltonetworks.com/ EDU-260: Cortex XDR Prevention and Deployment Course Objectives Palo Alto Networks Certified XDR Engineer Datasheet:https://www.paloaltonetworks.com/services/education
/certification#xdr-engineer
NEW QUESTION # 31
Which action is being taken with the query below?
dataset = xdr_data
| fields agent_hostname, _time, _product
| comp latest as latest_time by agent_hostname, _product | join
type=inner (dataset = endpoints
| fields endpoint_name, endpoint_status, endpoint_type) as lookup
lookup.endpoint_name = agent_hostname
| filter endpoint_status = ENUM.CONNECTED
| fields agent_hostname, endpoint_status, latest_time, _product
- A. Checking for endpoints with outdated agent versions
- B. Identifying endpoints that have disconnected from the network
- C. Monitoring the latest activity of endpoints
- D. Monitoring the latest activity of connected firewall endpoints
Answer: C
Explanation:
The query pulls the latest event time for each endpoint and then joins it to the endpoints dataset to keep only endpoints with status CONNECTED. That means it is being used to monitor the most recent activity of connected endpoints, not disconnected ones or firewall devices.
NEW QUESTION # 32
What information can be used to create a dynamic endpoint group?
- A. MAC address
- B. Logged-on user
- C. Installed software
- D. IP address
Answer: D
Explanation:
Dynamic endpoint groups can be created using endpoint attributes such as IP address criteria, allowing endpoints to be automatically included when they match the defined network-based condition.
NEW QUESTION # 33
Multiple remote desktop users complain of in-house applications no longer working. The team uses macOS with Cortex XDR agents version 8.7.0, and the applications were previously allowed by disable prevention rules attached to the Exceptions Profile "Engineer-Mac." Based on the images below, what is a reason for this behavior?
- A. XDR agent version was downgraded from 8.7.0 to 8.4.0
- B. Endpoint IP address changed from 192.168.0.0 range to 192.168.100.0 range
- C. Installation type changed from VDI to Kubernetes
- D. The Cloud Identity Engine is disconnected or removed
Answer: D
Explanation:
Looking at the Endpoint Groups section, the filter for WSE Engineer 1 includes conditions referencing Cloud Identity Engine attributes (the filter text shows "domain directory" and
"annotation type = Standard"). If the Cloud Identity Engine is disconnected, endpoints can no longer be matched to that group.
As a result, the affected macOS machines fall out of the XDR Engineer 1 group, so the Engineer
1 prevention policy rule - which targets group:name = XDR Engineer 1 and applies the Engineer-Mac exceptions profile - no longer applies to them. Without that exceptions profile, the previously allowed in-house applications are blocked by default prevention rules.
NEW QUESTION # 34
An analyst uploads custom file hashes associated with a newly discovered threat actor campaign.
What occurs after the IOC is activated?
- A. Existing incidents are archived
- B. Future activity only is evaluated
- C. Prevention policies are disabled
- D. Historical and future telemetry is analyzed
Answer: D
Explanation:
IOC matching evaluates historical telemetry for previous compromises while continuously monitoring future events. This dual capability allows organizations to identify both existing infections and newly emerging threat activity.
NEW QUESTION # 35
The most recent Cortex XDR agents are being installed at a newly acquired company. A list with endpoint types (i.e., OS, hardware, software) is provided to the engineer. What should be cross- referenced for the Linux systems listed regarding the OS types and OS versions supported?
- A. Kernel Module Version Support
- B. End-of-Life Summary
- C. Content Compatibility Matrix
- D. Agent Installer Certificate
Answer: A
Explanation:
For Linux systems specifically, the critical compatibility check is the Kernel Module Version Support document. Unlike Windows or macOS, Linux has significant variability in kernel versions across distributions, and the Cortex XDR agent relies on kernel modules that must be compatible with the specific kernel version running on each endpoint.
NEW QUESTION # 36
What is the earliest time frame an alert could be automatically generated once the conditions of a new correlation rule are met?
- A. 5 minutes or less
- B. Between 30 and 45 minutes
- C. Immediately
- D. Between 10 and 20 minutes
Answer: A
Explanation:
In Cortex XDR,correlation rulesare used to detect specific patterns or behaviors by analyzing ingested data and generating alerts when conditions are met. The time frame for alert generation depends on the data ingestion pipeline, the processing latency of the Cortex XDR backend, and the rule's evaluation frequency.
For a new correlation rule, once the conditions are met (i.e., the relevant events are ingested and processed), Cortex XDR typically generates alerts within a short time frame, often5 minutes or less, due to its near-real- time processing capabilities.
* Correct Answer Analysis (C):Theearliest time framefor an alert to be generated is5 minutes or less, as Cortex XDR's architecture is designed to process and correlate events quickly. This accounts for the time to ingest data, evaluate the correlation rule, and generate the alert in the system.
* Why not the other options?
* A. Between 30 and 45 minutes: This time frame is too long for Cortex XDR's near-real-time detection capabilities. Such delays might occur in systems with significant processing backlogs, but not in a properly configured Cortex XDR environment.
* B. Immediately: While Cortex XDR is fast, "immediately" implies zero latency, which is not realistic due to data ingestion, processing, and rule evaluation steps. A small delay (within 5 minutes) is expected.
* D. Between 10 and 20 minutes: This is also too long for the earliest possible alert generation in Cortex XDR, as the system is optimized for rapid detection and alerting.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains correlation rule processing: "Alerts are generated within 5 minutes or less after the conditions of a correlation rule are met, assuming data is ingested and processed in near real-time" (paraphrased from the Correlation Rules section). TheEDU-262: Cortex XDR Investigation and Responsecourse covers detection engineering, stating that "Cortex XDR's correlation engine processes rules and generates alerts typically within a few minutes of event ingestion" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "detection engineering" as a key exam topic, encompassing correlation rule alert generation.
References:
Palo Alto Networks Cortex XDR Documentation Portal:https://docs-cortex.paloaltonetworks.com/ EDU-262: Cortex XDR Investigation and Response Course Objectives Palo Alto Networks Certified XDR Engineer Datasheet:https://www.paloaltonetworks.com/services/education
/certification#xdr-engineer
NEW QUESTION # 37
A signed application from a trusted vendor unexpectedly begins spawning command shells and downloading remote payloads. Which detection method is most effective?
- A. Signature Reputation Only
- B. Behavioral Analytics
- C. Endpoint Enumeration
- D. Asset Tag Validation
Answer: B
Explanation:
Behavioral analytics focuses on suspicious actions rather than software reputation. Even trusted or signed applications can be compromised, making behavioral detection essential for identifying supply-chain and living-off-the-land attacks.
NEW QUESTION # 38
What is a benefit of ingesting and forwarding Palo Alto Networks NGFW logs to Cortex XDR?
- A. Enabling additional analysis through enhanced application logging
- B. Blocking network traffic based on Cortex XDR detections
- C. Automated downloading of malware signatures from the NGFW
- D. Sending endpoint logs to the NGFW for analysis
Answer: A
Explanation:
When Palo Alto Networks NGFW logs are ingested into Cortex XDR, they provide additional network and application context that enhances XDR's analytics and detection capabilities. The firewall logs can be correlated with endpoint, user, and network activity, enabling enhanced application logging and deeper analysis across the environment.
NEW QUESTION # 39
When using Kerberos as the authentication method for Pathfinder, which two settings must be validated on the DNS server? (Choose two.)
- A. AD DS-integrated zones
- B. Reverse DNS records
- C. Reverse DNS zone
- D. DNS forwarders
Answer: B,C
Explanation:
Pathfinderin Cortex XDR is a tool for discovering unmanaged endpoints in a network, often using authentication methods likeKerberosto access systems securely. Kerberos authentication relies heavily on DNS for resolving hostnames and ensuring proper communication between clients, servers, and the Kerberos Key Distribution Center (KDC). Specific DNS settings must be validated to ensure Kerberos authentication works correctly for Pathfinder.
* Correct Answer Analysis (B, C):
* B. Reverse DNS zone: Areverse DNS zoneis required to map IP addresses to hostnames (PTR records), which Kerberos uses to verify the identity of servers and clients. Without a properly configured reverse DNS zone, Kerberos authentication may fail due to hostname resolution issues.
* C. Reverse DNS records:Reverse DNS records(PTR records) within the reverse DNS zone must be correctly configured for all relevant hosts. These records ensure that IP addresses resolve to the correct hostnames, which is critical for Kerberos to authenticate Pathfinder's access to endpoints.
* Why not the other options?
* A. DNS forwarders: DNS forwarders are used to route DNS queries to external servers when a local DNS server cannot resolve them. While useful for general DNS resolution, they are not specifically required for Kerberos authentication or Pathfinder.
* D. AD DS-integrated zones: Active Directory Domain Services (AD DS)-integrated zones enhance DNS management in AD environments, but they are not strictly required for Kerberos authentication. Kerberos relies on proper forward and reverse DNS resolution, not AD-specific DNS configurations.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains Pathfinder configuration: "For Kerberos authentication, ensure that the DNS server has a properly configured reverse DNS zone and reverse DNS records to support hostname resolution" (paraphrased from the Pathfinder Configuration section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers Pathfinder setup, stating that "Kerberos requires valid reverse DNS zones and PTR records for authentication" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "planning and installation" as a key exam topic, encompassing Pathfinder authentication settings.
References:
Palo Alto Networks Cortex XDR Documentation Portal:https://docs-cortex.paloaltonetworks.com/ EDU-260: Cortex XDR Prevention and Deployment Course Objectives Palo Alto Networks Certified XDR Engineer Datasheet:https://www.paloaltonetworks.com/services/education
/certification#xdr-engineer
NEW QUESTION # 40
When onboarding a Palo Alto Networks NGFW to Cortex XDR, what must be done to confirm that logs are being ingested successfully after a device is selected and verified?
- A. Retrieve device certificate from NGFW dashboard
- B. Conduct an XQL query for NGFW log data
- C. Wait for an incident that involves the NGFW to populate
- D. Confirm that the selected device has a valid certificate
Answer: B
Explanation:
When onboarding aPalo Alto Networks Next-Generation Firewall (NGFW)to Cortex XDR, the process involves selecting and verifying the device to ensure it can send logs to Cortex XDR. After this step, confirming successful log ingestion is critical to validate the integration. The most direct and reliable method to confirm ingestion is to query the ingested logs usingXQL (XDR Query Language), which allows the engineer to search for NGFW log data in Cortex XDR.
* Correct Answer Analysis (A):Conduct an XQL query for NGFW log datais the correct action.
After onboarding, the engineer can run an XQL query such as dataset = panw_ngfw_logs | limit 10 to check if NGFW logs are present in Cortex XDR. This confirms that logs are being successfully ingested and stored in the appropriate dataset, ensuring the integration is working as expected.
* Why not the other options?
* B. Wait for an incident that involves the NGFW to populate: Waiting for an incident is not a reliable or proactive method to confirm log ingestion. Incidents depend on detection rules and may not occur immediately, even if logs are beingingested.
* C. Confirm that the selected device has a valid certificate: While a valid certificate is necessary during the onboarding process (e.g., for secure communication), this step is part of the verification process, not a method to confirm log ingestion after verification.
* D. Retrieve device certificate from NGFW dashboard: Retrieving the device certificate from the NGFW dashboard is unrelated to confirming log ingestion in Cortex XDR. Certificates are managed during setup, not for post-onboarding validation.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains NGFW log ingestion validation: "To confirm successful ingestion of Palo Alto Networks NGFW logs, run an XQL query (e.g., dataset = panw_ngfw_logs) to verify that log data is present in Cortex XDR" (paraphrased from the Data Ingestion section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers NGFW integration, stating that "XQL queries are used to validate that NGFW logs are being ingested after onboarding" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "data ingestion and integration" as a key exam topic, encompassing log ingestion validation.
References:
Palo Alto Networks Cortex XDR Documentation Portal:https://docs-cortex.paloaltonetworks.com/ EDU-260: Cortex XDR Prevention and Deployment Course Objectives Palo Alto Networks Certified XDR Engineer Datasheet:https://www.paloaltonetworks.com/services/education
/certification#xdr-engineer
NEW QUESTION # 41
Which method will drop undesired logs and reduce the amount of data being ingested?
- A. [COLLECT:vendor="vendor", product="product", target_dataset="", no_hit=drop] * drop _raw_log contains "undesired logs";
- B. [INGEST:vendor="vendor", product="product",
target_dataset="vendor_product_raw",no_hit=drop] * filter _raw_log not contains "undesired logs"; - C. [COLLECT:vendor="vendor", product="product", target_brokers="", no_hit=drop] * drop _raw_log contains "undesired logs";
- D. [INGEST:vendor="vendor", product="product", target_brokers="vendor_product_raw", no_hit=keep] * filter _raw_log not contains "undesired logs";
Answer: B
Explanation:
In Palo Alto Networks Cortex XDR/XSIAM, parsing rules use a specialized variant of XQL to process, normalize, and selectively filter incoming raw logs before they consume storage licenses in the cloud data lake.
The Core Block Structure: Custom parsing rules must utilize the INGEST declaration block to route log traffic into an active repository (specified via target_dataset). The COLLECT block (seen in options A and C) is structurally incorrect for this parsing workflow.
The Filtering Mechanism: The statement filter _raw_log not contains "undesired logs"; evaluates incoming logs and keeps only the lines that do not match your noisy or unnecessary signatures.
Handling Dropped Traffic via no_hit: The parameter no_hit=drop is the critical setting here. It specifies that any log lines that are completely filtered out or fail to match the parsing logic conditions should be permanently dropped at the ingestion stage, successfully preventing them from being written to the database and reducing your ingestion volume metrics.
NEW QUESTION # 42
An organization wants endpoints automatically isolated when high-confidence ransomware activity is detected. Which Cortex XDR capability provides this automation?
- A. Response Action Rules
- B. Dynamic Host Inventory
- C. IOC Expiration Policies
- D. Local Analysis Engine
Answer: A
Explanation:
Response Action Rules automate remediation activities based on predefined criteria. Security teams can automatically isolate devices, collect forensic evidence, or terminate processes when specific threat conditions are satisfied.
NEW QUESTION # 43
......
New 2026 Realistic Free Palo Alto Networks XDR-Engineer Exam Dump Questions and Answer: https://examtorrent.actual4test.com/XDR-Engineer_examcollection.html