Which two statements about working with incomplete executions are true? (Choose two.)

(D) When an incomplete execution is manually resolved, Adobe Workfront Fusion intelligently resumes the process from the specific module where the error originally occurred. It re-processes the exact bundle of data that caused the failure and continues it through the remainder of the scenario's modules. This ensures data integrity and avoids redundant processing of the entire workflow.
(B) The storage of incomplete executions is a behavior controlled by a specific setting within each scenario. While official documentation indicates this setting ("Allow storing of incomplete executions") is enabled by default on new scenarios, the core concept of the statement is correct: it is a configurable option that must be in an "enabled" state for the storage to occur. This makes it a more accurate choice than other options that fundamentally misrepresent the process.

A. This is incorrect because resolving an incomplete execution does not run the entire scenario. It specifically resumes from the point of failure with the failed data bundle.
C. This is incorrect because the primary purpose of storing and resolving incomplete executions is for error handling and data recovery to ensure a process completes successfully, not only to provide visibility for design improvements.

1. Adobe Experience League Documentation

"View and resolve incomplete executions in Adobe Workfront Fusion."

Reference for D: In the section "Resolve an incomplete execution

" the documentation states

"When you resolve an incomplete execution

Workfront Fusion starts the scenario again

beginning with the module that failed. The same bundle of data that caused the error is re-processed by that module."

Reference against A: The same sentence above confirms that the entire scenario is not re-run.

2. Adobe Experience League Documentation

"Scenario settings in Adobe Workfront Fusion."

Reference for B: This document details the scenario settings

including "Allow storing of incomplete executions

" confirming it is a configurable option. It notes

"This option is enabled by default

" which contradicts the first part of option B

but confirms the existence and necessity of the setting itself.

Reference against C: The existence of robust features for resolving incomplete executions underscores their purpose for operational recovery

not just as a design tool.