QUESTION: 13

A Fusion user is developing a scenario. The first half of the scenario needs to be tested for consistency. No additional actions are to be executed.
Which control module is required to disable the execution of subsequent modules?

Router
Sleep
Ignore
Break

Answer(s): D

Explanation:

Understanding the Requirement:
The user wants to test the first half of the scenario for consistency without executing the remaining modules.
This requires halting further execution after a specific point in the scenario.
Why Option D ("Break") is Correct:
The Break module is a flow control module in Adobe Workfront Fusion that stops the execution of all subsequent modules in the scenario.
It is specifically designed for scenarios where you want to terminate execution after testing or processing a portion of the flow.
Example Use Case: After ensuring the first set of modules processes data correctly, the Break module prevents the execution of later modules to avoid unintended actions or changes.
Why the Other Options are Incorrect:
Option A ("Router"):
The Router splits the execution flow into multiple branches but does not stop the execution of subsequent modules.
Option B ("Sleep"):
The Sleep module pauses execution for a specified time but does not disable subsequent modules permanently.
Option C ("Ignore"):
There is no "Ignore" module in Workfront Fusion.
Steps to Use the Break Module:
Insert the Break module at the point where you want to stop execution. Save and run the scenario to test the flow up to the Break module. Once satisfied with the results, remove or bypass the Break module to continue testing or finalizing the full scenario.
How This Solves the Problem:
The Break module allows targeted testing of specific sections of the scenario while preventing unwanted execution of subsequent actions, making it a safe and efficient way to debug workflows.
Reference and Supporting Documentation:
Adobe Workfront Fusion Flow Control Modules Documentation Workfront Community: Using the Break Module in Scenario Development

Reveal Solution Next Question

QUESTION: 14

A CSV export from another system provides columns of information about Purchase Orders. The graphic below includes information from each column and an example of data from one row:
The customer wants this information in the title of their Workfront projects in the following order:
1.PO#
2. Name
3. PO Fulfillment Date
4. If a discount was given, include the Discount% and the Approver's Last Name. Ex. 2837 - Compendium-Premium Running Shoes - 21 /02/16 -15% Discount - UserLast Which expression below represents the project name that the customer wants?

Answer(s): A

Explanation:

Understanding the Requirement:
The project name in Workfront must include:
Purchase Order Number (PO#).
Name of the product.
PO Fulfillment Date (formatted as YY/MM/DD).
If a discount is provided, append the discount percentage and the approver's last name in the format: 15% Discount - UserLast.
Example Output:
sql
Copy
2837 - Compendium-Premium Running Shoes - 21/02/16 - 15% Discount - UserLast Why Option A is Correct:
The expression in Option A achieves the desired result step-by-step:
3.PO#: Includes the PO number.
3.Name: Appends the name of the product.
formatDate(3.PO Fulfillment Date, YY/MM/DD): Formats the PO Fulfillment Date in the desired

YY/MM/DD format.
if(3.Discount Provided? = "Yes"; "- " + 3.Discount % + " Discount - " + 3.Approver Last Name):
Uses the if function to check if a discount was provided. If "Yes," it appends the discount percentage (3.Discount %) and approver's last name (3.Approver Last Name) with the required format.
Why the Other Options are Incorrect:
Option B:
The expression is incorrect because it places if(3.Discount Provided?...) directly after PO Fulfillment Date without using formatDate for date formatting. This results in an unformatted date.
Option C:
Uses parseDate instead of formatDate, which is incorrect in this context. parseDate is used to interpret strings as dates, not to format dates for output.

Option D:
The expression does not include any conditional logic for checking if a discount is provided. It simply appends Discount - Approver Last Name regardless of whether a discount was given.
Steps to Use the Expression in Workfront Fusion:
Place the expression in the module that defines the project title in Workfront. Map the fields (PO#, Name, PO Fulfillment Date, etc.) to the respective columns from the CSV data. Test the scenario to ensure the output matches the desired format.
Final Expression (Option A):

3.PO# + " - " + 3.Name + " - " + formatDate(3.PO Fulfillment Date; YY/MM/DD) + if(3.Discount Provided? = "Yes"; " - " + 3.Discount % + " Discount - " + 3.Approver Last Name) Reference and Supporting Documentation:
Adobe Workfront Fusion Functions Documentation
Workfront Community: Handling Conditional Logic and Date Formatting

Reveal Solution Next Question

QUESTION: 15

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

What is the correct expression?

Answer(s): 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.

Reveal Solution Next Question

QUESTION: 16

Which action makes it possible to see the exact API request and the response a module executes?

Using the Bundle Inspector
Using the execution history
Using the Fusion DevTool scenario debugger
Using the Fusion DevTool error evaluator

Answer(s): B

Explanation:

Understanding the Requirement:
The user needs to view the exact API request and the corresponding response a module executes in Adobe Workfront Fusion.
This is critical for debugging, troubleshooting, or validating API operations within scenarios.
Why Option B is Correct:

Execution History:
The execution history logs detailed information about every module that runs in a scenario. It provides access to the API request sent, including the headers, parameters, and body. It also displays the API response received, including HTTP status codes, returned data, and error messages (if applicable).
This feature is indispensable for debugging and verifying the behavior of modules.
Why the Other Options are Incorrect:
Option A ("Using the Bundle Inspector"):
The Bundle Inspector provides a view of processed data bundles but does not include API request/response details.
Option C ("Using the Fusion DevTool scenario debugger"):
Fusion does not have a specific "DevTool debugger." The execution history serves this purpose.
Option D ("Using the Fusion DevTool error evaluator"):
While error logs help evaluate issues, they do not directly show the API request/response unless an error occurs. Execution history is a more comprehensive source of this data.
Steps to View Execution History:
Run the scenario or inspect a previously executed scenario.
Navigate to the Execution History tab for the scenario.
Select a specific module to view its details.
Inspect the API request and response, which includes all relevant parameters and data.
Reference and Supporting Documentation:
Adobe Workfront Fusion Documentation: Execution History
Workfront Community: Debugging with Execution History

Reveal Solution Next Question

Free AD0-E902 Exam Braindumps (page: 5)

QUESTION: 13

Explanation:

QUESTION: 14

Explanation:

QUESTION: 15

Explanation:

QUESTION: 16

Explanation:

AD0-E902 Exam Discussions & Posts