Free AD0-E902 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Step-by-Step Explanation

Purpose of the Query:

The task is to retrieve field options from a custom form field. This operation involves fetching data,

not creating or modifying it, which requires a GET method.

Correct API Structure:

The URL must follow Workfront's API structure:

ruby

Copy

https://{your-workfront-domain}/attask/api/{version}/{endpoint}

Option B follows this standard structure, where:

wfdomain.workfront.com is the placeholder for the Workfront instance.

/attask/api/v12.0 specifies the API version.

/PARAM/search is the endpoint to search for parameters or fields.

Why Not Other Options?

A: The use of POST is incorrect because it is meant for creating or updating resources, not retrieving

data. Additionally, the URL structure is incorrect and includes unnecessary query strings (username,

password) not relevant for this operation.

C: While the method GET is correct, the URL (PARAM/search) is incomplete and lacks the required

Workfront API structure, making it invalid.

Reference

Workfront API Documentation: Querying and Retrieving Custom Form Field Data

Experience League Community: Best Practices for Using GET Methods in Workfront API

Understanding the Requirement:

The user wants to upload a document into Workfront and attach it to a specific task.

This action involves creating a document in Workfront and associating it with a task as a related

record.

Why Option B is Correct:

The Upload Document module is specifically designed for uploading files into Workfront.

It includes the ability to set a related record (e.g., a task, project, or issue) to which the document

will be attached.

This ensures the document is uploaded and correctly linked to the task in a single operation.

Why the Other Options are Incorrect:

Option A ("Create Record for Document Version after Create Record for the document on the task"):

This involves multiple steps, which are unnecessary. The Upload Document module already handles

both the upload and the attachment in one action.

Option C ("Create Record of Document type while setting the related record"):

The Create Record module is not designed for file uploads. It only creates metadata records, not the

actual document.

Option D ("Miscellaneous Action to attach document to a task"):

There is no Miscellaneous Action specifically for attaching a document to a task. The Upload

Document module is the appropriate choice.

Steps to Upload a Document in Workfront Fusion:

Add the Upload Document module to the scenario.

Specify the file to upload (e.g., from a previous module like Google Drive or an HTTP request).

Set the related record to the target task by providing its ID.

Run the scenario to upload and attach the document to the task.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Upload Document Module

Workfront Community: Best Practices for Document Management in Fusion

The Upload Document module is the most efficient and accurate method for uploading and attaching

a document to a task in Workfront.

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

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

Step by Step Comprehensive Detailed Explanation:

Understanding the Error:

The error message [403] The caller does not have permission is a Google API permission error.

It typically indicates that the user or application does not have the required access rights to perform

the requested action on the Google Slide presentation.

Option Analysis:

A . Reauthorize their Google connection:

This step might be necessary if the user's credentials or token have expired, but this is not the

primary issue here since the error specifically states a permission problem.

B . Update Google sharing permissions for the document:

Correct. The error suggests that the Google Slide document has not been shared with the user or

service account being used in Fusion. Updating the sharing settings to grant proper permissions (e.g.,

"Editor" or "Viewer" access) will resolve the issue.

C . Contact Workfront Support to troubleshoot the root cause:

While Workfront Support can help with Fusion-related issues, this error originates from Google and

is unrelated to Workfront's systems.

D . Search the Google status site to determine the cause:

The Google status site is useful for identifying system-wide outages, but this is a user-specific

permission issue, not a Google platform-wide problem.

Steps to Resolve:

Open the Google Slide presentation.

Update the sharing permissions:

Grant access to the Google account or service account being used in Fusion.

Ensure the account has at least Editor or appropriate access rights.

Save the changes and rerun the Fusion scenario.

Why Updating Permissions is Best:

This action directly addresses the root cause of the error, which is inadequate access rights.

Once permissions are updated, Fusion will be able to connect to and manipulate the Google Slide

document as intended.

Reference:

The [403] The caller does not have permission error is documented in Google API troubleshooting

guides, which recommend verifying and updating document sharing settings for resolving access

issues.

Key Scenario Settings:

Adobe Workfront Fusion provides settings to control the execution of scenarios. These settings

impact how the scenario behaves when it runs, especially under conditions such as errors or long-

running processes.

Explanation of Correct Options:

Option A ("Number of consecutive errors"):

This setting determines the maximum number of consecutive errors allowed before the scenario

execution halts.

By adjusting this value, users can define how resilient the scenario is to temporary failures in

modules or external systems.

Option B ("Max number of cycles"):

This setting limits the maximum number of cycles (iterations) the scenario performs in a single run.

It prevents scenarios from running indefinitely or consuming excessive resources in cases of large

datasets.

Why the Other Options are Incorrect:

Option C ("Number of bundles per run"): This value is not adjustable in the scenario settings. Instead,

the system dynamically determines how many bundles (data packets) are processed per cycle.

Option D ("Number of consecutive runs"): Workfront Fusion does not have a setting for the number

