Free AD0-E902 Exam Braindumps (page: 4)

Page 3 of 14

What two module outputs does a user receive from this expression? (Choose two.)

  1. Non-empty array
  2. An empty field
  3. Text value'No Type"
  4. Collections comma separated

Answer(s): A,C

Explanation:

Understanding the Expression:
The provided expression uses the ifempty function:

ifempty(2.data:types[]; "No Type")
Structure of the Expression:
The first parameter, 2.data:types[], is an array being checked for content. The second parameter, "No Type", is the fallback value returned if the array is empty or undefined.

Purpose of ifempty: This function checks if the given value is empty or undefined. If the value is not empty, it returns the value. If the value is empty, it returns the fallback text ("No Type").
Expected Module Outputs:
A . Non-empty array:
If 2.data:types[] is a non-empty array, the function returns the array as-is.
C . Text value 'No Type':
If 2.data:types[] is empty or undefined, the function returns the fallback text value "No Type".
Why the Other Options are Incorrect:
Option B ("An empty field"):
The ifempty function does not return an empty field. If the value is empty, it substitutes it with the fallback text ("No Type").
Option D ("Collections comma separated"):
The function operates on arrays, but it does not format the output as comma-separated collections.
The raw array is returned if non-empty.
Key Use Cases:
This type of function is frequently used in Workfront Fusion to handle situations where data might be missing or incomplete, ensuring scenarios continue to run smoothly without errors caused by undefined or empty fields.
Example Outputs:
If 2.data:types[] = ["Type1", "Type2"]: The function returns ["Type1", "Type2"]. If 2.data:types[] = [] or undefined: The function returns "No Type".
Reference and Supporting Documentation:
Adobe Workfront Fusion Functions Reference
Workfront Community: Handling Empty Fields with ifempty



In a Fusion scenario, a new project in Workfront will trigger the creation of a new project in ServiceNow. The name of the project in ServiceNow will be constructed in the following format:
Two Digit Year - Reference Number - Project Name
Which expression will generate the correct string?

  1. formatDate(now;YY) - referenceNumber - name
  2. join(formatDate(now;YY) - referenceNumber - name)
  3. concat(formatDate(now;YY) - referenceNumber - name)

Answer(s): C

Explanation:

Understanding the Requirement:
The desired output format for the project name in ServiceNow is:
Two-Digit Year - Reference Number - Project Name
This requires dynamically constructing a string by combining:
The current year in a two-digit format.
The referenceNumber (a variable or input).
The name (a variable or input, likely the project name).

Why Option C is Correct:
The concat function combines multiple strings into a single string.
Expression:

concat(formatDate(now;YY), " - ", referenceNumber, " - ", name) This ensures proper formatting with hyphens and spaces between the elements.
Breaking Down the Components:
formatDate(now;YY): Retrieves the current year in a two-digit format (e.g., "23" for 2023).
" - ": Adds the required separator.
referenceNumber: Dynamically adds the reference number.
name: Dynamically adds the project name.
Why the Other Options are Incorrect:
Option A ("formatDate(now;YY) - referenceNumber - name"):
This is not valid because it does not explicitly use a string concatenation function. Option B ("join(formatDate(now;YY) - referenceNumber - name"):
The join function is used for concatenating elements of an array, not individual strings. Since the inputs are not in an array, this function will not work.
How This Solves the Problem:
The concat function correctly constructs the string with the desired format, dynamically generating the project name for ServiceNow based on the given inputs.
Reference and Supporting Documentation:
Adobe Workfront Fusion Functions Documentation
Workfront Community: Using the concat Function



A query returns a partial list of possible values.
Which flow control module should be used to ensure all the possible results are queried?

  1. Aggregator
  2. Repeater
  3. Iterator
  4. Router

Answer(s): B

Explanation:

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



Data coming from a third-party system contains a field that needs to be transformed into one of three possible choices.
Which function supports this transformation?

  1. Switch
  2. Slice
  3. Split

Answer(s): A

Explanation:

Understanding the Requirement:
The field data from a third-party system needs to be transformed into one of three possible choices. This transformation implies conditional logic, where the output depends on the value of the input field.
Why Option A ("Switch") is Correct:
The Switch function evaluates a given input against multiple cases and outputs a corresponding value based on the matched condition.

For example:

switch(field, "value1", "choice1", "value2", "choice2", "defaultChoice") If field equals "value1", the output is "choice1".
If field equals "value2", the output is "choice2".
If no conditions match, the output is "defaultChoice".
This functionality perfectly fits the requirement to transform the input into one of three possible choices.
Why the Other Options are Incorrect:
Option B ("Slice"):
The slice function is used for extracting a portion of a string or array but does not support conditional transformations.
Option C ("Split"):
The split function divides a string into an array based on a specified delimiter. It is not designed for conditional logic or value mapping.
How This Solves the Problem:
The Switch function allows flexible and dynamic transformations, ensuring the field data is mapped to the correct choice based on its value.
Reference and Supporting Documentation:
Adobe Workfront Fusion Functions Documentation
Workfront Community: Using the Switch Function for Conditional Logic






Post your Comments and Discuss Adobe AD0-E902 exam with other Community members:

AD0-E902 Exam Discussions & Posts