Free Adobe AD0-E902 Practice Exams - Page 3 of 3

Question #20

A Fusion user is trying to get a Google Slide presentation to connect to projects in Workfront.

Each time the user runs the scenario, this error message appears:

What action should the user take to resolve the error message?

A . Reauthorize their Google connection
B . Update Google sharing permissions for the document
C . Contact Workfront Support to troubleshoot the root cause
D . Search the Google status site to determine the cause

Reveal Solution Hide Solution

Question #22

Refer to the exhibit.

In this image, all items are displayed in a position that does not hide their execution sequence.

In what order do the modules execute?

A . Google Drive > Email > Workfront > Data Store > Salesforce
B . Email > Workfronl > Data Store > Salesforce > Google Drive
C . Email > Data Store > Workfront > Salesforce >
D . Google Drive Google Drive > Email > Data Store > Workfront > Salesforce

Reveal Solution Hide Solution

Correct Answer: D
D

Explanation:

Understanding the Diagram:

The image depicts a Workfront Fusion scenario using Routers to split and manage multiple execution paths.

Fusion executes modules in a left-to-right and top-to-bottom sequence along each path. Routers

direct the flow to downstream modules.

Determining the Execution Sequence:

Path 1:

The first path begins with Google Drive. The Router branches out, directing execution sequentially to

other modules.

Path 2:

The second path starts with Email and continues downwards through the remaining modules.

Order Within Branches:

After passing through a Router, each branch completes its sequence of modules before moving to the next Router.

Why Option D is Correct:

Execution begins from the leftmost module (Google Drive) and flows rightward. The sequence is as

follows:

Google Drive

Email

Data Store

Workfront

Salesforce

This matches the visual layout and Fusion’s execution rules for scenarios with Routers.

Why the Other Options are Incorrect:

Option A ("Google Drive > Email > Workfront > Data Store > Salesforce"): Incorrect because Workfront does not precede Data Store in the execution order.

Option B ("Email > Workfront > Data Store > Salesforce > Google Drive"): Incorrect because execution begins with Google Drive, not Email.

Option C ("Email > Data Store > Workfront > Salesforce"):

Incorrect because it excludes Google Drive as the starting point and places modules out of sequence.

Execution Rules in Workfront Fusion:

Fusion executes modules in the order they appear visually, starting from left to right and top to bottom within each branch.

Routers split the execution into separate branches, which are completed sequentially.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Execution Flow Rules

Workfront Community: Understanding Router and Module Execution

The correct execution sequence is Google Drive > Email > Data Store > Workfront > Salesforce, ensuring all paths are processed as per the scenario’s layout.

Question #23

In a scenario that searches for recently completed tasks, a user notices the following input and output for a date transformation.

Input: March 3, 2021 10:34 AM Output: March 1, 2021 10:34 AM

Which expression produces this date transformation?

A . subDays(now,2)
B . addHours(now; -48)
C . addDays(today; -4)

Reveal Solution Hide Solution

Question #24

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?

A . Select 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.
B . Use 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.
C . Set 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.

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

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

Question #25

A scenario is too large, with too many modules.

Which technique can reduce the number of modules?

A . Nesting multiple mapping panel functions instead of setting and resetting variables when transforming data in more than one way
B . Using a Compose a string module to combine variables and module output. Then use the Text Parser to parse the data and assign to variables
C . Setting the scenario to Auto Commit in scenario settings

Reveal Solution Hide Solution

Question #26

Which statement about the differences between instant and polling triggers is true?

A . To keep track of records processed, instant triggers store received webhooks in a queue, whereas polling triggers remember which records have already been processed
B . A user should use instant triggers when available because instant triggers allow Fusion to process bundles of data faster than polling triggers
C . A user must set up a webhook in Fusion to use Instant Triggers that make polling triggers easier to use and more reliable in scenarios
D . Only polling triggers can be set to run on a schedule and should be used to avoid shutdown of third-party systems during working hours

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

Understanding Instant and Polling Triggers:

Instant Triggers:

Rely on webhooks to receive real-time data from a third-party system.

The external system sends a notification (webhook) to Fusion whenever an event occurs, triggering

the scenario immediately.

Polling Triggers:

Regularly check (poll) the third-party system for new or updated records at scheduled intervals.

These are slower because they involve repeated API requests.

Why Option B is Correct:

Speed and Efficiency:

Instant triggers process data faster because they act immediately upon receiving a webhook. Polling

triggers, on the other hand, may take time depending on the polling frequency and can result in

unnecessary delays.

Reduced Load on Systems:

Instant triggers generate fewer API calls than polling triggers, which continuously check for new records even if no changes have occurred.

Best Practice: Use instant triggers whenever supported by the third-party system to ensure faster and

more efficient scenario execution.

Why the Other Options are Incorrect:

Option A ("Instant triggers store received webhooks in a queue"):

Webhooks do not store data in a queue; they simply notify Fusion of events in real-time. Polling triggers also do not store records but remember the last processed record. Option C ("A user must set up a webhook in Fusion"):

Instant triggers require setting up webhooks in the external system, not in Fusion. Fusion provides the webhook endpoint, but the user must configure the source system to send data. Option D ("Only polling triggers can be set to run on a schedule"):

This is incorrect because instant triggers do not rely on schedules; they operate in real-time. Polling triggers, however, run on schedules and are used when instant triggers are unavailable. Reference and Supporting Documentation:

Adobe Workfront Fusion Triggers Documentation

Workfront Community: Differences Between Instant and Polling Triggers

Instant triggers are the preferred option when available, as they provide real-time data processing with greater speed and efficiency than polling triggers.