of consecutive runs. Scenarios are executed based on schedules, triggers, or manual execution.

Steps to Adjust Scenario Settings:

Open the scenario in Adobe Workfront Fusion.

Click the gear icon in the top-right corner to access Scenario Settings.

Locate and adjust the following fields:

Number of consecutive errors: Set a value based on acceptable failure tolerance.

Max number of cycles: Specify the maximum number of iterations allowed.

Save and activate the scenario.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Scenario Settings

Workfront Community: Best Practices for Scenario Optimization

Understanding the Issue:

The Watch Events module is generating a high number of bundles because it monitors a broad range

of project updates in Workfront, resulting in an overwhelming amount of data passing through the

scenario.

The goal is to reduce the number of bundles by narrowing the scope of monitored events.

Why Option C is Correct:

Switching to Watch Record:

The Watch Record module allows users to monitor specific records (e.g., projects, tasks) with

additional filtering options in the criteria or filter box.

By applying filters, the module can focus only on relevant updates, significantly reducing the number

of bundles being processed.

Example: Filtering for specific project statuses, update types, or assigned users ensures that only

relevant changes are captured.

Why the Other Options are Incorrect:

Option A ("Reducing the maximum number of returned events on the trigger"):

This limits the number of bundles processed per cycle but does not address the root cause, which is

the broad monitoring scope of the Watch Events module.

Option B ("Reducing the maximum number of cycles in scenario settings"):

The number of cycles determines how many iterations the scenario performs in one run but does not

reduce the number of bundles entering the scenario.

Steps to Use the Watch Record Module:

Replace the Watch Events module with Watch Record.

Specify the record type to monitor (e.g., Project).

Use the optional filter box to apply criteria, such as specific project fields, statuses, or other

conditions.

Activate the scenario to test the refined data flow.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Watch Record Module

Workfront Community: Managing High Bundle Volumes in Fusion

When dealing with intermittent errors, such as "service is not reachable," the default error handling

in Adobe Workfront Fusion is often sufficient to improve execution success rates.

Default Error Handling:

Fusion automatically retries operations when transient errors, such as network or connection issues,

occur.

By leveraging this built-in functionality, the system will attempt to re-execute the failing module after

a brief delay, which is often enough for the external service to become reachable again.

Why Not Other Options?

A . Adding an error handler that will notify the system owner: While notifying the owner can be

useful for monitoring purposes, it does not directly address improving the success rate of executions.

C . Adding a Break directive to the module: Adding a Break directive will stop the execution entirely,

which is counterproductive in this case, as the service typically becomes reachable again after a short

time.

Reference:

Adobe Workfront Fusion Documentation: Default Error Handling Mechanisms

Experience League Community: Managing Intermittent API Errors in Fusion

Understanding the Requirement:

The user wants to enable resource sharing in Fusion, including connections, data stores, and keys.

Resource sharing is necessary to allow multiple scenarios or users to access shared resources

efficiently within the same Fusion environment.

Why Option B ("Create a new team") is Correct:

Teams in Fusion:

Teams are a feature in Adobe Workfront Fusion designed to group users together within an

organization.

By creating a team, you can enable shared access to resources such as API connections, data stores,

and authentication keys, streamlining collaboration and avoiding duplication.

Resource Sharing with Teams:

All members of the team can access shared resources (e.g., connections), allowing consistent and

collaborative scenario development and execution.

Example: If multiple users within a team need to use the same API connection, creating a team

allows the connection to be configured once and shared among all team members.

Why the Other Options are Incorrect:

Option A ("Create a new group"):

Groups in Fusion are used primarily for organizing scenarios or categorizing users but do not

inherently allow sharing of resources like connections or keys. Groups lack the resource-sharing

functionality of teams.

Option C ("Create a new organization"):

Organizations in Fusion represent the highest-level administrative entity. While creating an

organization allows resource sharing among all users within the organization, it is not the

recommended solution for managing resource sharing in smaller or more focused groups, such as

project teams.

Steps to Create a New Team and Share Resources:

Log in to Adobe Workfront Fusion.

Navigate to the Admin Panel or Team Management section.

Select Create a New Team and provide a name for the team.

Assign users to the team by adding their Fusion accounts.

Configure shared resources (e.g., connections, data stores, keys) to be accessible by the team.

Save the settings, and all team members will now have access to the shared resources.

How This Solves the Problem:

Creating a team ensures that all resources, such as connections, data stores, and keys, are accessible

to team members without requiring individual duplication or configuration. It simplifies

collaboration and promotes consistency across scenarios.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Teams Overview

Workfront Community: Managing Teams and Resource Sharing

Step by Step Comprehensive Detailed Explanation:

Understanding the Scenario:

In Workfront Fusion, each module in a scenario processes data and generates bundles as output.

The bundle inspector shows the number of bundles (data packets) output by a module during an

execution.

Option Analysis:

A . The number of seconds to process the module:

