Adobe AD0-E902 Practice Exam Questions & Answers

Step 1: Query Workfront for User Based on Email Address

Salesforce provides the email address of the user. Since Workfront uses user IDs for task assignments, the email address can be used as a unique identifier to query Workfront's database.

A query module in Workfront Fusion retrieves the corresponding Workfront user ID using the provided email address.

Step 2: Assign Task Using Returned ID

After retrieving the Workfront user ID, use it in the assignment field of the task module in Fusion.

The task assignment process requires a valid user ID, ensuring proper linkage and assignment within Workfront.

Why Not Other Options?

A . Assign the task using the provided user ID > add the user ID to the assignment field: The Salesforce user ID is not recognized by Workfront. It is necessary to query Workfront to convert the email into a Workfront-compatible user ID.

C . Query Workfront based on the user's name > assign task using returned email address: Workfront uses user IDs, not email addresses, for task assignments. Names are also not unique and could cause assignment errors.

Adobe Workfront Fusion Documentation: Task Assignments Using User IDs

Experience League Community: Mapping Salesforce Data to Workfront Tasks

Understanding the Array and the Task:

Input Array (Colors):

[

{ 'ID': '22342', 'name': 'Red' },

{ 'ID': '33495', 'name': 'Blue' }

]

Goal: Extract the first ID from the array, which is '22342'.

Why Option B is Correct:

The expression get(map(2.Colors; ID); 1):

map(2.Colors; ID): Iterates over the array 2.Colors and extracts the ID field from each object. This creates a new array containing just the IDs: ['22342', '33495'].

get(...; 1): Retrieves the first element of the newly created array, which is '22342'.

Why the Other Options are Incorrect:

Option A (map(2.Colors; ID; ID; 1)):

This syntax is invalid because the additional ID and 1 parameters are misplaced. The map function requires only two arguments: the array and the field to map.

Option C (map(get(2.Colors; ID); 1)):

This incorrectly attempts to use get inside map. The get function does not return a field for mapping, so the syntax is invalid.

How the Expression Works:

Step 1: map(2.Colors; ID)

Extracts the ID field from each object in the Colors array.

Output: ['22342', '33495'].

Step 2: get(...; 1)

Retrieves the first element of the mapped array.

Output: '22342'.

Use Case in Workfront Fusion:

This approach is commonly used when processing arrays in Fusion scenarios, ensuring specific elements are accessed without additional looping or complex logic.

Reference and Supporting Documentation:

Adobe Workfront Fusion Functions Documentation

Workfront Community: Using Map and Get Functions

By combining map and get, this expression efficiently extracts the first ID from the array, ensuring correct and reliable results.

Understanding the Requirement:

The query returns only a partial list of possible values.

The task is to ensure that all results are processed by iterating through multiple queries or pages of data.

Why Option B ('Repeater') is Correct:

The Repeater module is designed to repeat an operation a specified number of times or until a condition is met.

It is commonly used for querying paginated data or when a system limits the number of records returned in a single request.

In this case, the Repeater ensures all possible values are queried by making additional requests to retrieve subsequent pages or results.

Why the Other Options are Incorrect:

Option A ('Aggregator'):

The Aggregator combines multiple data bundles into a single output. It does not handle iterative queries or pagination.

Option C ('Iterator'):

The Iterator splits an array into individual items for processing. It does not handle querying for additional data or looping through requests.

Option D ('Router'):

The Router splits the flow of a scenario into multiple paths based on conditions. It is unrelated to iterative querying.

Steps to Configure the Repeater:

Add the Repeater module to your scenario.

Configure the number of repetitions or the condition to continue querying (e.g., based on the presence of additional data).

Link the Repeater to the module responsible for retrieving the data, ensuring it processes all available results.

How This Solves the Problem:

The Repeater module ensures that all possible results are queried by iteratively sending requests until no more data is available.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Repeater Module Documentation

Workfront Community: Using Flow Control Modules

Understanding the Requirement:

