[Feb-2026] Pass Palo Alto Networks XDR-Engineer Exam in First Attempt Guaranteed! [Q21-Q41]

[Feb-2026] Pass Palo Alto Networks XDR-Engineer Exam in First Attempt Guaranteed!

Full XDR-Engineer Practice Test and 52 unique questions with explanations waiting just for you, get it now!

NEW QUESTION # 21
An engineer is building a dashboard to visualize the number of alerts from various sources. One of the widgets from the dashboard is shown in the image below:

The engineer wants to configure a drilldown on this widget to allow dashboard users to select any of the alert names and view those alerts with additional relevant details. The engineer has configured the following XQL query to meet the requirement:
dataset = alerts
| fields alert_name, description, alert_source, severity, original_tags, alert_id, incident_id
| filter alert_name =
| sort desc _time
How will the engineer complete the third line of the query (filter alert_name =) to allow dynamic filtering on a selected alert name?

A. $x_axis.name
B. $x_axis.value
C. $y_axis.name
D. $y_axis.value

Answer: B

Explanation:
In Cortex XDR, dashboards and widgets supportdrilldownfunctionality, allowing users to click ona widget element (e.g., an alert name in a bar chart) to view detailed data filtered by the selected value. This is achieved usingXQL (XDR Query Language)queries with dynamic variables that reference the clicked element's value. In the provided XQL query, the engineer wants to filter alerts based on thealert_nameselected in the widget.
The widget likely displays alert names along thex-axis(e.g., in a bar chart where each bar represents an alert name and its count). When a user clicks on an alert name, the drilldown query should filter the dataset to show only alerts matching that selectedalert_name. In XQL, dynamic filtering for drilldowns uses variables like $x_axis.value to capture the value of the clicked element on the x-axis.
* Correct Answer Analysis (B):The variable$x_axis.valueis used to reference the value of the x-axis element (in this case, thealert_name) selected by the user. Completing the query with filter alert_name
= $x_axis.value ensures that the drilldown filters the alerts dataset to show only those records where the alert_namematches the clicked value.
* Why not the other options?
* A. $y_axis.value: This variable refers to the value on the y-axis, which typically represents a numerical value (e.g., the count of alerts) in a chart, not the categoricalalert_name.
* C. $x_axis.name: This is not a valid XQL variable for drilldowns. XQL uses $x_axis.value to capture the selected value, not $x_axis.name.
* D. $y_axis.name: This is also not a valid XQL variable, and the y-axis is not relevant for filtering byalert_name.
Exact Extract or Reference:
TheCortex XDR Documentation Portalin theXQL Reference Guideexplains drilldown configuration: "To filter data based on a clicked widget element, use $x_axis.value to reference the value of the x-axis category selected by the user" (paraphrased from the Dashboards and Widgets section). TheEDU-262: Cortex XDR Investigation and Responsecourse covers dashboard creation and XQL, noting that "drilldown queries use variables like $x_axis.value to dynamically filter based on user selections" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetlists "dashboards and reporting" as a key exam topic, including configuring interactive widgets.
References:
Palo Alto Networks Cortex XDR Documentation Portal: XQL Reference Guide (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 # 22
A query is created that will run weekly via API. After it is tested and ready, it is reviewed in the Query Center. Which available column should be checked to determine how many compute units will be used when the query is run?

A. Simulated Compute Units
B. Compute Unit Usage
C. Query Status
D. Compute Unit Quota

Answer: B

Explanation:
In Cortex XDR, theQuery Centerallows administrators to manage and reviewXQL (XDR Query Language) queries, including those scheduled to run via API. Each query consumescompute units, a measure of the computational resources required to execute the query. To determine how many compute units a query will use, theCompute Unit Usagecolumn in the Query Center provides the actual or estimated resource consumption based on the query's execution history or configuration.
* Correct Answer Analysis (B):TheCompute Unit Usagecolumn in the Query Center displays the number of compute units consumed by a query when it runs. For a tested and ready query, this column provides the most accurate information on resource usage, helping administrators plan for API-based executions.
* Why not the other options?
* A. Query Status: The Query Status column indicates whether the query ran successfully, failed, or is pending, but it does not provide information on compute unit consumption.
* C. Simulated Compute Units: While some systems may offer simulated estimates, Cortex XDR' s Query Center does not have a "Simulated Compute Units" column. The actual usage is tracked in Compute Unit Usage.
* D. Compute Unit Quota: The Compute Unit Quota refers to the total available compute units for the tenant, not the specific usage of an individual query.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains Query Center functionality: "The Compute Unit Usage column in the Query Center shows the compute units consumed by a query, enabling administrators to assess resource usage for scheduled or API-based queries" (paraphrased from the Query Center section). TheEDU-
262: Cortex XDR Investigation and Responsecourse covers query management, stating that "Compute Unit Usage provides details on the resources used by each query in the Query Center" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "maintenance and troubleshooting" as a key exam topic, encompassing query resource 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 # 23
In addition to using valid authentication credentials, what is required to enable the setup of the Database Collector applet on the Broker VM to ingest database activity?

A. Valid SQL query targeting the desired data
B. Access to the database transaction log
C. Database schema exported in the correct format
D. Access to the database audit log

Answer: A

Explanation:
TheDatabase Collector appleton the Broker VM in Cortex XDR is used to ingest database activity logs by querying the database directly. To set up the applet, valid authentication credentials (e.g., username and password) are required to connect to the database. Additionally, avalid SQL querymust be provided to specify the data to be collected, such as specific tables, columns, or events (e.g., login activity or data modifications).
* Correct Answer Analysis (A):Avalid SQL query targeting the desired datais required to configure the Database Collector applet. The query defines which database records or events are retrieved and sent to Cortex XDR for analysis. This ensures the applet collects only the relevant data, optimizing ingestion and analysis.
* Why not the other options?
* B. Access to the database audit log: While audit logs may contain relevant activity, the Database Collector applet queries the database directly using SQL, not by accessing audit logs.
Audit logs are typically ingested via other methods, such as Filebeat or syslog.
* C. Database schema exported in the correct format: The Database Collector does not require an exported schema. The SQL query defines the data structure implicitly, and Cortex XDR maps the queried data to its schema during ingestion.
* D. Access to the database transaction log: Transaction logs are used for database recovery or replication, not for direct data collection by the Database Collector applet, which relies on SQL queries.
Exact Extract or Reference:
TheCortex XDR Documentation Portaldescribes the Database Collector applet: "To configure the Database Collector, provide valid authentication credentials and a valid SQL query to retrieve the desired database activity" (paraphrased from the Broker VM Applets section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers data ingestion, stating that "the Database Collector applet requires a SQL query to specify the data to ingest from the database" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "data ingestion and integration" as a key exam topic, encompassing Database 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 # 24
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. Conduct an XQL query for NGFW log data
B. Retrieve device certificate from NGFW dashboard
C. Confirm that the selected device has a valid certificate
D. Wait for an incident that involves the NGFW to populate

Answer: A

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 # 25
During deployment of Cortex XDR for Linux Agents, the security engineering team is asked to implement memory monitoring for agent health monitoring. Which agent service should be monitored to fulfill this request?

A. clad
B. pyxd
C. pmd
D. dypdng

Answer: C

Explanation:
Cortex XDR agents on Linux consist of several services that handle different aspects of agent functionality, such as event collection, policy enforcement, and health monitoring.Memory monitoringfor agent health involves tracking the memory usage of the agent's core processes to ensure they are operating within acceptable limits, which is critical for maintaining agent stability and performance. Thepmd(Process Monitoring Daemon) service is responsible for monitoring the agent's health, including memory usage, on Linux systems.
* Correct Answer Analysis (D):Thepmdservice should be monitored to fulfill the request for memory monitoring. The Process Monitoring Daemon tracks the Cortex XDR agent's resource usage, including memory consumption, and reports health metrics to the console. Monitoring this service ensures the agent remains healthy and can detect issues like memory leaks or excessive resource usage.
* Why not the other options?
* A. dypdng: This is not a valid Cortex XDR service on Linux. It appears to be a typo or a misnamed service.
* B. clad: The clad service (Cortex Linux Agent Daemon) is responsible for core agent operations, such as communication with the Cortex XDR tenant, but it is not specifically focused on memory monitoring for health purposes.
* C. pyxd: The pyxd service handles Python-based components of the agent, such asscript execution for certain detections, but it is not responsible for memory monitoring or agent health.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains Linux agent services: "The pmd (Process Monitoring Daemon) service on Linux monitors agent health, including memory usage, to ensure stable operation" (paraphrased from the Linux Agent Deployment section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers Linux agent setup, stating that "pmd is the service to monitor for agent health, including memory usage, on Linux systems" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "planning and installation" as a key exam topic, encompassing Linux agent deployment and monitoring.
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 # 26
What happens when the XDR Collector is uninstalled from an endpoint by using the Cortex XDR console?

A. The associated configuration data is removed from the Action Center immediately after uninstallation
B. The machine status remains active until manually removed, and the configuration data is retained for up to seven days
C. The files are removed immediately, and the machine is deleted from the system without any retention period
D. It is uninstalled during the next heartbeat communication, machine status changes to Uninstalled, and the configuration data is retained for 90 days

Answer: D

Explanation:
TheXDR Collectoris a lightweight agent in Cortex XDR used to collect logs and events from endpoints or servers. When uninstalled via the Cortex XDR console, the uninstallation process is initiated remotely, but the actual removal occurs during the endpoint's next communication with the Cortex XDR tenant, known as the heartbeat. The heartbeat interval is typically every few minutes, ensuring timely uninstallation. After uninstallation, the machine's status in the console updates, and associated configuration data is retained for a specific period to support potential reinstallation or auditing.
* Correct Answer Analysis (C):When the XDR Collector is uninstalled using the Cortex XDR console, it is uninstalled during the next heartbeat communication, themachine status changes to Uninstalled, and theconfiguration data is retained for 90 days. This retention period allows administrators to review historical data or reinstall the collector if needed, after which the data is permanently deleted.
* Why not the other options?
* A. The files are removed immediately, and the machine is deleted from the system without any retention period: Uninstallation is not immediate; it occurs at the next heartbeat.
Additionally, Cortex XDR retains configuration data for a period, not deleting it immediately.
* B. The machine status remains active until manually removed, and the configuration data is retained for up to seven days: The machine status updates to Uninstalled automatically, not requiring manual removal, and the retention period is 90 days, not seven days.
* D. The associated configuration data is removed from the Action Center immediately after uninstallation: Configuration data is retained for 90 days, not removed immediately, and the Action Center is not the primary location for this data.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains XDR Collector uninstallation: "Whenuninstalled via the console, the XDR Collector is removed at the next heartbeat, the machine status changes to Uninstalled, and configuration data is retained for 90 days" (paraphrased from the XDR Collector Management section). The EDU-260: Cortex XDR Prevention and Deploymentcourse covers collector management, stating that
"uninstallation occurs at the next heartbeat, with a 90-day retention period for configuration data" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes
"post-deployment management and configuration" as a key exam topic, encompassing XDR Collector uninstallation.
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 # 27
A new parsing rule is created, and during testing and verification, all the logs for which field data is to be parsed out are missing. All the other logs from this data source appear as expected. What may be the cause of this behavior?

A. The XDR Collector is dropping the logs
B. The Broker VM is offline
C. The parsing rule corrupted the database
D. The filter stage is dropping the logs

Answer: D

Explanation:
In Cortex XDR,parsing rulesare used to extract and normalize fields from raw log data during ingestion, ensuring that the data is structured for analysis and correlation. The parsing process includes stages such as filtering, parsing, and mapping. If logs for which field data is to be parsed out are missing, while other logs from the same data source are ingested as expected, the issue likely lies within the parsing rule itself, specifically in the filtering stage that determines which logs are processed.
* Correct Answer Analysis (C):The filter stage is dropping the logsis the most likely cause. Parsing rules often include afilter stagethat determines which logs are processed based on specific conditions (e.
g., log content, source, or type). If the filter stage of the new parsing rule is misconfigured (e.g., using an incorrect condition like log_type != expected_type or a regex that doesn't match the logs), it may drop the logs intended for parsing, causing them to be excluded from the ingestion pipeline. Since other logs from the same data source are ingested correctly, the issue is specific to the parsing rule's filter, not a broader ingestion problem.
* Why not the other options?
* A. The Broker VM is offline: If the Broker VM were offline, it would affect all log ingestion from the data source, not just the specific logs targeted by the parsing rule. The question states that other logs from the same data source are ingested as expected, so the Broker VM is likely operational.
* B. The parsing rule corrupted the database: Parsing rules operate on incoming logs during ingestion and do not directly interact with or corrupt the Cortex XDR database. This is an unlikely cause, and database corruption would likely cause broader issues, not just missing specific logs.
* D. The XDR Collector is dropping the logs: The XDR Collector forwards logs to Cortex XDR, and if it were dropping logs, it would likely affect all logs from the data source, not just those targeted by the parsing rule. Since other logs are ingested correctly, the issue is downstream in the parsing rule, not at the collector level.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains parsing rule behavior: "The filter stage in a parsing rule determines which logs are processed; misconfigured filters can drop logs, causing them to be excluded from ingestion" (paraphrased from the Data Ingestion section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers parsing rule troubleshooting, stating that "if specific logs are missing during parsing, check the filter stage for conditions that may be dropping the logs" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "data ingestion and integration" as a key exam topic, encompassing parsing rule configuration and troubleshooting.
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 # 28
A security audit determines that the Windows Cortex XDR host-based firewall is not blocking outbound RDP connections for certain remote workers. The audit report confirms the following:
* All devices are running healthy Cortex XDR agents.
* A single host-based firewall rule to block all outbound RDP is implemented.
* The policy hosting the profile containing the rule applies to all Windows endpoints.
* The logic within the firewall rule is adequate.
* Further testing concludes RDP is successfully being blocked on all devices tested at company HQ.
* Network location configuration in Agent Settings is enabled on all Windows endpoints.What is the likely reason the RDP connections are not being blocked?

A. The profile's default action for outbound traffic is set to Allow
B. Report mode is set to Enabled in the report settings under the profile configuration
C. The pertinent host-based firewall rule group is only applied to external rule groups
D. The pertinent host-based firewall rule group is only applied to internal rule groups

Answer: D

Explanation:
Cortex XDR'shost-based firewallfeature allows administrators to define rules to control network traffic on endpoints, such as blocking outbound Remote Desktop Protocol (RDP) connections (typically on TCP port
3389). The firewall rules are organized intorule groups, which can be applied based on the endpoint's network location(e.g., internal or external). Thenetwork location configurationin Agent Settings determines whether an endpoint is considered internal (e.g., on the company network at HQ) or external (e.g., remote workers on a public network). The audit confirms that a rule to block outbound RDP exists, the rule logic is correct, and it works at HQ but not for remote workers.
* Correct Answer Analysis (D):The likely reason RDP connections are not being blocked for remote workers is thatthe pertinent host-based firewall rule group is only applied to internal rule groups.
Since network location configuration is enabled, Cortex XDR distinguishes between internal (e.g., HQ) and external (e.g., remote workers) networks. If the firewall rule group containing the RDP block rule is applied only tointernal rule groups, it will only take effect for endpoints at HQ (internal network), as confirmed by the audit. Remote workers, on an external network, would not be subject to this rule group, allowing their outbound RDP connections to proceed.
* Why not the other options?
* A. The profile's default action for outbound traffic is set to Allow: While a default action of Allow could permit traffic not matched by a rule, the audit confirms the RDP block rule's logic is adequate and works at HQ. This suggests the rule is being applied correctly for internal endpoints, but not for external ones, pointing to a rule group scoping issue rather than the default action.
* B. The pertinent host-based firewall rule group is only applied to external rule groups: If the rule group were applied only to external rule groups, remote workers (on external networks) would have RDP blocked, but the audit shows the opposite-RDP is blocked at HQ (internal) but not for remote workers.
* C. Report mode is set to Enabled in the report settings under the profile configuration: If report mode were enabled, the firewall rule would only log RDP traffic without blocking it, but this would affect all endpoints (both HQ and remote workers). The audit shows RDP is blocked at HQ, so report mode is not enabled.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains host-based firewall configuration: "Firewall rule groups can be applied to internal or external network locations, as determined by the network location configuration in Agent Settings. Rules applied to internal rule groups will not affect endpoints on external networks" (paraphrased from the Host-Based Firewall section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers firewall rules, stating that "network location settings determine whether a rule group applies to internal or external endpoints, impacting rule enforcement" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "Cortex XDR agent configuration" as a key exam topic, encompassing host-based firewall 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 # 29
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. Indicator of Compromise (IOC)
B. Analytics Behavioral Indicator of Compromise (ABIOC)
C. Correlation
D. Behavioral Indicator of Compromise (BIOC)

Answer: D

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 # 30
An XDR engineer is configuring an automation playbook to respond to high-severity malware alerts by automatically isolating the affected endpoint and notifying the security team via email. The playbook should only trigger for alerts generated by the Cortex XDR analytics engine, not custom BIOCs. Which two conditions should the engineer include in the playbook trigger to meet these requirements? (Choose two.)

A. Alert status is New
B. Alert severity is High
C. Alert source is Cortex XDR Analytics
D. Alert category is Malware

Answer: B,D

Explanation:
In Cortex XDR,automation playbooks(also referred to as response actions or automation rules) allow engineers to define automated responses to specific alerts based on trigger conditions. The playbook in this scenario needs to isolate endpoints and send email notifications for high-severity malware alerts generated by the Cortex XDR analytics engine, excluding custom BIOC alerts. To achieve this, the engineer must configure the playbook trigger with conditions that match the alert's severity, category, and source.
* Correct Answer Analysis (A, C):
* A. Alert severity is High: The playbook should only trigger for high-severity alerts, as specified in the requirement. Setting the conditionAlert severity is Highensures that only alerts with a severity level of "High" activate the playbook, aligning with the engineer's goal.
* C. Alert category is Malware: The playbook targets malware alerts specifically. The condition Alert category is Malwareensures that the playbook only responds to alerts categorized as malware, excluding other types of alerts (e.g., lateral movement, exploit).
* Why not the other options?
* B. Alert source is Cortex XDR Analytics: While this condition would ensure the playbook triggers only for alerts from the Cortex XDR analytics engine (and not custom BIOCs), the requirement to exclude BIOCs is already implicitly met because BIOC alerts are typically categorized differently (e.g., as custom alerts or specific BIOC categories). The alert category (Malware) and severity (High) conditions are sufficient to target analytics-driven malware alerts, and adding the source condition is not strictly necessary for the stated requirements. However, if the engineer wanted to be more explicit, this condition could be considered, but the question asks for the two most critical conditions, which are severity and category.
* D. Alert status is New: The alert status (e.g., New, In Progress, Resolved) determines the investigation stage of the alert, but the requirement does not specify that the playbook should only trigger for new alerts. Alerts with a status of "InProgress" could still be high-severity malware alerts requiring isolation, so this condition is not necessary.
Additional Note on Alert Source: The requirement to exclude custom BIOCs and focus on Cortex XDR analytics alerts is addressed by theAlert category is Malwarecondition, as analytics-driven malware alerts (e.
g., from WildFire or behavioral analytics) are categorized as "Malware," while BIOC alerts are often tagged differently (e.g., as custom rules). If the question emphasized the need to explicitly filter by source, option B would be relevant, but the primary conditions for the playbook are severity and category.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains automation playbook triggers: "Playbook triggers can be configured with conditions such as alert severity (e.g., High) and alert category (e.g., Malware) to automate responses like endpoint isolation and email notifications" (paraphrased from the Automation Rules section).
TheEDU-262: Cortex XDR Investigation and Responsecourse covers playbook creation, stating that
"conditions like alert severity and category ensure playbooks target specific alert types, such as high-severity malware alerts from analytics" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "playbook creation and automation" as a key exam topic, encompassing trigger condition configuration.
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 # 31
A static endpoint group is created by adding 321 endpoints using the Upload From File feature. However, after group creation, the members count field shows 244 endpoints. What are two possible reasons why endpoints were not added to the group? (Choose two.)

A. Endpoints added to the group were in Disconnected or Connection Lost status when groupmembership was added
B. Endpoints added to the new group were previously added to an existing group
C. Static groups have a limit of 250 endpoints when adding by file
D. The IP address, hostname, or alias of the endpoints must match an existing agent that has registered with the tenant

Answer: A,D

Explanation:
In Cortex XDR,static endpoint groupsare manually defined groups of endpoints, often created by uploading a file containing endpoint identifiers (e.g., IP addresses, hostnames, or aliases) using theUpload From File feature. If fewer endpoints are added to the group than expected (e.g., 244 instead of 321), there are several possible reasons related to endpoint status or registration.
* Correct Answer Analysis (C, D):
* **C. Endpoints added to the group were in Disconnected or Connection Lost status when group status when group membership was added: If endpoints are in aDisconnectedorConnection Loststatus (i.e., not actively communicating with the Cortex XDR tenant), they may not be successfully added to the group, as Cortex XDR requires active registration to validate and process group membership.
* D. The IP address, hostname, or alias of the endpoints must match an existing agent that has registered with the tenant: For endpoints to be added to a static group, their identifiers (IP address, hostname, or alias) in the uploaded file must correspond to agents that are registered with the Cortex XDR tenant. If the identifiers do not match registered agents, those endpoints will not be added to the group.
* Why not the other options?
* A. Static groups have a limit of 250 endpoints when adding by file: There is no documented limit of 250 endpoints for static groups in Cortex XDR when using the Upload From File feature.
The platform supports large numbers of endpoints in groups, and this is not a valid reason.
* B. Endpoints added to the new group were previously added to an existing group: In Cortex XDR, endpoints are assigned to a single group for policy application to avoid conflicts, but this does not prevent endpoints from being added to a new static group during creation. The issue lies in registration or connectivity, not prior group membership.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains endpoint group management: "Endpoints must be registered and actively connected to the tenant to be added to static groups. Unregistered or disconnected endpoints may not be included in the group" (paraphrased from the Endpoint Management section). TheEDU-
260: Cortex XDR Prevention and Deploymentcourse covers group creation, stating that "static groups require valid, registered endpoint identifiers, and disconnected endpoints may not be added" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "Cortex XDR agent configuration" as a key exam topic, encompassing endpoint group management.
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 # 32
A cloud administrator reports high network bandwidth costs attributed to Cortex XDR operations and asks for bandwidth usage to be optimized without compromising agent functionality. Which two techniques should the engineer implement? (Choose two.)

A. Enable minor content version updates
B. Enable agent content management bandwidth control
C. Deploy a Broker VM and activate the local agent settings applet
D. Configure P2P download sources for agent upgrades and content updates

Answer: B,D

Explanation:
Cortex XDR agents communicate with the cloud for tasks like receiving content updates, agent upgrades, and sending telemetry data, which can consume significant network bandwidth. To optimize bandwidth usage without compromising agent functionality, the engineer should implement techniques that reduce network traffic while maintaining full detection, prevention, and response capabilities.
* Correct Answer Analysis (A, C):
* A. Configure P2P download sources for agent upgrades and content updates: Peer-to-Peer (P2P) download sources allow Cortex XDR agents to share content updates and agent upgrades with other agents on the same network, reducing the need for each agent to download data directly from the cloud. This significantly lowers bandwidth usage, especially in environments with many endpoints.
* C. Enable agent content management bandwidth control: Cortex XDR provides bandwidth control settings in theContent Managementconfiguration, allowing administrators to limit the bandwidth used for content updates and agent communications. This feature throttles data transfers to minimize network impact while ensuring updates are still delivered.
* Why not the other options?
* B. Enable minor content version updates: Enabling minor content version updates ensures agents receive incremental updates, but this alone does not significantly optimize bandwidth, as it does not address the volume or frequency of data transfers. It is a standard practice but not a primary bandwidth optimization technique.
* D. Deploy a Broker VM and activate the local agent settings applet: A Broker VM can act as a local proxy for agent communications, potentially reducing cloud traffic, but thelocal agent settings appletis used for configuring agent settings locally, not for bandwidth optimization.
Additionally, deploying a Broker VM requires significant setup and may not directly address bandwidth for content updates or upgrades compared to P2P or bandwidth control.
Exact Extract or Reference:
TheCortex XDR Documentation Portaldescribes bandwidth optimization: "P2P download sources enable agents to share content updates and upgrades locally, reducing cloud bandwidth usage" and "Content Management bandwidth control allows administrators to limit the network impact of agent updates" (paraphrased from the Agent Management and Content Updates sections). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers post-deployment optimization, stating that "P2P downloads and bandwidth control settings are key techniques for minimizing network usage" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "post-deployment management and configuration" as a key exam topic, encompassing bandwidth optimization.
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 # 33
Log events from a previously deployed Windows XDR Collector agent are no longer being observed in the console after an OS upgrade. Which aspect of the log events is the probable cause of this behavior?

A. They are in Winlogbeat format
B. They are greater than 5MB
C. They are in Filebeat format
D. They are less than 1MB

Answer: B

NEW QUESTION # 34
When isolating Cortex XDR agent components to troubleshoot for compatibility, which command is used to turn off a component on a Windows machine?

A. "C:\Program Files\Palo Alto Networks\Traps\cytool.exe" occp
B. "C:\Program Files\Palo Alto Networks\Traps\cytool.exe" runtime stop
C. "C:\Program Files\Palo Alto Networks\Traps\xdr.exe" stop
D. "C:\Program Files\Palo Alto Networks\Traps\xdr.exe" -s stop

Answer: B

Explanation:
Cortex XDR agents on Windows include multiple components (e.g., for exploit protection, malware scanning, or behavioral analysis) that can be individually enabled or disabled for troubleshooting purposes, such as isolating compatibility issues. Thecytool.exeutility, located in the Cortex XDR installation directory (typically C:\Program Files\Palo Alto Networks\Traps\), is used to manage agent components and settings. The runtime stop command specifically disables a component without uninstalling the agent.
* Correct Answer Analysis (B):The command"C:\Program Files\Palo Alto Networks\Traps\cytool.
exe" runtime stopis used to turn off a specific Cortex XDR agent component on a Windows machine.
For example, cytool.exe runtime stop protection would disable the protection component, allowing troubleshooting for compatibility issues while keeping other components active.
* Why not the other options?
* A. "C:\Program Files\Palo Alto Networks\Traps\xdr.exe" stop: The xdr.exe binary is not used for managing components; it is part of the agent's corefunctionality. The correct utility is cytool.exe.
* C. "C:\Program Files\Palo Alto Networks\Traps\xdr.exe" -s stop: Similarly, xdr.exe is not the correct tool, and -s stop is not a valid command syntax for component management.
* D. "C:\Program Files\Palo Alto Networks\Traps\cytool.exe" occp: The occp command is not a valid cytool.exe option. The correct command for stopping a component is runtime stop.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains component management: "To disable a Cortex XDR agent component on Windows, use the command cytool.exe runtime stop <component> from the installation directory" (paraphrased from the Troubleshooting section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers agent troubleshooting, stating that "cytool.exe runtime stop is used to turn off specific components for compatibility testing" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "maintenance and troubleshooting" as a key exam topic, encompassing agent component management.
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 # 35
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. Conduct an XQL query for NGFW log data
B. Retrieve device certificate from NGFW dashboard
C. Confirm that the selected device has a valid certificate
D. Wait for an incident that involves the NGFW to populate

Answer: A

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. Between 10 and 20 minutes
B. 5 minutes or less
C. Immediately
D. Between 30 and 45 minutes

Answer: B

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
Which method will drop undesired logs and reduce the amount of data being ingested?

A. [INGEST:vendor="vendor", product="product", target_dataset="vendor_product_raw",no_hit=drop] * filter _raw_log not contains "undesired logs";
B. [INGEST:vendor="vendor", product="product", target_brokers="vendor_product_raw", no_hit=keep] * 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. [COLLECT:vendor="vendor", product="product", target_dataset="", no_hit=drop] * drop _raw_log contains "undesired logs";

Answer: D

Explanation:
In Cortex XDR, managing data ingestion involves defining rules to collect, filter, or drop logs to optimize storage and processing. The goal is todrop undesired logsto reduce the amount of data ingested. The syntax used in the options appears to be a combination of ingestion rule metadata (e.g., [COLLECT] or [INGEST]) and filtering logic, likely written in a simplified query language for log processing. Thedropaction explicitly discards logs matching a condition, whilefilterwithnot containscan achieve similar results by keeping only logs that do not match the condition.
* Correct Answer Analysis (C):The method in option C,[COLLECT:vendor="vendor", product=" product", target_dataset="", no_hit=drop] * drop _raw_log contains "undesired logs";, explicitly dropslogs where the raw log content contains "undesired logs". The [COLLECT] directive defines the log collection scope (vendor, product, and dataset), and the no_hit=drop parameter indicates that unmatched logs are dropped. The drop _raw_log contains "undesired logs" statement ensures that logs matching the "undesired logs" pattern are discarded, effectively reducing the amount of data ingested.
* Why not the other options?
* A. [COLLECT:vendor="vendor", product="product", target_brokers="", no_hit=drop] * drop _raw_log contains "undesired logs";: This is similar to option C but uses target_brokers="", which is typically used for Broker VM configurations rather than direct dataset ingestion. While it could work, option C is more straightforward with target_dataset="".
* B. [INGEST:vendor="vendor", product="product", target_dataset="
vendor_product_raw", no_hit=drop] * filter _raw_log not contains "undesired logs";: This method uses filter _raw_log not contains "undesired logs" to keep logs that do not match the condition, which indirectly drops undesired logs. However, the drop action in option C is more explicit and efficient for reducing ingestion.
* D. [INGEST:vendor="vendor", product="product", target_brokers="
vendor_product_raw", no_hit=keep] * filter _raw_log not contains "undesired logs";: The no_hit=keep parameter means unmatched logs are kept, which does not align with the goal of reducing data. The filter statement reduces data, but no_hit=keep may counteract this by retaining unmatched logs, making this less effective than option C.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains log ingestion rules: "To reduce data ingestion, use the drop action to discard logs matching specific patterns, such as _raw_log contains 'pattern'" (paraphrased from the Data Ingestion section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers data ingestion optimization, stating that "dropping logs with specific content using drop _raw_log contains is an effective way to reduce ingested data volume" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "data ingestion and integration" as a key exam topic, encompassing log filtering and dropping.
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 # 38
How can a customer ingest additional events from a Windows DHCP server into Cortex XDR with minimal configuration?

A. Activate Windows Event Collector (WEC)
B. Install the XDR Collector
C. Install the Cortex XDR agent
D. Enable HTTP collector integration

Answer: B

Explanation:
To ingest additional events from a Windows DHCP server into Cortex XDR with minimal configuration, the recommended approach is to use theCortex XDR Collector. TheXDR Collectoris a lightweight component designed to collect and forward logs and events from various sources, including Windows servers, to Cortex XDR for analysis and correlation. It is specifically optimized for scenarios where full Cortex XDR agent deployment is not required, and it minimizes configuration overhead by automating much of the data collection process.
For a Windows DHCP server, the XDR Collector can be installed on the server to collect DHCP logs (e.g., lease assignments, renewals, or errors) from the Windows Event Log or other relevant sources. Once installed, the collector forwards these events to the Cortex XDR tenant with minimal setup, requiring only basic configuration such as specifying the target data types and ensuring network connectivity to the Cortex XDR cloud. This approach is more straightforward than alternatives like setting up a full agent or configuring external integrations like Windows Event Collector (WEC) or HTTP collectors, which require additional infrastructure or manual configuration.
* Why not the other options?
* A. Activate Windows Event Collector (WEC): While WEC can collect events from Windows servers, it requires significant configuration, including setting up a WEC server, configuring subscriptions, and integrating with Cortex XDR via a separate ingestion mechanism. This is not minimal configuration.
* C. Enable HTTP collector integration: HTTP collector integration is used for ingesting data via HTTP/HTTPS APIs, which is not applicable for Windows DHCP server events, as DHCP logs are typically stored in the Windows Event Log, not exposed via HTTP.
* D. Install the Cortex XDR agent: The Cortex XDR agent is a full-featured endpoint protection and detection solution that includes prevention, detection, and responsecapabilities. While it can collect some event data, it is overkill for the specific task of ingesting DHCP server events and requires more configuration than the XDR Collector.
Exact Extract or Reference:
TheCortex XDR Documentation Portaldescribes theXDR Collectoras a tool for "collecting logs and events from servers and endpoints with minimal setup" (paraphrased from the Data Ingestion section). TheEDU-260:
Cortex XDR Prevention and Deploymentcourse emphasizes that "XDR Collectors are ideal for ingesting server logs, such as those from Windows DHCP servers, with streamlined configuration" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetlists "data source onboarding and integration configuration" as a key skill, which includes configuring XDR Collectors for log ingestion.
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 # 39
How are dynamic endpoint groups created and managed in Cortex XDR?

A. Endpoint groups are defined based on fields such as OS type, OS version, and network segment
B. Endpoint groups require intervention to update the group with new endpoints when a new device is added to the network
C. After an endpoint group is created, its assigned security policy cannot be changed without deleting and recreating the group
D. Each endpoint can belong to multiple groups simultaneously, allowing different security policies to be applied to the same device at the same time

Answer: A

Explanation:
In Cortex XDR,dynamic endpoint groupsare used to organize endpoints for applying security policies, managing configurations, and streamlining operations. These groups are defined based on dynamic criteria, such asOS type,OS version,network segment,hostname, or other endpoint attributes. When a new endpoint is added to the network, it is automatically assigned to the appropriate group(s) based on these criteria, without manual intervention. This dynamic assignment ensures that security policies are consistently applied to endpoints matching the group's conditions.
* Correct Answer Analysis (D):The optionDaccurately describes how dynamic endpoint groups are created and managed. Administrators define groups using filters based on endpoint attributes like operating system (e.g., Windows, macOS, Linux), OS version (e.g., Windows 10 21H2), or network segment (e.g., subnet or domain). These filters are evaluated dynamically, so endpoints are automatically added or removed from groups as their attributes change or new devices are onboarded.
* Why not the other options?
* A. Endpoint groups require intervention to update the group with new endpoints when a new device is added to the network: This is incorrect because dynamic endpoint groups are designed to automatically include new endpoints that match the group's criteria, without manual intervention.
* B. Each endpoint can belong to multiple groups simultaneously, allowing different security policies to be applied to the same device at the same time: This is incorrect because, in Cortex XDR, an endpoint is assigned to a single endpoint group for policy application to avoid conflicts.
While endpoints can match multiple group criteria, the system uses a priority or hierarchy to assign the endpoint to onegroup for policy enforcement.
* C. After an endpoint group is created, its assigned security policy cannot be changed without deleting and recreating the group: This is incorrect because Cortex XDR allows administrators to modify the security policy assigned to an endpoint group without deleting and recreating the group.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains endpoint group management: "Dynamic endpoint groups are created by defining filters based on endpoint attributes such as OS type, version, or network segment.
Endpoints are automatically assigned to groups based on these criteria" (paraphrased from the Endpoint Management section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers endpoint group configuration, stating that "groups are dynamically updated as endpoints join or leave the network based on defined attributes" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "endpoint management and policy configuration" as a key exam topic, which encompasses dynamic endpoint groups.
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 using Kerberos as the authentication method for Pathfinder, which two settings must be validated on the DNS server? (Choose two.)

A. Reverse DNS records
B. DNS forwarders
C. Reverse DNS zone
D. AD DS-integrated zones

Answer: A,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 # 41
......

Prepare for your Palo Alto Networks certification with the updated UpdateDumps XDR-Engineer exam questions: https://drive.google.com/open?id=1sSYpIBxSCdqQJEmjBWR7R5vpYILpfomS

Get Latest XDR-Engineer Dumps Exam Questions in here: https://www.updatedumps.com/Palo-Alto-Networks/XDR-Engineer-updated-exam-dumps.html

[Feb-2026] Pass Palo Alto Networks XDR-Engineer Exam in First Attempt Guaranteed! [Q21-Q41]

Palo Alto Networks XDR-Engineer Certification Practice Exam

[Feb-2026] Pass Palo Alto Networks XDR-Engineer Exam in First Attempt Guaranteed! [Q21-Q41]

Related Articles