Free Adobe AD0-E902 Practice Exams - Page 2 of 3

Question #11

Which two actions are best practices for making a Fusion scenario easier to read, share and understand? (Choose two.)

A . Naming all modules by providing short but relevant labels.
B . Insert Note Modules at the beginning of the scenario.
C . Add notes where applicable to clarify what is happening.
D . Attach the requirements document using the scenario settings.

Reveal Solution Hide Solution

Question #12

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

A . Expected outcome of test
B . Name of test owner
C . Clear procedure for completing the test
D . Source code being tested

Reveal Solution Hide Solution

Question #13

Given this Fusion scenario, a user needs to access multiple fields from the Workfront module for mapped expressions in the HTTP PUT requests.

Which action should the user take?

A . Set Multiple Variables module after the Workfront module. Get Multiple Variables between the Text Parser and the bottom Router.
B . Set Multiple Variables module after the Workfront module. Get Variable modules just before each HTTP module for the specific variables needed in each bottom path.
C . Set Variable module after the Workfront module. Get Variable modules just before each HTTP module in the bottom paths.

Reveal Solution Hide Solution

Correct Answer: A
A

Explanation:

Understanding the Scenario:

The image represents a Workfront Fusion scenario with a Workfront module, HTTP modules, and routers splitting the execution path.

The goal is to reuse multiple fields from the Workfront module (e.g., data extracted or processed earlier in the flow) as mapped expressions in HTTP PUT requests located in the bottom paths.

Why Option A is Correct:

Set Multiple Variables Module: This module allows you to define and store multiple variables at a single point in the scenario (e.g., after the Workfront module). These variables can then be reused throughout subsequent steps in the scenario.

Get Multiple Variables Module: By placing this module between the Text Parser and the bottom Router, you can retrieve all previously stored variables, ensuring consistent access across all branches of the flow. This avoids redundancy and ensures the data is easily accessible for each HTTP request in

the bottom paths.

Why the Other Options are Incorrect:

Option B ("Set Multiple Variables after Workfront, Get Variables before each HTTP module"): This is partially correct but less efficient. Adding multiple Get Variable modules before each HTTP request results in repetitive configuration and increases maintenance complexity.

Option C ("Set Variable and Get Variable for each HTTP module"): Using individual Set and Get Variable modules increases duplication. This approach requires separate variables for each data point, which is inefficient compared to using the Set/Get Multiple Variables module for multiple fields at once.

Steps to Configure the Solution:

After the Workfront module:

Add a Set Multiple Variables module.

Define all the fields required for the HTTP PUT requests as variables, mapping them from the Workfront module outputs.

Between the Text Parser and the bottom Router:

Add a Get Multiple Variables module.

Retrieve the previously stored variables, ensuring they are accessible for all paths.

In the HTTP modules on each bottom path:

Use the retrieved variables for mapping in the PUT requests.

How This Solves the Problem:

This approach centralizes variable management, making it easier to access and modify data as needed.

It avoids redundancy, as variables are defined once and reused across all paths, reducing the risk of

errors and ensuring consistency.

Reference and Supporting Documentation:

Adobe Workfront Fusion: Variables Module Overview

Workfront Community: Efficient Use of Variables in Fusion

Question #14

A customer wants all their Salesforce Opportunities to sync with their connected projects in Workfront -approximately 20,000+ projects.

After the admin sets a Workfront Fusion scenario to run each night and perform this action, the scenario is run once to test. After 40 minutes, it unexpectedly stops running.

Why did this occur?

A . Workfront has a limit to the number of API calls it can receive and stopped the scenario from running
B . Workfront Fusion occasionally times out if trying to process over 2000 records within a 40-minute period
C . Workfront Fusion has an execution timeout and likely stopped the scenario from running
D . The Workfront API stops integration webhooks if they are hit more than 2000 times in a 10 minute period

Reveal Solution Hide Solution

Correct Answer: C
C

Explanation:

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.

Question #15

A Fusion designer needs to create a Fusion scenario that will assign a user to each task with the Copywriter job role on a project.

Which method results in the fewest number of operations?

A . Searching for all assignments in the project where the role is Copywriter and add the user to each assignment
B . Searching for Tasks in the project with the Copywriter role and assign the user to each task
C . Using the Misc Action module for the project to assign all Copywriter assignments to the user

Reveal Solution Hide Solution

Question #16

In scenario settings, which two fields can be adjusted to affect how a scenario is executed once running? (Choose two.)

A . Number of consecutive errors
B . Max number of cycles
C . Number of bundles per run
D . Number of consecutive runs

Reveal Solution Hide Solution

Question #17

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?

A . Update the Scenario settings to automatically retry failed executions.
B . Update the Module settings to automatically ignore failed executions.
C . Add an error handler to the Module and select a Break directive.
D . Add an additional route after the failing module with a repeater to retry errors.

Reveal Solution Hide Solution

Question #18

A Fusion user must archive the last five versions of a scenario for one year.

What should the user do?

A . Save the scenario frequently
B . Download the scenario blueprints
C . Clone the scenario anytime the design changes
D . Find previous versions using the History tab

Reveal Solution Hide Solution

Question #19

A query returns a partial list of possible values.

Which flow control module should be used to ensure all the possible results are queried?

A . Aggregator
B . Repeater
C . Iterator
D . Router

Reveal Solution Hide Solution

Question #20

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?

A . Reauthorize their Google connection
B . Update Google sharing permissions for the document
C . Contact Workfront Support to troubleshoot the root cause
D . Search the Google status site to determine the cause

Reveal Solution Hide Solution