XSOAR-Engineer Incident Interactions And Reporting Practice Test 1 — 15 Questions

Question 1

An analyst is reviewing the War Room audit log and notices that an entry generated by an integration script contains sensitive API keys. How can the analyst remove this sensitive text from the War Room history?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Hover over the specific War Room entry, click the options menu, and select 'Delete'. In Cortex XSOAR, the War Room audit log entries can be individually deleted via the entry's options menu. Hovering over the specific entry and selecting 'Delete' removes that entry from the War Room history, effectively eliminating the sensitive text. This is the only supported method to remove a single entry without affecting other data.

Answer

Modify the integration code to retroactively scrub historical database entries

Answer

Lock the incident, which automatically sanitizes all War Room text matching regex patterns

Answer

Run the '!clear-war-room-secrets' command with the entry ID

Question 2

During a high-severity incident, an analyst needs to run a playbook task manually while bypassing standard automated conditional gates. How can this be accomplished from the War Room?

Accepted Answer

Navigate to the Playbook tab within the incident, select the specific task, and choose 'Force Run'. In Cortex XSOAR, the Playbook tab within an incident shows the visual playbook graph, and selecting a specific task exposes a 'Force Run' option that executes that task immediately, bypassing conditional gates and dependencies. This is the supported manual-override mechanism during high-severity incidents when an analyst needs to skip automation logic.

Answer

Restart the entire XSOAR server container to reset playbook state machines

Answer

Type '!force-playbook-task' directly in the War Room CLI without parameters

Answer

Edit the incident type schema to automatically convert all conditional tasks to automatic

Question 3

Where can an analyst view a chronological timeline of all automated and manual actions taken within an active incident?

Accepted Answer

The War Room tab. The War Room tab in Cortex XSOAR is the central collaboration and audit interface for an active incident. It records every automated task, playbook step, manual analyst command, and entry (notes, files, indicators) in chronological order, making it the definitive place to view a timeline of all actions taken. The Dashboards tab, while useful for aggregated metrics and visualizations, does not provide a per-incident chronological action log; it displays widget-based summaries that can be filtered but lack the detailed, sequential audit trail of the War Room.

Answer

The Threat Intel tab

Answer

Settings > About

Question 4

An analyst needs to add a private note to an incident's War Room that only specific team members can view. How should the analyst enter the note?

Accepted Answer

Type the text directly into the War Room input bar and press Enter. In Cortex XSOAR, a private note is created by typing the text directly into the War Room input bar and pressing Enter — the note is then visible only to the analyst who created it (and can be toggled to be shared). This is the standard, native mechanism for adding analyst-only commentary to an incident's War Room without invoking any automation or changing configuration. No special command, export, or encryption setting is required.

Answer

Use the '!private-note' automation command

Answer

Export the incident to an encrypted ZIP file

Answer

Navigate to Settings > Security > War Room Encryption

Question 5

An administrator wants to create a dashboard widget that counts only incidents where the SLA has been breached. Which query syntax should be used in the widget definition?

Accepted Answer

slastatus:breached. SLA status is tracked via built-in fields like 'duedate' or specific SLA indicator flags such as 'closingReason' or SLA breach properties.

Answer

status:closed and severity:high

Answer

duedate > now

Answer

sla:expired

Question 6

An administrator is troubleshooting a scheduled report that fails to email its PDF output to stakeholders. Where should the administrator check first to diagnose the delivery failure?

Accepted Answer

Settings > About > Troubleshooting > Server Logs. Server logs and the specific reporting execution logs help identify mailing or rendering errors.

Answer

The Incident War Room of the report creator

Answer

The browser developer tools console while viewing the dashboard

Answer

Settings > Integrations > Instances > Mail Sender status

Question 7

An administrator configured a custom incident field of type 'MultiSelect', but analysts complain that they cannot select more than one option when creating a new incident. What is the most likely cause?

Accepted Answer

The corresponding field element in the incident layout is configured as a single-select dropdown instead of multi-select. Layout configurations must match field types; if the layout element is configured as a single select or dropdown instead of multi-select, or if the field definition itself was incorrectly set, behavior is restricted. Assuming layout field configuration.

Answer

Multi-select fields are not supported in custom incident types

Answer

All multi-select fields require an active threat intelligence feed license

Answer

The database index for multi-select fields must be rebuilt via CLI using '!rebuild-index'

Question 8

An analyst wants to view incidents that were closed within the last 24 hours. Which query should be entered in the WorkArea search bar?

Accepted Answer

closed > 24hours. Cortex XSOAR's WorkArea search bar supports a query syntax where 'closed > 24hours' filters incidents whose closed timestamp is within the last 24 hours. This is the documented relative-time syntax for the closed field, making it the correct query for the analyst's requirement.

Answer

active:false and duration<1d

Answer

status:closed and time:today

Answer

