The Admin Guide states that layouts-representing how analysts view incident data, evidence, fields, and work plans-are attached directly toincident types. When configuring an incident type, the administrator can specify the layout for the "New," "Editing," and "Preview" modes. This ensures consistent presentation of data across the SOC, tailored to each use case (e.g., phishing, endpoint alerts, malware investigations).
Pre-process rules (option A) operate before incident creation and do not control the user interface layout.
Incident playbooks (option B) automate response actions but have no effect on how the incident UI is presented. Integration instance settings (option C) define connection details and ingestion parameters but do not control UI layouts.
Only theIncident Type configuration pageincludes fields for selecting or assigning custom layouts. This aligns with XSOAR's design principle: incident types define schema, workflows, and UI behavior, including which layout is displayed to analysts.
Thus, the correct answer isD, as incident layouts are configured and bound within theIncident Typesettings.