Free Adobe AD0-E902 Übungsprüfungen - Seite 2 von 3

Question #10

A source system should provide a Workfront task ID, but queries keep resulting in an error.

Which module helps determine if the task ID is valid?

A . Read Record
B . Read Related Record
C . Search Record

Lösung einblenden Lösung ausblenden

Question #12

A Fusion scenario is triggered by a project status update. The scenario then updates the status, causing repeated execution of the scenario.

Which action should a user take to keep this from happening?

A . When using instant triggers, finish the scenario with the Break directive to prevent the record from being updated again
B . Create a filter after the instant trigger that only passes records that have not been updated by Fusion
C . Schedule the instant trigger to only run at intervals to prevent Fusion from thinking the record has been updated after each run

Lösung einblenden Lösung ausblenden

Question #13

Given the array below, a user wants a comma-separated string of all stat names.

What is the correct expression?

A)

B)

C)

D)

A . Option A
B . Option B
C . Option C
D . Option D

Lösung einblenden Lösung ausblenden

Richtige Antwort: B
B

Explanation:

Understanding the Requirement:

The input is an array containing objects, and the goal is to extract all the stat.name values into a comma-separated string.

Example Input:

[

{

"base_stat": 48,

"effort": 1,

"stat": {

"name": "hp",

"url": "https://pokeapi.co/api/v2/stat/1/"

}

},

{

"base_stat": 48,

"effort": 0,

"stat": {

"name": "attack",

"url": "https://pokeapi.co/api/v2/stat/2/"

}

}

]

Example Output:

"hp, attack"

Why Option B is Correct:

The expression join(map(2.data: stats[]; stats.stat.name); ", "):

map: Iterates through each object in the array (2.data: stats[]) and extracts the stat.name field.

join: Combines the extracted values into a single string, separated by a comma and space (", ").

Breaking it down:

map(2.data: stats[]; stats.stat.name) → Creates an array of names: ["hp", "attack"].

join(…; ", ") → Converts the array into the string "hp, attack".

Why the Other Options are Incorrect:

Option A: join(2.data: stats[]; stat.name; ", ")

This syntax is incorrect because it attempts to directly access stat.name within the join function without first mapping the values.

Option C: join(map(2.data: stats[]; stat.name); ", ")

The mapping references stat.name directly but does not account for the nested structure (stats.stat.name).

Option D: join(flatten(2.data: stats[]); ", ")

The flatten function is unnecessary here as the data is already structured. It would not properly extract the stat.name values.

Steps to Implement in Workfront Fusion:

Add a Mapping/Transformation Module.

Use the join(map(…)) function as described to transform the input array into a comma-separated string.

Test the output to ensure it correctly generates the desired format.

How This Solves the Problem:

The map function ensures the proper extraction of nested stat.name values. The join function combines these values into the desired format efficiently. Reference and Supporting Documentation:

Adobe Workfront Fusion Functions Documentation

Workfront Community: Using Map and Join Functions

The combination of map and join ensures that the stat names are extracted and formatted into a single comma-separated string, as required.

Question #14

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

Lösung einblenden Lösung ausblenden

Richtige Antwort: 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 #15

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

Lösung einblenden Lösung ausblenden

Question #16

A solution requested for a use case requires that the scenario is initiated with project updates.

Which Workfront app module will start the scenario immediately?

A . Watch Events
B . Watch Record
C . Watch Field
D . Search

Lösung einblenden Lösung ausblenden

Richtige Antwort: A
A

Explanation:

Understanding the Question:

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

Question #17

A Fusion user notices that a third-party web service is sometimes returning a connection error -" "service is not reachable". However, the module executes successfully a few minutes later in a new execution.

Which action increases the success rate of the executions?

A . Adding an error handler that will notify the system owner
B . Making use of the default error handling
C . Adding a Break directive to the module

Lösung einblenden Lösung ausblenden

Question #18

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: