In the Cortex XSOAR ecosystem, the core of automation is the relationship between Incident Types and Playbooks . To automate the response to a compromised account, an administrator follows the standard "Classification and Mapping" workflow:

Ingestion: The alert (e.g., from XDR or an Identity provider) is ingested into XSOAR.

Mapping (A): The event is mapped to a specific Cortex XSOAR Incident Type (such as "Access - Compromised Account"). This ensures the system knows which fields to look at (like Username, IP, or Source).

Playbook Execution: XSOAR is configured so that when an incident of that specific "Type" is created, it automatically triggers a corresponding Playbook .

Response: The playbook contains the automated logic (e.g., "If user is in Executive group, notify SOC Manager; then disable account in AD and revoke O365 tokens").

Why other options are incorrect:

Option B: This is a manual or semi-automated action within XDR, not a full "automated response workflow."

Option C: You do not need a script to run a playbook; the mapping to an Incident Type is what natively triggers the playbook in XSOAR.

Option D: While XSIAM has automation capabilities, the most accurate description of the structured SOAR workflow (Mapping - > Incident Type - > Playbook) is found in Option A.