What is an outcome of using sections within a tab when customizing an incident layout?.
Answer : C
The Layout customization section of the XSOAR Admin Guide explains that incident layouts control how analysts view and interact with fields, evidence, and metadata. Within a layout tab, sections exist purely for the purpose of organizing related fields into structured blocks, improving clarity, readability, and workflow efficiency. This is essential in complex incident types where numerous fields must be grouped logically (e.g., ''User Details,'' ''Endpoint Information,'' ''Alert Metadata'').
Sections do not trigger automations or playbooks; automation triggers are defined through playbooks, field-change scripts, or incident type settings. They also do not enforce field mandatory requirements---mandatory fields are defined in the incident type configuration, not within layout sections. Likewise, RBAC does not operate at the section level; access restrictions apply to fields or entire incident types, not layout sections.
Therefore, the only correct and documented result of using sections within tabs is enhanced logical grouping of fields, improving analyst usability and data-entry organization. This aligns with option C, matching the intended purpose described in the layout configuration documentation.
Which of the following does a XSOAR Admin need to create an integration with a third party cloud application?
Answer : B
Which three options can be defined in the layout settings? (Choose three.)
Answer : A, C, E
When using the playbook debugger, what may be the cause of a starred incident missing from the Test Data selections?.
Answer : A
The XSOAR Playbook Debugger allows engineers to simulate playbook behavior using existing incidents as sample data. The documentation explicitly states that only open incidents appear within the debugger's Test Data selection list. Closed incidents are removed from the selectable list because the debugger cannot execute against non-active incident states.
Starring an incident does not affect debugger availability; the star is a user-level convenience for bookmarking. RBAC restrictions (B) could hide an incident in general UI contexts but not selectively from the debugger. Incorrect incident type (D) also does not prevent selection as long as the incident is open.
Therefore, if a starred incident does not appear as a debugging option, the most common and documented reason is that the incident has been closed, and closed incidents cannot be used as debugger input. This aligns with option A.
In a Dev/Prod deployment model, what is available only in the development tenant?.
Answer : D
In Cortex XSOAR's documented Dev/Prod deployment model, the development tenant is designed to be the workspace where engineers create, modify, test, and validate content before promoting it into production. As part of this workflow, the development tenant includes the ''Export all custom content'' feature, which generates a structured content bundle containing custom playbooks, integrations, fields, layouts, lists, and other artifacts. This bundle is then imported into the production tenant to ensure controlled, versioned, and tested promotion of content.
The Admin Guide highlights that this export capability is restricted to the development environment to preserve the integrity and stability of the production tenant. Production systems are intentionally limited, allowing only the import (not export) of custom content to prevent accidental overwriting, drift, or unintended modifications.
Marketplace access (A) exists in both tenants. Custom integration instances (C) can be created in either tenant. The Content Repository page (B) is also available across both environments.
Therefore, the only feature exclusive to the development tenant is D: ''Export all custom content.'' This ensures a safe, repeatable DevProd promotion model aligned with enterprise change-control requirements.
Which Marketplace content pack will allow sharing of threat intelligence in STIX format?.
Answer : D
STIX/TAXII are industry-standard protocols for structured threat intelligence exchange. According to the Threat Intelligence section of the XSOAR documentation, TAXII servers and clients provide automated bidirectional sharing using STIX objects, supporting both ingestion and distribution of indicators, observables, relationships, and threat objects.
The TAXII Server content pack specifically enables an organization to expose its threat intelligence via a TAXII 2.0/2.1 compliant endpoint, where the transmitted data is formatted as STIX, making it the correct choice for sharing structured intelligence externally.
The Generic Export Indicators Service pack supports indicator export, but not in STIX format---it exports simple CSV, JSON, or list-based formats. MISP Server supports STIX ingestion and export but is considered a MISP-specific implementation and not the generic STIX distribution mechanism expected in the question. External dynamic lists are not related to STIX or TAXII at all.
Thus, the correct answer is D, as only the TAXII Server pack is designed explicitly for STIX-formatted intelligence sharing.
An Engineer wants to filter a csvList value according to a dynamic value saved under the test context key.
Which three values would save the test context key? (Choose three.)

Answer : A, B, E