Adobe Exam AD0-E902 Topic 1 Question 9 Discussion

Actual exam question for Adobe's AD0-E902 exam

Question #: 9
Topic #: 1

A global customer has end users who input date and currency data into fields in inconsistent formats. Despite continued training efforts, this continues to be an issue. Unfortunately, the third-party service that the end users are using does not support forcing a required field format. These input mistakes do not happen frequently, but they currently stop the scenario from executing after the default three retries.

In Fusion, which action can the admin take to ensure that errors are corrected after they occur in a scenario?

ASelect storing of Incomplete Executions in the scenario settings. The customer admin can then filter and search the execution history to resolve errors as they occur.

BUse the switch module to catch dates not in the required format and convert the common misused patterns into the appropriate format to prevent the scenario from stopping after three failed executions.

CSet up an error handling path that will catch errors in the end user's inputs and message the users in an email update that they need to try again.

Show Suggested Answer

Suggested Answer: A

Understanding the Scenario:

The issue involves end users inputting inconsistent date and currency formats that result in errors in a Workfront Fusion scenario.

The default behavior of Fusion stops the scenario after three retries due to input mismatches or invalid formats.

Why Option A is Correct:

Storing Incomplete Executions: In Adobe Workfront Fusion, enabling 'Store incomplete executions' in the scenario settings allows administrators to capture incomplete runs without fully stopping the entire process. This feature stores all relevant data, even from incomplete runs, allowing administrators to identify and correct input issues manually.

Error Troubleshooting: By reviewing incomplete executions, admins can pinpoint where the scenario failed, resolve the issue, and potentially reprocess those incomplete records, preventing complete scenario stoppage.

Why Option B is Incorrect:

The 'switch module' can handle specific input variations, but it is not a comprehensive solution for handling unexpected or inconsistent formats entered by end users. While it might mitigate some errors, it does not address the root cause and can miss unanticipated input patterns.

Why Option C is Incorrect:

Setting up an error handling path to notify users and request corrections adds an additional manual step for users but does not resolve the problem efficiently within Fusion. Moreover, this solution does not prevent the scenario from halting after retries.

Steps to Enable Storing Incomplete Executions:

Navigate to the scenario in Adobe Workfront Fusion.

Open the Scenario Settings by clicking the gear icon.

Enable the option Store Incomplete Executions under Execution settings.

Save the settings and activate the scenario.

How This Solves the Problem:

Enabling this setting ensures that no data is lost when the scenario fails due to inconsistent inputs. Admins can access the incomplete executions through the scenario execution history, apply necessary corrections, and retry specific records or steps as needed.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Scenario Settings

Workfront Community: Handling Incomplete Executions

by Tresa at Apr 08, 2025, 09:45 PM

Limited Time Offer

25%

Off

Get Premium AD0-E902 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Ricki

18 days ago

I've got a radical idea - what if we just hire a team of professional date and currency formatters to sit next to the end users and input the data for them? Just a thought. But barring that, option C seems like the most straightforward way to deal with this problem.

upvoted 0 times

...

Mila

20 days ago

Hmm, tough one. Option B sounds like a clever way to handle those pesky date and currency format issues, but it might be a bit of a band-aid solution. I'd lean towards option C - at least then we can keep the users in the loop and make them accountable for their own data blunders.

upvoted 0 times

...

2 months ago

I think option A is the best choice. Storing incomplete executions will help the admin to easily identify and correct errors.

upvoted 0 times

...