Adobe AD0-E902 Exam Questions

Understanding the Scenario:

The image represents a Workfront Fusion scenario with a Workfront module, HTTP modules, and routers splitting the execution path.

The goal is to reuse multiple fields from the Workfront module (e.g., data extracted or processed earlier in the flow) as mapped expressions in HTTP PUT requests located in the bottom paths.

Why Option A is Correct:

Set Multiple Variables Module: This module allows you to define and store multiple variables at a single point in the scenario (e.g., after the Workfront module). These variables can then be reused throughout subsequent steps in the scenario.

Get Multiple Variables Module: By placing this module between the Text Parser and the bottom Router, you can retrieve all previously stored variables, ensuring consistent access across all branches of the flow. This avoids redundancy and ensures the data is easily accessible for each HTTP request in the bottom paths.

Why the Other Options are Incorrect:

Option B ('Set Multiple Variables after Workfront, Get Variables before each HTTP module'): This is partially correct but less efficient. Adding multiple Get Variable modules before each HTTP request results in repetitive configuration and increases maintenance complexity.

Option C ('Set Variable and Get Variable for each HTTP module'): Using individual Set and Get Variable modules increases duplication. This approach requires separate variables for each data point, which is inefficient compared to using the Set/Get Multiple Variables module for multiple fields at once.

Steps to Configure the Solution:

After the Workfront module:

Add a Set Multiple Variables module.

Define all the fields required for the HTTP PUT requests as variables, mapping them from the Workfront module outputs.

Between the Text Parser and the bottom Router:

Add a Get Multiple Variables module.

Retrieve the previously stored variables, ensuring they are accessible for all paths.

In the HTTP modules on each bottom path:

Use the retrieved variables for mapping in the PUT requests.

How This Solves the Problem:

This approach centralizes variable management, making it easier to access and modify data as needed.

It avoids redundancy, as variables are defined once and reused across all paths, reducing the risk of errors and ensuring consistency.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Variables Module Overview

Workfront Community: Efficient Use of Variables in Fusion

Understanding the Questio n:

The scenario must begin as soon as a project update occurs in Adobe Workfront.

The correct Workfront module should continuously monitor for specific changes (in this case, project updates) and trigger the scenario immediately.

Why Option A ('Watch Events') is Correct:

Watch Events Module: This module in Adobe Workfront Fusion is specifically designed to monitor events, such as updates to projects, tasks, or issues, and trigger scenarios as soon as those events occur.

Real-Time Triggering: The 'Watch Events' module listens to the Workfront event stream and ensures the scenario starts immediately upon detecting relevant updates.

Example Use Case: Monitoring updates to a project's status, such as changes in 'Completion' or 'Progress,' to trigger notifications or integrations with other systems.

Why the Other Options are Incorrect:

Option B ('Watch Record'): This module monitors specific Workfront records (e.g., projects, tasks, issues) for new additions or modifications, but it does not initiate scenarios immediately when updates occur. It works better for periodic checks rather than real-time events.

Option C ('Watch Field'): This module monitors changes to specific fields within a Workfront object, but it is not designed for broader event monitoring like project updates. It is more suited for field-specific tracking.

Option D ('Search'): This module performs queries to find specific data in Workfront (e.g., searching for projects based on criteria), but it is not an event-driven module and does not automatically trigger scenarios.

Steps to Configure the Watch Events Module in Workfront Fusion:

In the Fusion scenario editor, add the Watch Events module as the first step in your scenario.

Configure the module:

Select Workfront Connection: Choose the authorized Workfront account.

Event Object: Specify the object type (e.g., Project, Task, Issue) to monitor.

Event Type: Select the type of event to watch, such as 'Update' or 'Change.'

Save and activate the scenario.

How This Solves the Problem:

Using the Watch Events module ensures the scenario is event-driven and starts automatically when the desired project update occurs. This approach is both efficient and timely, meeting the requirement for immediate initiation.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Watch Events Module

Workfront Community Forum: Use Cases for Watch Events

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

Understanding the Questio n:

The scenario must begin as soon as a project update occurs in Adobe Workfront.

The correct Workfront module should continuously monitor for specific changes (in this case, project updates) and trigger the scenario immediately.

Why Option A ('Watch Events') is Correct:

Watch Events Module: This module in Adobe Workfront Fusion is specifically designed to monitor events, such as updates to projects, tasks, or issues, and trigger scenarios as soon as those events occur.

Real-Time Triggering: The 'Watch Events' module listens to the Workfront event stream and ensures the scenario starts immediately upon detecting relevant updates.

Example Use Case: Monitoring updates to a project's status, such as changes in 'Completion' or 'Progress,' to trigger notifications or integrations with other systems.

Why the Other Options are Incorrect:

Option B ('Watch Record'): This module monitors specific Workfront records (e.g., projects, tasks, issues) for new additions or modifications, but it does not initiate scenarios immediately when updates occur. It works better for periodic checks rather than real-time events.

Option C ('Watch Field'): This module monitors changes to specific fields within a Workfront object, but it is not designed for broader event monitoring like project updates. It is more suited for field-specific tracking.

Option D ('Search'): This module performs queries to find specific data in Workfront (e.g., searching for projects based on criteria), but it is not an event-driven module and does not automatically trigger scenarios.

Steps to Configure the Watch Events Module in Workfront Fusion:

In the Fusion scenario editor, add the Watch Events module as the first step in your scenario.

Configure the module:

Select Workfront Connection: Choose the authorized Workfront account.

Event Object: Specify the object type (e.g., Project, Task, Issue) to monitor.

Event Type: Select the type of event to watch, such as 'Update' or 'Change.'

Save and activate the scenario.

How This Solves the Problem:

Using the Watch Events module ensures the scenario is event-driven and starts automatically when the desired project update occurs. This approach is both efficient and timely, meeting the requirement for immediate initiation.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Watch Events Module

Workfront Community Forum: Use Cases for Watch Events

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