Adobe AD0-E902 Dumps Questions Answers

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)

References and Supporting Documentation :

Adobe Workfront Fusion Functions Documentation

Workfront Community: Handling Conditional Logic and Date Formatting

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.

References 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.

Step by Step Comprehensive Detailed Explanation :

Understanding the Scenario :

The diagram shows two routes, each leading to an aggregator module (Aggregator 1 and Aggregator 2).

The bundle inspector indicates different output counts for the two aggregators: Aggregator 1 displays 1, and Aggregator 2 displays 10.

Option Analysis :

A. Aggregator 1’s route is set to process the 1st bundle only, and Aggregator 2's route is set to process all bundles :

Incorrect. Aggregators process data from their input modules based on their configuration. While filters or limits might be applied earlier in the flow, the scenario does not suggest that the aggregator's configuration explicitly limits bundles in this way.

B. The source module for the aggregators are different :

Correct. The two aggregators receive input from different modules. For example, Aggregator 1 might aggregate bundles from "Projects," which outputs a single bundle, while Aggregator 2 aggregates bundles from "Issues," which outputs 10 bundles. This explains the differing numbers in the bundle inspector.

C. Aggregator 2 displays a 10 in the bundle inspector because it is set to repeat 10 times :

Incorrect. Aggregators do not "repeat" a specific number of times. Instead, they process the input bundles passed to them and output a result based on the aggregation logic.

D. The scenario's router is set to only allow projects through the route to Aggregator 1 and only allows tasks through the route to Aggregator 2 :

Incorrect. While the router might direct specific bundles (e.g., "Projects" to Aggregator 1 and "Issues" to Aggregator 2), the difference in bundle counts is determined by the source modules, not by the router's configuration alone.

Why Source Modules Determine Bundle Counts :

Each aggregator processes data from a source module. If the source module outputs different numbers of bundles, the aggregators will show different bundle counts.

In this example, "Projects" might output only 1 bundle (e.g., 1 project), while "Issues" outputs 10 bundles (e.g., 10 issues).

How to Verify :

Inspect the source modules feeding into each aggregator. Check the number of bundles they produce during the scenario run.

Confirm that the aggregators are aggregating based on their respective inputs.

References : This explanation aligns with Workfront Fusion's handling of bundles and aggregation logic. Differences in bundle counts at the aggregator level are typically due to differences in the source module outputs, as shown in the scenario.