This is incorrect. The number in the bundle inspector does not indicate time but rather the count of

output bundles. Processing time is not displayed in this way.

B . The number of output bundles:

Correct. The number displayed in the bundle inspector represents how many bundles the module

output during the execution. In the given example, the "Tasks" module outputs 1 bundle, and the

"Project" module outputs 23 bundles.

C . The number of operations performed:

This is incorrect. The bundle inspector displays the number of output bundles, not operations. While

operations may be a result of processing bundles, they are tracked separately in Fusion reports.

D . The number of times a module has been edited:

This is incorrect. Editing history is not displayed in the bundle inspector.

Explanation of Bundle Inspector:

Each module processes input data and generates output bundles.

These numbers in the bundle inspector indicate how many bundles the module is outputting in the

current run of the scenario.

For example, if a "Search" module retrieves 23 records, the bundle inspector will show 23, meaning

the module outputs 23 bundles.

Context of the Given Image:

The "Tasks" module processes and outputs 1 bundle.

The "Project" module processes 1 input bundle (from "Tasks") and outputs 23 bundles.

Reference:

This information is consistent with Workfront Fusion documentation, which explains the bundle

inspector's function during scenario execution. The bundle inspector is used to monitor data

processing and ensure expected outputs from modules.

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.

E. Executive sponsor expectations: While valuable for overall project alignment, it is not an essential

component of a technical test plan.

Reference:

Workfront Training Materials: Best Practices for Scenario Testing

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

Scenarios

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.

Reference:

Adobe Workfront Fusion Documentation: Task Assignments Using User IDs

Experience League Community: Mapping Salesforce Data to Workfront Tasks

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.

Reference:

REST API Documentation Best Practices: CRUD Operations

Experience League: Understanding CRUD in Workfront APIs

Step by Step Comprehensive Detailed Explanation:

Scenario Summary:

The source system provides a list of users, job roles, and departments.

The destination system requires a mapping of job roles to different departments.

Updates to this mapping are infrequent, and there is a concern for more security than a spreadsheet

offers.

Option Analysis:

A . Switch: A switch function in Workfront Fusion is used to make decisions based on specific

conditions but does not maintain persistent data like mappings over time. It is not suitable for storing

mappings that require infrequent updates.

B . Spreadsheet: Spreadsheets may be simple to use but are less secure and not ideal for integrating

with Workfront Fusion workflows due to their lack of direct integration features or control over

changes.

C . Data store: A data store in Workfront Fusion is specifically designed for storing persistent data,

such as mappings or reference tables. It is secure, easy to manage, and integrates seamlessly with

workflows, making it the best choice for this use case.

D . Table aggregator: A table aggregator is used for combining or processing data within a workflow

but is not suitable for storing persistent mappings outside of a running scenario.

Why Data Store is Appropriate:

Persistence: A data store is ideal for maintaining the job role and department mappings across

scenarios.

Security: It is managed within Workfront Fusion, offering better control and access restrictions

compared to a spreadsheet.

Ease of Integration: Data stores can be directly queried or updated in Fusion workflows, allowing

seamless handling of mappings.

Scalability: While updates are infrequent, the data store can handle changes easily and scale if the

volume of mappings increases.

Implementation in Workfront Fusion:

Create a data store for job roles and departments in Workfront Fusion.

Set up fields for Job Role and Department in the data store.

Use Workfront Fusion scenarios to retrieve and update mappings from this data store based on

requirements.

Reference:

This approach aligns with the Workfront Fusion documentation on data stores, which are designed

for secure and efficient storage of persistent data used across scenarios. See Workfront Fusion

resources for data store setup and use cases for further details.

When encountering the error 429: Too many requests, which indicates the web service is being

overwhelmed by requests, the following actions can help:

A . Add a Sleep Module:

Adding a Sleep module introduces a delay between iterations, reducing the frequency of API calls.

By slowing down the rate of requests, you avoid hitting the rate limits of the web service, thus

reducing the chances of receiving a 429 error.

This approach is useful for managing high-volume iterations without overloading the external

service.

C . Add a Module to Test the Service for Errors:

Adding a module to test the service's response before making a call can help prevent the 429 error

by checking if the service is ready to handle requests.

This preemptive check allows the scenario to conditionally execute, ensuring that it doesn't

overwhelm the service and respects the API rate limits.

Why Not Other Options?

B . Use an Ignore Directive: Ignoring errors can be risky because it would cause the scenario to ignore

429 errors, possibly leading to failed API calls that are not addressed. Ignoring an error doesn’t solve

the issue of too many requests being sent to the service.

D . Use a Break Directive: The Break directive would stop the execution, which is counterproductive

when trying to resolve the issue by reducing the rate of requests. It would not address the root cause

of too many requests.

Reference:

Adobe Workfront Fusion Documentation: Handling API Rate Limiting with Sleep and Error Handling

Experience League Community: Managing Web Service Errors in High-Volume Iterations