2025 New AD0-E902 Dumps - Real Adobe Exam Questions [Q17-Q37]

4/5 - (1 vote)

2025 New AD0-E902 Dumps – Real Adobe Exam Questions

Dependable AD0-E902 Exam Dumps to Become Adobe Certified

Adobe AD0-E902 Exam Syllabus Topics:

Topic	Details
Topic 1	Working with APIs: This section of the exam measures the skills of Integration Specialists and assesses knowledge of API interactions within Fusion. Candidates must handle rate-limiting errors, identify ways to integrate third-party APIs and determine the correct module types when built-in functionalities are unavailable. One critical skill evaluated is implementing a solution for API rate limits to ensure seamless integration.
Topic 2	Testing and Error Handling: This section of the exam measures the skills of Quality Assurance Engineers and evaluates the principles of testing and error handling in Fusion. Candidates must define test plans and test cases, identify directives for handling unreliable services, and configure custom error handling mechanisms. One specific skill tested is applying the correct error-handling directive to manage service disruptions.
Topic 3	Foundational Technical Concepts: This section of the exam measures the skills of Fusion Developers and covers core technical concepts related to data transformation, function nesting, and expression formation in Fusion. Candidates must understand how to modify field formats, use appropriate functions, and work with data manipulation techniques. One key skill evaluated is selecting the correct function to transform data between different formats.
Topic 4	Scenario Design and Architecture: This section of the exam measures the skills of Solution Architects and focuses on designing and structuring Fusion scenarios efficiently. Candidates must determine the correct steps to parse JSON, perform data lookups, and distinguish between different triggers. Understanding system limitations, module selection, and timezone handling is also essential. One key skill assessed is identifying the appropriate method for uploading documents while managing access controls.

QUESTION 17
REST APIs commonly implement CRUD operations, including Create, Read, Update, and Delete.
Which two actions is an object ID generally required to be provided as an input? Choose two.

Update

Delete

Respond

Create

QUESTION 18
A Fusion scenario uses an HTTP module to create a new record.
Which response code indicates that the connection was successful?

GREEN

200

402

500

QUESTION 19
Which two features or modules can be used to create conditional or nested error handling when using Error Handling Directives? (Choose two.)

Text Parser

Filters

Workfront app

Routers

QUESTION 20
Which statement about the differences between instant and polling triggers is true?

To keep track of records processed, instant triggers store received webhooks in a queue, whereas polling triggers remember which records have already been processed

A user should use instant triggers when available because instant triggers allow Fusion to process bundles of data faster than polling triggers

A user must set up a webhook in Fusion to use Instant Triggers that make polling triggers easier to use and more reliable in scenarios

Only polling triggers can be set to run on a schedule and should be used to avoid shutdown of third- party systems during working hours

* Understanding Instant and Polling Triggers:
* Instant Triggers:
* Rely on webhooks to receive real-time data from a third-party system.
* The external system sends a notification (webhook) to Fusion whenever an event occurs, triggering the scenario immediately.
* Polling Triggers:
* Regularly check (poll) the third-party system for new or updated records at scheduled intervals.
* These are slower because they involve repeated API requests.
* Why Option B is Correct:
* Speed and Efficiency:
* Instant triggers process data faster because they act immediately upon receiving a webhook. Polling triggers, on the other hand, may take time depending on the polling frequency and can result in unnecessary delays.
* Reduced Load on Systems:
* Instant triggers generate fewer API calls than polling triggers, which continuously check for new records even if no changes have occurred.
* Best Practice: Use instant triggers whenever supported by the third-party system to ensure faster and more efficient scenario execution.
* Why the Other Options are Incorrect:
* Option A (“Instant triggers store received webhooks in a queue”):
* Webhooks do not store data in a queue; they simply notify Fusion of events in real-time.
Polling triggers also do not store records but remember the last processed record.
* Option C (“A user must set up a webhook in Fusion”):
* Instant triggers require setting up webhooks in the external system, not in Fusion. Fusion provides the webhook endpoint, but the user must configure the source system to send data.
* Option D (“Only polling triggers can be set to run on a schedule”):
* This is incorrect because instant triggers do not rely on schedules; they operate in real-time.
Polling triggers, however, run on schedules and are used when instant triggers are unavailable.
References and Supporting Documentation:
* Adobe Workfront Fusion Triggers Documentation
* Workfront Community: Differences Between Instant and Polling Triggers Instant triggers are the preferred option when available, as they provide real-time data processing with greater speed and efficiency than polling triggers.

QUESTION 21
A solution requested for a use case requires that the scenario is initiated with project updates.
Which Workfront app module will start the scenario immediately?

Watch Events

Watch Record

Watch Field