closeddate:past-day

Question 9

An administrator wants to ensure that specific sensitive incidents are restricted so that only members of the 'IncidentResponse' team can view or edit them. How should this be implemented?

Accepted Answer

Configure Role-Based Access Control (RBAC) and assign incident type permissions to the 'IncidentResponse' role. Incident-level access control or role-based permissions on incident types can restrict visibility.

Answer

Turn off the REST API server for all non-admin users

Answer

Password-protect each individual incident via the War Room header

Answer

Encrypt the incident database table using AES-256 keys

Question 10

Which TWO built-in fields are automatically populated when a new incident is created in Cortex XSOAR?

Accepted Answer

Status. Built-in fields like incident ID, creation time (or modified time), and status are automatically populated upon creation.

Answer

Vehicle license plate number

Answer

Frequent flyer miles balance

Answer

Employee payroll identification number

Question 11

An administrator wants to ensure that specific incident fields are automatically populated and marked as read-only once an incident reaches the 'Containment' phase. Where should this behavior be configured?

Accepted Answer

In the Layouts configuration using conditional formatting or read-only rules tied to incident phases.. Layouts in Cortex XSOAR determine field visibility, editability, and arrangement based on incident types and phases.

Answer

In the Incident Types settings under the 'Mandatory Fields' tab.

Answer

In the Server Configuration under the 'incident.readonly.phases' parameter.

Answer

In the Automation script parameters for the containment playbook task.

Question 12

A SOC manager needs to grant an analyst the ability to see and edit only incidents assigned to the analyst's team, while still allowing the analyst to view the full War Room of those incidents. The manager creates a new role and assigns it to the analyst. Which Cortex XSOAR role configuration setting must be enabled to enforce this restriction?

Accepted Answer

Enable 'Investigation' permission and set the role's incident access to 'Team' scope.. The correct answer is to enable the 'Investigation' permission and set the role's incident access to 'Team' scope. Cortex XSOAR's RBAC model uses incident access scopes to control visibility. 'Team' scope allows users to see incidents assigned to their team, while 'Investigation' permission grants access to the War Room. This precisely meets the manager's requirement without granting excessive privileges.

Answer

Enable 'War Room' permission and configure a custom incident type filter.

Answer

Enable 'Incident' permission and set the role's incident access to 'All' scope.

Answer

Enable 'Playbook' permission and set the role's incident access to 'Owner' scope.

Question 13

An analyst is investigating a phishing incident in Cortex XSOAR and wants to share a summary of the investigation with a colleague who does not have access to the incident. The analyst decides to create a link to the incident that includes a read-only view of the War Room entries. Which Cortex XSOAR feature should the analyst use to generate this link?

Accepted Answer

Create a 'War Room' report and export it as a PDF to send to the colleague.. The correct approach is to create a War Room report and export it as a PDF. Cortex XSOAR's reporting feature allows analysts to compile War Room entries into a report that can be exported and shared. This provides a read-only summary without granting system access. Other options either do not exist or do not meet the requirement of sharing with an external colleague.

Answer

Enable 'Anonymous Access' for the incident in the incident's settings.

Answer

Use the 'Share' button in the incident's toolbar to create a shareable link.

Answer

Generate a 'Public Link' from the incident's War Room menu.

Question 14

An analyst is reviewing a high-severity phishing incident in Cortex XSOAR. The incident was ingested from an email integration instance. The analyst wants to add a tagged entry to the War Room that explicitly marks a specific command output as 'evidence' for later audit purposes. Which action should the analyst take?

Accepted Answer

Use the 'Add Entry' button to create a note, then apply the 'Evidence' tag from the tag selector.. Tagging War Room entries is the native way to categorize notes and command outputs for auditing. The analyst should add a note and apply the appropriate tag, which enables filtering and reporting. Other options either reference non-existent commands or misapply features like custom fields or PDF export.

Answer

Run the '!mark-evidence' command from the CLI to flag the last command result.

Answer

Use the 'Export to PDF' option in the War Room to save the entry with an evidence watermark.

Answer

Edit the incident's custom fields to add an 'Evidence' field and paste the command output there.

Question 15

A security analyst is working on an incident in Cortex XSOAR and wants to quickly see all the playbook tasks that are currently waiting for manual input. Which view in the incident should the analyst use to identify these tasks?

Accepted Answer

The 'Playbook' tab, filtering by 'Waiting' status.. The Playbook tab is the correct place to view playbook execution and identify tasks waiting for manual input. Tasks with a 'Waiting' status are clearly indicated in the playbook graph, allowing the analyst to act on them. Other tabs either do not show task statuses or require inefficient searching.

Answer

The 'Incident Details' tab, checking the 'Tasks' section.

Answer

The 'Dashboard' tab, using the 'Pending Tasks' widget.

Answer

The 'War Room' tab, searching for 'manual' in the entries.