Adobe Workfront Fusion Developer Professional AD0-E902 Exam Questions

Answer : B

Step 1: Query Workfront for User Based on Email Address

Salesforce provides the email address of the user. Since Workfront uses user IDs for task assignments, the email address can be used as a unique identifier to query Workfront's database.

A query module in Workfront Fusion retrieves the corresponding Workfront user ID using the provided email address.

Step 2: Assign Task Using Returned ID

After retrieving the Workfront user ID, use it in the assignment field of the task module in Fusion.

The task assignment process requires a valid user ID, ensuring proper linkage and assignment within Workfront.

Why Not Other Options?

A . Assign the task using the provided user ID > add the user ID to the assignment field: The Salesforce user ID is not recognized by Workfront. It is necessary to query Workfront to convert the email into a Workfront-compatible user ID.

C . Query Workfront based on the user's name > assign task using returned email address: Workfront uses user IDs, not email addresses, for task assignments. Names are also not unique and could cause assignment errors.

Adobe Workfront Fusion Documentation: Task Assignments Using User IDs

Experience League Community: Mapping Salesforce Data to Workfront Tasks

Answer : B

Understanding the Issue:

The user observes that all task due dates are incorrect due to a mismatch in the time zone.

The solution must ensure that the correct time zone is applied universally across all scenarios and dates within the organization's Fusion instance.

Why Option B is Correct:

Fusion Organization's Time Zone Setting:

Changing the time zone at the organization level ensures that all scenarios within the organization adopt the updated time zone setting.

This change applies globally, making it the simplest and most efficient method to ensure consistency across all dates and scenarios.

This adjustment prevents the need for scenario-specific or localized changes, saving time and reducing errors.

Why the Other Options are Incorrect:

Option A ('Set a variable for every date using formatDate'):

While the formatDate function can adjust time zones for individual dates, applying this approach to every date in every scenario is highly inefficient and error-prone. It does not offer a global solution.

Option C ('Change the scenario's time zone default'):

Scenarios in Fusion do not have a specific 'time zone default' setting. The organization's time zone setting is the controlling factor.

Option D ('Change the time zone in the computer's localization settings'):

Fusion scenarios run on cloud servers, not the user's local machine. Changing the computer's time zone would have no effect on the scenarios' behavior.

Steps to Change the Organization's Time Zone:

Log in to Adobe Workfront Fusion.

Navigate to the Organization Settings:

Go to the Admin Panel or the organization settings section.

Locate the Time Zone setting.

Select the desired time zone from the dropdown list.

Save the changes.

All scenarios will now adopt the updated time zone setting.

How This Solves the Problem:

Changing the organization's time zone applies a consistent time zone across all dates used in scenarios. This ensures accuracy without requiring individual scenario adjustments or manual interventions.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Organization Settings

Workfront Community: Best Practices for Time Zone Configuration

Answer : A, B

Object ID in CRUD Operations: REST APIs commonly use CRUD operations to interact with resources. The Object ID serves as a unique identifier for the resource and is generally required for the following actions:

A . Update:

To update a specific resource, the API must know which resource to modify. The Object ID is used to identify the exact resource that should be updated.

Example: A PUT or PATCH request typically requires the Object ID in the URL or body of the request.

URL Example:

PUT /tasks/{id}

B . Delete:

Similarly, when deleting a specific resource, the Object ID is needed to ensure the correct resource is removed.

Example: A DELETE request requires the Object ID in the URL to target the specific resource.

URL Example:

DELETE /tasks/{id}

Why Not Other Options?

C . Respond: This is not a standard CRUD operation in REST APIs and does not involve an Object ID.

D . Create: The Create operation (typically POST) does not require an Object ID because the resource does not yet exist. Instead, the API usually generates the Object ID after creation.

REST API Documentation Best Practices: CRUD Operations

Experience League: Understanding CRUD in Workfront APIs

Answer : C

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.

Answer : B

Step by Step Comprehensive Detailed Explanation:

Understanding the Requirement:

The user needs to archive the last five versions of a scenario for one year.

Archiving ensures there is a record of previous versions in case rollback or review is needed.

Option Analysis:

A . Save the scenario frequently:

Incorrect. While frequent saving ensures changes are not lost, it does not provide an archival mechanism for version history.

B . Download the scenario blueprints:

Correct. Downloading blueprints of the scenario allows the user to store version snapshots externally. Blueprints include the complete design and settings of the scenario, making them ideal for archival purposes.

C . Clone the scenario anytime the design changes:

Incorrect. Cloning creates duplicates of the scenario but does not inherently manage or track version history for archival purposes.

D . Find previous versions using the History tab:

Incorrect. The History tab only shows recent edits and logs but does not provide a long-term archiving solution.

Why Downloading Blueprints is Best:

External Storage: Blueprints can be downloaded and stored securely for long-term use.

Restoration: A saved blueprint can be re-imported into Fusion to restore a scenario exactly as it was.

Implementation Steps:

Go to the scenario in Workfront Fusion.

Use the Download Blueprint option to save a copy of the scenario.

Label and organize the blueprints by version and date for easy retrieval later.

Answer : D

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.

Answer : B, C, D

Workfront's training on scenario testing emphasizes the importance of a well-structured test plan to ensure scenario reliability and accuracy. The three essential elements include:

B . Description of Expected Behavior:

This provides clarity on what the scenario is supposed to achieve when executed successfully.

It serves as a benchmark for evaluating the outcome of test executions.

C . Specific Event/Trigger per Scenario:

Identifying and testing specific triggers ensures that the scenario starts under the correct conditions.

This is crucial for verifying the proper configuration of the scenario's start point.

D . Description of Testing Steps:

Outlining step-by-step instructions for the testing process ensures that all aspects of the scenario are tested systematically.

It helps identify potential bottlenecks or areas for improvement in the scenario's configuration.

Why Not Other Options?

A . Roadmap requirements: This pertains to project planning and is not directly relevant to scenario testing.

Workfront Training Materials: Best Practices for Scenario Testing

Experience League Documentation: How to Design and Execute a Test Plan for Workfront Fusion Scenarios