* Understanding the Question:
* The scenario must begin as soon as a project update occurs in Adobe Workfront.
* The correct Workfront module should continuously monitor for specific changes (in this case, project updates) and trigger the scenario immediately.
* Why Option A (“Watch Events”) is Correct:
* Watch Events Module: This module in Adobe Workfront Fusion is specifically designed to monitor events, such as updates to projects, tasks, or issues, and trigger scenarios as soon as those events occur.
* Real-Time Triggering: The “Watch Events” module listens to the Workfront event stream and ensures the scenario starts immediately upon detecting relevant updates.
* Example Use Case: Monitoring updates to a project’s status, such as changes in “Completion” or
“Progress,” to trigger notifications or integrations with other systems.
* Why the Other Options are Incorrect:
* Option B (“Watch Record”): This module monitors specific Workfront records (e.g., projects, tasks, issues) for new additions or modifications, but it does not initiate scenarios immediately when updates occur. It works better for periodic checks rather than real-time events.
* Option C (“Watch Field”): This module monitors changes to specific fields within a Workfront object, but it is not designed for broader event monitoring like project updates. It is more suited for field-specific tracking.
* Option D (“Search”): This module performs queries to find specific data in Workfront (e.g., searching for projects based on criteria), but it is not an event-driven module and does not automatically trigger scenarios.
* Steps to Configure the Watch Events Module in Workfront Fusion:
* In the Fusion scenario editor, add theWatch Eventsmodule as the first step in your scenario.
* Configure the module:
* Select Workfront Connection: Choose the authorized Workfront account.
* Event Object: Specify the object type (e.g., Project, Task, Issue) to monitor.
* Event Type: Select the type of event to watch, such as “Update” or “Change.”
* Save and activate the scenario.
* How This Solves the Problem:
* Using the Watch Events module ensures the scenario is event-driven and starts automatically when the desired project update occurs. This approach is both efficient and timely, meeting the requirement for immediate initiation.
References and Supporting Documentation:
* Adobe Workfront Fusion Official Documentation: Watch Events Module
* Workfront Community Forum: Use Cases for Watch Events

QUESTION 22
A Fusion Developer receives frequent notifications that a specific Scenario has been stopped. Upon investigation, the developer notes that there is nothing wrong with the data or process in the scenario, but that the error always occurs on a specific module that calls a third-party system. The error recorded is consistently a service unavailable error, particularly during times of high network traffic to the target system.
Which action should the Fusion Developer take to reduce the number of times the scenario is automatically stopped by Fusion?

Update the Scenario settings to automatically retry failed executions.

Update the Module settings to automatically ignore failed executions.

Add an error handler to the Module and select a Break directive.

Add an additional route after the failing module with a repeater to retry errors.

QUESTION 23
A Fusion scenario updates project conditions each night, and should set the project condition to At Risk if there are any high priority open issues on the project. The scenario retrieves all open projects and cycles through the projects. For each project with issues, it retrieves all associated open issues, iterates through them and sets the project condition to At Risk if the issue is high priority or On Target if it is not.
A user notices that Fusion is updating the progress condition multiple times, once for each issue in the project.
How can the developer ensure the project is updated only once?

Change the issue search module to result set of First Matching

Record Add an Ignore error directive as an error handler route for the update module

Create a separate scenario to update the overall project condition

Apply the Run Once flow control function

QUESTION 24
What are two required elements of a test case? (Choose two.)

Expected outcome of test

Name of test owner

Clear procedure for completing the test

Source code being tested

QUESTION 25
A user needs to dynamically create custom form field options in two customer environments.

Given this image, which type of Workfront module is referenced in the formula with the parameterlD value?

Custom API Call

Misc Action

Read Related Records

QUESTION 26
Which action makes it possible to see the exact API request and the response a module executes?

Using the Bundle Inspector

Using the execution history

Using the Fusion DevTool scenario debugger

Using the Fusion DevTool error evaluator

QUESTION 27
In a scenario that searches for recently completed tasks, a user notices the following input and output for a date transformation.
Input: March 3, 2021 10:34 AM Output: March 1, 2021 10:34 AM
Which expression produces this date transformation?

subDays(now,2)

addHours(now; -48)

addDays(today; -4)

QUESTION 28

In a scenario, there are two aggregators displaying different numbers in the bundle inspector: Aggregator 1 displays a 1, and Aggregator 2 displays a 10. What is a possible reason for this difference?

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

The source module for the aggregators are different

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

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

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.

QUESTION 29
A CSV export from another system provides columns of information about Purchase Orders. The graphic below includes information from each column and an example of data from one row:
The customer wants this information in the title of their Workfront projects in the following order:
1.PO#
2. Name
3. PO Fulfillment Date
4. If a discount was given, include the Discount% and the Approver’s Last Name.
Ex. 2837 – Compendium-Premium Running Shoes – 21 /02/16 -15% Discount – UserLast Which expression below represents the project name that the customer wants?

