Check the Available XDR-Engineer Exam Dumps with 52 QA's UPDATED 2026
Download XDR-Engineer Exam Dumps Questions to get 100% Success in Palo Alto Networks
Palo Alto Networks XDR-Engineer Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 17
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. The requested data requires additional configuration to be captured
- B. Check Host Inventory -> Mounts
- C. dataset = xdr_data | filter event_type = ENUM.MOUNT and event_sub_type = ENUM.
MOUNT_DRIVE_MOUNT - D. preset = device_control
Answer: B
Explanation:
In Cortex XDR, theDevice Configuration profile(an extension of the agent settings profile) controls how the Cortex XDR agent monitors and manages device-related activities, such as the mounting of removable drives.
By default, the Device Configuration profile includes monitoring for device mount events, such as when a USB drive or other removable media is connected to an endpoint. These events are logged and can be accessed for investigations, such as detecting unauthorized drive usage in an insider compromise scenario.
* Correct Answer Analysis (A):TheHost Inventory -> Mountssection in the Cortex XDR console provides a detailed view of mount events for each endpoint, including information about removable drives mounted on the system. This is the most straightforward place to find evidence of an unauthorized removable drive being mounted on the company laptop, as it aggregates device mount events captured by the default Device Configuration profile.
* Why not the other options?
* B. dataset = xdr_data | filter event_type = ENUM.MOUNT and event_sub_type = ENUM.
MOUNT_DRIVE_MOUNT: This XQL query is technically correct for retrieving mount events from thexdr_datadataset, but it requires manual query execution and knowledge of specific event types. The Host Inventory -> Mounts section is a more user-friendly and direct method for accessing this data, making it the preferred choice for an engineer investigating this issue.
* C. The requested data requires additional configuration to be captured: This is incorrect because the default Device Configuration profile already captures mount events for removable drives, so no additional configuration is needed.
* D. preset = device_control: Thedevice_controlpreset in XQL retrieves device control-related events (e.g., USB block or allow actions), but it may not specifically include mount events unless explicitly configured. The Host Inventory -> Mounts section is more targeted for this investigation.
Exact Extract or Reference:
TheCortex XDR Documentation Portaldescribes device monitoring: "The default Device Configuration profile logs mount events for removable drives, which can be viewed in the Host Inventory -> Mounts section of the console" (paraphrased from the Device Configuration section). TheEDU-262: Cortex XDR Investigation and Responsecourse covers investigation techniques, stating that "mount events for removable drives are accessible in the Host Inventory for endpoints with default device monitoring" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "maintenance and troubleshooting" as a key exam topic, encompassing investigation of endpoint events.
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 # 18
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 filter stage is dropping the logs
- B. The XDR Collector is dropping the logs
- C. The parsing rule corrupted the database
- D. The Broker VM is offline
Answer: A
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 # 19
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. Wait for an incident that involves the NGFW to populate
- B. Retrieve device certificate from NGFW dashboard
- C. Conduct an XQL query for NGFW log data
- D. Confirm that the selected device has a valid certificate
Answer: C
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 # 20
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 agent content management bandwidth control
- B. Enable minor content version updates
- C. Configure P2P download sources for agent upgrades and content updates
- D. Deploy a Broker VM and activate the local agent settings applet
Answer: A,C
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 # 21
Using the Cortex XDR console, how can additional network access be allowed from a set of IP addresses to an isolated endpoint?
- A. Add entries in Configuration section of Security Settings
- B. Add entries in the Allowed Domains section of Security Settings for the tenant
- C. Add entries in Response Actions section of Agent Settings profile
- D. Add entries in Exceptions Configuration section of Isolation Exceptions
Answer: D
Explanation:
In Cortex XDR,endpoint isolationis a response action that restricts network communication to and from an endpoint, allowing only communication with the Cortex XDR management server to maintain agent functionality. To allow additional network access (e.g., from a set of IP addresses) to an isolated endpoint, administrators can configureisolation exceptionsto permit specific traffic while the endpoint remains isolated.
* Correct Answer Analysis (C):TheExceptions Configuration section of Isolation Exceptionsin the Cortex XDR console allows administrators to define exceptions for isolated endpoints, such as permitting network access from specific IP addresses. This ensures that the isolated endpoint can communicate with designated IPs (e.g., for IT support or backup servers) while maintaining isolation from other network traffic.
* Why not the other options?
* A. Add entries in Configuration section of Security Settings: The Security Settings section in the Cortex XDR console is used for general tenant-wide configurations (e.g., password policies), not for managing isolation exceptions.
* B. Add entries in the Allowed Domains section of Security Settings for the tenant: The Allowed Domains section is used to whitelist domains for specific purposes (e.g., agent communication), not for defining IP-based exceptions for isolated endpoints.
* D. Add entries in Response Actions section of Agent Settings profile: The Response Actions section in Agent Settings defines automated response actions (e.g., isolate on specific conditions), but it does not configure exceptions for already isolated endpoints.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains isolation exceptions: "To allow specific network access to an isolated endpoint, add IP addresses or domains in the Exceptions Configuration section of Isolation Exceptions in the Cortex XDR console" (paraphrased from the Endpoint Isolation section). TheEDU-262:
Cortex XDR Investigation and Responsecourse covers isolation management, stating that "Isolation Exceptions allow administrators to permit network access from specific IPs to isolated endpoints" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes
"post-deployment management and configuration" as a key exam topic, encompassing isolation exception 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 # 22
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 source is Cortex XDR Analytics
- B. Alert category is Malware
- C. Alert status is New
- D. Alert severity is High
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 # 23
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. dypdng
- C. pyxd
- D. pmd
Answer: D
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 # 24
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 Filebeat format
- B. They are greater than 5MB
- C. They are less than 1MB
- D. They are in Winlogbeat format
Answer: B
Explanation:
TheXDR Collectoron a Windows endpoint collects logs (e.g., Windows Event Logs) and forwards them to the Cortex XDR console for analysis. An OS upgrade can impact the collector's functionality, particularly if it affects log formats, sizes, or compatibility. If log events are no longer observed after the upgrade, the issue likely relates to a change in how logs are processed or transmitted. Cortex XDR imposes limits on log event sizes to ensure efficient ingestion and processing.
* Correct Answer Analysis (A):The probable cause is thatthe log events are greater than 5MB. Cortex XDR has a size limit for individual log events, typically around 5MB, to prevent performance issues during ingestion. An OS upgrade may change the way logs are generated (e.g., increasing verbosity or adding metadata), causing events to exceed this limit. If log events are larger than 5MB, the XDR Collector will drop them, resulting in no logs being observed in the console.
* Why not the other options?
* B. They are in Winlogbeat format: Winlogbeat is a supported log shipper for collecting Windows Event Logs, and the XDR Collector is compatible with this format. The format itself is not the issue unless misconfigured, which is not indicated.
* C. They are in Filebeat format: Filebeat is also supported by the XDR Collector for file-based logs. The format is not the likely cause unless the OS upgrade changed the log source, which is not specified.
* D. They are less than 1MB: There is no minimum size limit for log events in Cortex XDR, so being less than 1MB would not cause logs to stop appearing.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains log ingestion limits: "Individual log events larger than 5MB are dropped by the XDR Collector to prevent ingestion issues, which may occur after changes like an OS upgrade" (paraphrased from the XDR Collector Troubleshooting section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers log collection issues, stating that "log events exceeding 5MB are not ingested, a common issue after OS upgrades thatincrease log size" (paraphrased from course materials).
ThePalo Alto Networks Certified XDR Engineer datasheetincludes "maintenance and troubleshooting" as a key exam topic, encompassing log ingestion issues.
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
What are two possible actions that can be triggered by a dashboard drilldown? (Choose two.)
- A. Navigate to a different dashboard
- B. Send alerts to console users
- C. Link to an XQL query
- D. Initiate automated response actions
Answer: A,C
Explanation:
In Cortex XDR,dashboard drilldownsallow users to interact with widgets (e.g., charts or tables) by clicking on elements to access additional details or perform actions. Drilldowns enhance the investigative capabilities of dashboards by linking to related data or views.
* Correct Answer Analysis (A, C):
* A. Navigate to a different dashboard: A drilldown can be configured to navigate to another dashboard, providing a more detailed view or related metrics. For example, clicking on an alert count in a widget might open a dashboard focused on alert details.
* C. Link to an XQL query: Drilldowns often link to anXQL querythat filters data based on the clicked element (e.g., an alert name or source). This allows users to view raw events or detailed records in the Query Builder or Investigation view.
* Why not the other options?
* B. Initiate automated response actions: Drilldowns are primarily for navigation and data exploration, not for triggering automated response actions. Response actions (e.g., isolating an endpoint) are typically initiated from the Incident or Alert views, not dashboards.
* D. Send alerts to console users: Drilldowns do not send alerts to users. Alerts are generated by correlation rules or BIOCs, and dashboards are used for visualization, not alert distribution.
Exact Extract or Reference:
TheCortex XDR Documentation Portaldescribes drilldown functionality: "Dashboard drilldowns can navigate to another dashboard or link to an XQL query to display detailed data based on the selected widget element" (paraphrased from the Dashboards and Widgets section). TheEDU-262: Cortex XDR Investigation and Responsecourse covers dashboards, stating that "drilldowns enable navigation to other dashboards or XQL queries for deeper analysis" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "dashboards and reporting" as a key exam topic, encompassing drilldown 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 # 26
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. Between 30 and 45 minutes
- C. Immediately
- D. 5 minutes or less
Answer: D
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 # 27
What happens when the XDR Collector is uninstalled from an endpoint by using the Cortex XDR console?
- A. It is uninstalled during the next heartbeat communication, machine status changes to Uninstalled, and the configuration data is retained for 90 days
- B. The associated configuration data is removed from the Action Center immediately after uninstallation
- C. The files are removed immediately, and the machine is deleted from the system without any retention period
- D. The machine status remains active until manually removed, and the configuration data is retained for up to seven days
Answer: A
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 # 28
Which method will drop undesired logs and reduce the amount of data being ingested?
- A. [COLLECT:vendor="vendor", product="product", target_brokers="", no_hit=drop] * drop _raw_log 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_dataset="", no_hit=drop] * drop _raw_log contains "undesired logs";
- D. [INGEST:vendor="vendor", product="product", target_dataset="vendor_product_raw",no_hit=drop] * filter _raw_log not contains "undesired logs";
Answer: C
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 # 29
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. The IP address, hostname, or alias of the endpoints must match an existing agent that has registered with the tenant
- B. Endpoints added to the group were in Disconnected or Connection Lost status when groupmembership was added
- C. Static groups have a limit of 250 endpoints when adding by file
- D. Endpoints added to the new group were previously added to an existing group
Answer: A,B
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 # 30
How can a customer ingest additional events from a Windows DHCP server into Cortex XDR with minimal configuration?
- A. Install the XDR Collector
- B. Enable HTTP collector integration
- C. Activate Windows Event Collector (WEC)
- D. Install the Cortex XDR agent
Answer: A
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 # 31
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. Apply an alert exclusion to the XDR agent alert
- B. Apply an alert exclusion to the XDR behavioral indicator of compromise (BIOC) alert
- C. Modify the behavioral indicator of compromise (BIOC) logic
- D. Apply an alert exception
Answer: B,D
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 # 32
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. Database schema exported in the correct format
- B. Access to the database transaction log
- C. Access to the database audit log
- D. Valid SQL query targeting the desired data
Answer: D
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 # 33
An administrator wants to employ reusable rules within custom parsing rules to apply consistent log field extraction across multiple data sources. Which section of the parsing rule should the administrator use to define those reusable rules in Cortex XDR?
- A. RULE
- B. CONST
- C. FILTER
- D. INGEST
Answer: B
Explanation:
In Cortex XDR, parsing rules are used to extract and normalize fields from log data ingested from various sources to ensure consistent analysis and correlation. To create reusable rules for consistent log field extraction across multiple data sources, administrators use theCONSTsection within the parsing rule configuration. TheCONSTsection allows the definition of reusable constants or rules that can be applied across different parsing rules, ensuring uniformity in how fields are extracted and processed.
TheCONSTsection is specifically designed to hold constant values or reusable expressions that can be referenced in other parts of the parsing rule, such as theRULEorINGESTsections. This is particularly useful when multiple data sources require similar field extraction logic, as it reduces redundancy and ensures consistency. For example, a constant regex pattern for extracting IP addresses can be defined in theCONST section and reused across multiple parsing rules.
* Why not the other options?
* RULE: TheRULEsection defines the specific logic for parsing and extracting fields from a log entry but is not inherently reusable across multiple rules unless referenced via constants defined in CONST.
* INGEST: TheINGESTsection specifies how raw log data is ingested and preprocessed, not where reusable rules are defined.
* FILTER: TheFILTERsection is used to include or exclude log entries based on conditions, not for defining reusable extraction rules.
Exact Extract or Reference:
While the exact wording of theCONSTsection's purpose is not directly quoted in public-facing documentation (as some details are in proprietary training materials like EDU-260 or the Cortex XDR Admin Guide), theCortex XDR Documentation Portal(docs-cortex.paloaltonetworks.com) describes data ingestion and parsing workflows, emphasizing the use of constants for reusable configurations. TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers data onboarding and parsing, noting that "constants defined in the CONST section allow reusable parsing logic for consistent field extraction across sources" (paraphrased from course objectives). Additionally, thePalo Alto Networks Certified XDR Engineer datasheetlists "data source onboarding and integration configuration" as a key skill, which includes mastering parsing rules and their components likeCONST.
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 # 34
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. Installation type changed from VDI to Kubernetes
- B. Endpoint IP address changed from 192.168.0.0 range to 192.168.100.0 range
- C. The Cloud Identity Engine is disconnected or removed
- D. XDR agent version was downgraded from 8.7.0 to 8.4.0
Answer: B
Explanation:
The scenario involves macOS users with Cortex XDR agents (version 8.7.0) who can no longer run in-house applications that were previously allowed via disable prevention rules in the"Engineer-Mac" Exceptions Profile. This profile is applied to an endpoint group (e.g., "Mac-Engineers"). Theissue likely stems from a change in the endpoint group's configuration or the endpoints' attributes, affecting policy application.
* Correct Answer Analysis (A):The reason for the behavior is that theendpoint IP address changed from 192.168.0.0 range to 192.168.100.0 range. In Cortex XDR, endpoint groups can be defined using dynamic criteria, such as IP address ranges, to apply specific policies like the "Engineer-Mac" Exceptions Profile. If the group "Mac-Engineers" was defined to include endpoints in the 192.168.0.0 range, and the remote desktop users' IP addresses changed to the 192.168.100.0 range (e.g., due to a network change or VPN reconfiguration), these endpoints would no longer belong to the "Mac- Engineers" group. As a result, the "Engineer-Mac" Exceptions Profile, which allowed the in-house applications, would no longer apply, causing the applications to be blocked by default prevention rules.
* Why not the other options?
* B. The Cloud Identity Engine is disconnected or removed: The Cloud Identity Engine provides user and group data for identity-based policies, but it is not directly related to Exceptions Profiles or application execution rules. Its disconnection would not affect the application of the "Engineer-Mac" profile.
* C. XDR agent version was downgraded from 8.7.0 to 8.4.0: The question states the users are using version 8.7.0, and there's no indication of a downgrade. Even if a downgrade occurred, it's unlikely to affect the application of an Exceptions Profile unless specific features were removed, which is not indicated.
* D. Installation type changed from VDI to Kubernetes: The installation type (e.g., VDI for virtual desktops or Kubernetes for containerized environments) is unrelated to macOS endpoints running remote desktop sessions. This change would not impact the application of the Exceptions Profile.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains endpoint group policies: "Dynamic endpoint groups based on IP address ranges apply policies like Exceptions Profiles; if an endpoint's IP changes to a different range, it may no longer belong to the group, affecting policy enforcement" (paraphrased from the Endpoint Management section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers policy application, stating that "changes in IP address ranges can cause endpoints to fall out of a group, leading to unexpected policy behavior like blocking previously allowed applications" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "Cortex XDR agent configuration" as a key exam topic, encompassing endpoint group and policy 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
An XDR engineer is creating a correlation rule to monitor login activity on specific systems. When the activity is identified, an alert is created. The alerts are being generated properly but are missing the username when viewed. How can the username information be included in the alerts?
- A. Select "Initial Access" in the MITRE ATT&CK mapping to include the username
- B. Add a drill-down query to the alert which pulls the username field
- C. Add a mapping for the username field in the alert fields mapping
- D. Update the query in the correlation rule to include the username field
Answer: C
Explanation:
In Cortex XDR,correlation rulesare used to detect specific patterns or behaviors (e.g., login activity) by analyzing ingested data and generating alerts when conditions are met. For an alert to include specific fields likeusername, the field must be explicitly mapped in thealert fields mappingconfiguration of the correlation rule. This mapping determines which fields from theunderlying dataset are included in the generated alert's details.
In this scenario, the correlation rule is correctly generating alerts for login activity, but theusernamefield is missing. This indicates that the correlation rule's query may be identifying the relevant events, but the usernamefield is not included in the alert's output fields. To resolve this, the engineer must update thealert fields mappingin the correlation rule to explicitly include theusernamefield, ensuring it appears in the alert details when viewed.
* Correct Answer Analysis (C):Adding a mapping for theusernamefield in thealert fields mapping ensures that the field is extracted from the dataset and included in the alert's metadata. This is done in the correlation rule configuration, where administrators can specify which fields to include in the alert output.
* Why not the other options?
* A. Select "Initial Access" in the MITRE ATT&CK mapping to include the username:
Mapping to a MITRE ATT&CK technique like "Initial Access" defines the type of attack or behavior, not specific fields likeusername. This does not address the missing field issue.
* B. Update the query in the correlation rule to include the username field: While the correlation rule's query must reference theusernamefield to detect relevant events, including it in the query alone does not ensure it appears in the alert's output. Thealert fields mappingis still required.
* D. Add a drill-down query to the alert which pulls the username field: Drill-down queries are used for additional investigation after an alert is generated, not for including fields in the alert itself. This does not solve the issue of missingusernamein the alert details.
Exact Extract or Reference:
TheCortex XDR Documentation Portaldescribes correlation rule configuration: "To include specific fields in generated alerts, configure the alert fields mapping in the correlation rule to map dataset fields, such as username, to the alert output" (paraphrased from the Correlation Rules section). TheEDU-262: Cortex XDR Investigation and Responsecourse covers detection engineering, stating that "alert fields mapping determines which data fields are included in alerts generated by correlation rules" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "detection engineering" as a key exam topic, encompassing correlation rule 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 # 36
How long is data kept in the temporary hot storage cache after being queried from cold storage?
- A. 1 hour, re-queried to a maximum of 12 hours
- B. 24 hours, re-queried to a maximum of 14 days
- C. 24 hours, re-queried to a maximum of 7 days
- D. 1 hour, re-queried to a maximum of 24 hours
Answer: C
Explanation:
In Cortex XDR, data is stored in different tiers:hot storage(for recent, frequently accessed data),cold storage (for older, less frequently accessed data), and atemporary hot storage cachefor data retrieved from cold storage during queries. When data is queried from cold storage, it is moved to the temporary hot storage cache to enable faster access for subsequent queries. The question asks how long this data remains in the cache and the maximum duration for re-queries.
* Correct Answer Analysis (B):Data retrieved from cold storage is kept in the temporary hot storage cache for24 hours. If the data is re-queried within this period, it remains accessible in the cache. The maximum duration for re-queries is7 days, after which the data may need to be retrieved from cold storage again, incurring additional processing time.
* Why not the other options?
* A. 1 hour, re-queried to a maximum of 12 hours: These durations are too short and do not align with Cortex XDR's data retention policies for the hot storage cache.
* C. 24 hours, re-queried to a maximum of 14 days: While the initial 24-hour cache duration is correct, the 14-day maximum for re-queries is too long and not supported by Cortex XDR's documentation.
* D. 1 hour, re-queried to a maximum of 24 hours: The 1-hour initial cache duration is incorrect, as Cortex XDR retains queried data for 24 hours.
Exact Extract or Reference:
TheCortex XDR Documentation Portalexplains data storage: "Data queried from cold storage is cached in hot storage for 24 hours, with a maximum re-query period of 7 days" (paraphrased from the Data Management section). TheEDU-262: Cortex XDR Investigation and Responsecourse covers data retention, stating that "queried cold storage data remains in the hot cache for 24 hours, accessible for up to 7 days with re-queries" (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes "maintenance and troubleshooting" as a key exam topic, encompassing data storage 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 # 37
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. Wait for an incident that involves the NGFW to populate
- B. Retrieve device certificate from NGFW dashboard
- C. Conduct an XQL query for NGFW log data
- D. Confirm that the selected device has a valid certificate
Answer: C
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 # 38
......
Best Value Available! 2026 Realistic Verified Free XDR-Engineer Exam Questions: https://www.prep4sureguide.com/XDR-Engineer-prep4sure-exam-guide.html
100% Accurate Answers! XDR-Engineer Actual Real Exam Questions: https://drive.google.com/open?id=1sgNdkfVEs8VnWq7O3AkkKxSa-B0k6OmV