Adobe AD0-E902 Exam Dumps

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

Step by Step Comprehensive Detailed Explanation:

Problem Summary:

The organization requires a process to track every project update made by Fusion to meet compliance standards.

This process must provide a clear audit trail of updates, including details like user and timestamp.

Option Analysis:

A . Use reporting on the Last Updated by ID and Last Update Date:

While this provides basic reporting, it only reflects the most recent update and does not maintain a comprehensive history of changes over time.

B . Update the External Reference ID with User ID and Timestamp:

Updating the External Reference ID could cause issues if this field is used for other purposes. It is not designed for logging multiple updates.

C . Create a Note record related to the record updated:

Correct. Creating a Note record for each update ensures that every change is logged with relevant details (e.g., user, timestamp, update reason). This approach creates a full audit trail that is easily accessible and reportable.

Why Note Records are Best:

Audit Trail: Notes provide a clear and searchable history of updates for each project.

Compliance: Ensures compliance by documenting who made what changes and when.

Flexibility: Notes can include custom details such as update reasons or additional context, making them more robust than standard fields.

Implementation:

In the Fusion scenario, add a module to create a Note record after each update.

Populate the Note with relevant details, such as:

User ID ({lastUpdatedBy})

Timestamp ({lastUpdateDate})

Description of the change.

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

Understanding the Issue:

The customer is syncing 20,000+ Salesforce Opportunities with Workfront projects using a scheduled Fusion scenario.

After running for 40 minutes, the scenario unexpectedly stops.

Why Option C is Correct:

Workfront Fusion Execution Timeout:

Fusion scenarios have a default execution timeout of 40 minutes per run.

If the scenario exceeds this time limit, Fusion automatically stops the execution to avoid resource overuse.

Handling Large Data Sets:

Scenarios involving large datasets (like syncing 20,000+ records) may require optimizations, such as breaking the data into smaller chunks using paginated requests or iterators.

In this case, the scenario stopped because the execution timeout was reached, not due to API limits or webhook restrictions.

Why the Other Options are Incorrect:

Option A ('Workfront API call limit'):

While Workfront does have API rate limits, they are generally generous and not the reason for the scenario stopping. Fusion scenarios are designed to manage API calls efficiently.

Option B ('Fusion times out if processing over 2000 records in 40 minutes'):

This is incorrect because Fusion does not have a hard limit on the number of records processed in 40 minutes. The timeout is time-based, not record-based.

Option D ('Workfront API stops webhooks after 2000 hits in 10 minutes'):

This does not apply to Fusion scenarios. Webhooks are separate from the API calls initiated by Fusion.

How to Resolve the Issue:

Split the Data: Use pagination or batch processing to divide the 20,000+ records into smaller chunks (e.g., 1,000 or 2,000 records per run).

Adjust Scheduling: Schedule the scenario to run more frequently with smaller batches, ensuring all records are synced over multiple runs.

Use Iterators: Add an Iterator module to loop through smaller subsets of data, preventing the scenario from exceeding the execution timeout.

Steps to Optimize the Scenario:

Add a Search Module to retrieve opportunities in smaller batches (e.g., using limits or pagination parameters).

Use a Repeater Module to process each batch iteratively.

Save the scenario and schedule it to run nightly or more frequently, depending on the sync requirements.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Execution Timeout Limits

Workfront Community: Managing Large Data Sets in Fusion Scenarios

By optimizing the scenario to handle smaller batches of data, the admin can avoid the execution timeout issue and ensure successful syncing of Salesforce Opportunities with Workfront projects.

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.