QUESTION 30
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?

formatDate(now;YY) – referenceNumber – name

join(formatDate(now;YY) – referenceNumber – name)

concat(formatDate(now;YY) – referenceNumber – name)

QUESTION 31
To meet compliance standards, a user must include a process that tracks every Workfront project update created by Fusion.
What can they do to address this business requirement?

Use reporting on the Last Updated by ID and Last Update Date

Update the External Reference ID with User ID and Timestamp

Create a Note record related to the record updated

QUESTION 32
A Fusion designer is unhappy with the high number of bundles passing through an instant Watch Events module that monitors Workfront project updates.
Which action reduces the number of bundles passing through the module?

Reducing the maximum number of returned events on the trigger

Reducing the maximum number of cycles in scenario setting

Changing the module type to Watch Record and applying criteria in the optional filter box

QUESTION 33
A Fusion user must archive the last five versions of a scenario for one year.
What should the user do?

Save the scenario frequently

Download the scenario blueprints

Clone the scenario anytime the design changes

Find previous versions using the History tab

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

Aggregator

Repeater

Iterator

Router

QUESTION 35
A Fusion scenario is triggered by a project status update. The scenario then updates the status, causing repeated execution of the scenario.
Which action should a user take to keep this from happening?

Schedule the instant trigger to only run at intervals to prevent Fusion from thinking the record has been updated after each run

When using instant triggers, finish the scenario with the Break directive to prevent the record from being updated again

Create a filter after the instant trigger that only passes records that have not been updated by Fusion

QUESTION 36
A Fusion user is trying to get a Google Slide presentation to connect to projects in Workfront. Each time the user runs the scenario, this error message appears:

What action should the user take to resolve the error message?

Reauthorize their Google connection

Update Google sharing permissions for the document

Contact Workfront Support to troubleshoot the root cause

Search the Google status site to determine the cause

Step by Step Comprehensive Detailed Explanation:
* Understanding the Error:
* The error message [403] The caller does not have permission is aGoogle 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 apermission 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 leastEditoror 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.
References: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.

QUESTION 37
A global customer has end users who input date and currency data into fields in inconsistent formats. Despite continued training efforts, this continues to be an issue. Unfortunately, the third-party service that the end users are using does not support forcing a required field format. These input mistakes do not happen frequently, but they currently stop the scenario from executing after the default three retries.
In Fusion, which action can the admin take to ensure that errors are corrected after they occur in a scenario?

Select storing of Incomplete Executions in the scenario settings. The customer admin can then filter and search the execution history to resolve errors as they occur.

Use the switch module to catch dates not in the required format and convert the common misused patterns into the appropriate format to prevent the scenario from stopping after three failed executions.

Set up an error handling path that will catch errors in the end user’s inputs and message the users in an email update that they need to try again.

* Understanding the Scenario:
* The issue involves end users inputting inconsistent date and currency formats that result in errors in a Workfront Fusion scenario.
* The default behavior of Fusion stops the scenario after three retries due to input mismatches or invalid formats.
* Why Option A is Correct:
* Storing Incomplete Executions: In Adobe Workfront Fusion, enabling “Store incomplete executions” in the scenario settings allows administrators to capture incomplete runs without fully stopping the entire process. This feature stores all relevant data, even from incomplete runs, allowing administrators to identify and correct input issues manually.
* Error Troubleshooting: By reviewing incomplete executions, admins can pinpoint where the scenario failed, resolve the issue, and potentially reprocess those incomplete records, preventing complete scenario stoppage.
* Why Option B is Incorrect:
* The “switch module” can handle specific input variations, but it is not a comprehensive solution for handling unexpected or inconsistent formats entered by end users. While it might mitigate some errors, it does not address the root cause and can miss unanticipated input patterns.
* Why Option C is Incorrect:
* Setting up an error handling path to notify users and request corrections adds an additional manual step for users but does not resolve the problem efficiently within Fusion. Moreover, this solution does not prevent the scenario from halting after retries.
* Steps to Enable Storing Incomplete Executions:
* Navigate to the scenario in Adobe Workfront Fusion.
* Open theScenario Settingsby clicking the gear icon.
* Enable the optionStore Incomplete Executionsunder Execution settings.
* Save the settings and activate the scenario.
* How This Solves the Problem:
* Enabling this setting ensures that no data is lost when the scenario fails due to inconsistent inputs.
Admins can access the incomplete executions through the scenario execution history, apply necessary corrections, and retry specific records or steps as needed.
References and Supporting Documentation:
* Adobe Workfront Fusion Official Documentation: Scenario Settings
* Workfront Community: Handling Incomplete Executions