You are investigating an open incident and want to add records from the Tickets module,...

Exact Extract: “The incidents module includes the visual correlation widget in its default layout, which displays related records linked to the incident. By default, the incidents module is correlated to the alerts, indicators, vulnerabilities, and assets modules. If there are records linked to the incident, either directly or indirectly through another linked record, they are displayed in the visual correlation widget. You can define more module correlation relationships in Application Editor > Correlation Settings.”

The correct answer is D because the visual correlation widget does not simply show every linked custom-module record automatically unless the module relationship is defined for correlation. Since the question states that ticket records are already linked to the incident, ingestion is not the issue, so A is wrong. Tagging records with the incident ID is also not the FortiSOAR mechanism for displaying them in the visual correlation graph, so B is wrong. Editing the incident template can change how the incident record layout is displayed, but it does not define the underlying module correlation logic, so C is wrong. The required action is to define the relationship between the Incidents module and the custom Tickets module under Application Editor > Correlation Settings . Once that module relationship exists, FortiSOAR can render the linked Tickets records in the visual correlation widget.

Technical Deep Dive: In FortiSOAR, visual correlation is metadata-driven. The graph depends on module relationship definitions, not only on UI layout. The incident template controls presentation; Correlation Settings control which linked records are eligible to appear as graph nodes and edges. This is why a custom module such as Tickets must be added as a correlation relationship before it appears in the incident graph. Hardware offloading such as FortiGate NP/CP acceleration is irrelevant here because this is FortiSOAR application-layer correlation logic, not packet forwarding or content inspection.