If a third-party system does not have a dedicated app connector in Workfront Fusion, users can still build an integration using Universal Connectors.

Universal Connectors in Fusion allow users to configure custom API calls, enabling communication with systems that lack pre-built integrations.

Steps to Build the Integration:

Determine the API Structure: Review the third-party system's API documentation to understand the available endpoints, data formats (e.g., JSON, XML), and request/response structure.

Identify Authentication Protocols: Determine how the third-party system handles authentication (e.g., API keys, OAuth 2.0, Basic Auth).

Configure the Universal Connector: Use modules like HTTP Request or Webhook to make API calls to the third-party system based on the documented structure.

Why Not Other Options?

B . Create a new connection to the third-party system in the connections area and then the Universal Connectors will be available for use: Creating a new connection in the connections area is only applicable for predefined connectors, not for Universal Connectors, which require manual configuration for unsupported systems.

C . Use the Workfront Custom API module to set up the connection using API calls to the third-party system: The Workfront Custom API module is specifically designed for Workfront's own API, not for connecting to third-party systems.

Adobe Workfront Fusion Documentation: Using Universal Connectors for Custom Integrations

Experience League Community: Integrating Third-Party Systems Using Workfront Fusion Universal Modules

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

Key Scenario Settings:

Adobe Workfront Fusion provides settings to control the execution of scenarios. These settings impact how the scenario behaves when it runs, especially under conditions such as errors or long-running processes.

Explanation of Correct Options:

Option A ('Number of consecutive errors'):

This setting determines the maximum number of consecutive errors allowed before the scenario execution halts.

By adjusting this value, users can define how resilient the scenario is to temporary failures in modules or external systems.

Option B ('Max number of cycles'):

This setting limits the maximum number of cycles (iterations) the scenario performs in a single run.

It prevents scenarios from running indefinitely or consuming excessive resources in cases of large datasets.

Why the Other Options are Incorrect:

Option C ('Number of bundles per run'): This value is not adjustable in the scenario settings. Instead, the system dynamically determines how many bundles (data packets) are processed per cycle.

Option D ('Number of consecutive runs'): Workfront Fusion does not have a setting for the number of consecutive runs. Scenarios are executed based on schedules, triggers, or manual execution.

Steps to Adjust Scenario Settings:

Open the scenario in Adobe Workfront Fusion.

Click the gear icon in the top-right corner to access Scenario Settings.

Locate and adjust the following fields:

Number of consecutive errors: Set a value based on acceptable failure tolerance.

Max number of cycles: Specify the maximum number of iterations allowed.

Save and activate the scenario.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Scenario Settings

Workfront Community: Best Practices for Scenario Optimization

In Adobe Workfront Fusion, error handling directives are used to manage and respond to errors during scenario execution. These directives allow the implementation of conditional or nested error handling mechanisms, ensuring workflows can adapt and recover from unexpected issues efficiently. Among the features and modules provided by Fusion:

Filters:

Filters are essential components in Workfront Fusion. They allow you to define specific conditions to control the flow of data between modules.

They enable conditional processing by allowing or restricting the passage of data based on defined criteria, which is fundamental for creating dynamic and conditional workflows.

When used with error handling, filters can evaluate whether certain data meets criteria to determine alternative pathways, thus enabling conditional error handling.

Routers:

Routers split the execution of a scenario into multiple branches based on specific conditions.

Each branch can be configured to handle different error types or conditions, allowing nested error handling and custom error recovery paths.

They are particularly useful when you need to define distinct responses for various error cases within a single scenario.

Eliminated Options:

A . Text Parser: While text parsers process and extract data from strings, they are not directly involved in error handling within scenarios.

C . Workfront App: The Workfront app is primarily for interacting with Workfront features and functionalities, not directly related to error handling within Fusion scenarios.

Adobe Workfront Fusion Documentation: Error Handling Directives Overview

Adobe Workfront Community: Filters and Routers in Conditional Logic Workflows

Experience League Documentation: https://experienceleague.adobe.com