Exact Extract: “If there are conflicts with any unique constraints (in other words, a new record is evaluated as being a duplicate record), you can configure the Create Record step to do one of the following: Stop the create process… Do not create a new record (keep the existing intact)… Update existing record… Selectively update some fields of the existing record.”
Exact Extract: “Do not create a new record (keep the existing intact): The playbook does not make any changes to the existing record, and the subsequent steps of the playbook work on the existing record if they refer to this step result. The duplicate record does not cause the playbook to fail.”
The correct answers are B and D. Duplicate handling only works if the module has uniqueness conditions, such as unique username, email address, employee ID, or another reliable identity field. Without uniqueness conditions, FortiSOAR cannot determine whether an incoming user record is a duplicate. Then, in the Create Record step, you select Do not create new record (keep existing intact) so the existing user record is not overwritten and the playbook does not fail when a duplicate is encountered.
A is wrong because it stops the playbook on duplicates. C is wrong because parallel execution affects processing behavior and speed, not duplicate protection or overwrite behavior.
Technical Deep Dive: The right design is: configure uniqueness at the module level, then choose duplicate behavior at the Create Record step. For user ingestion, use stable identifiers. Do not use mutable display names as uniqueness keys. In bulk or loop-based creation, this prevents duplicate records while allowing clean records to continue. This is FortiSOAR database and workflow logic; FortiGate NP/CP offloading is irrelevant.
