Adobe Workfront Fusion Developer Professional AD0-E902 Exam Questions

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 : B

Step by Step Comprehensive Detailed Explanation:

Understanding the Problem:

The scenario is triggered by a project status update.

After the scenario runs, it updates the project status again, which re-triggers the scenario, creating a loop.

The goal is to prevent the scenario from re-triggering itself.

Option Analysis:

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

Incorrect. The Break directive is not used to prevent updates; it is used to stop further iterations of a scenario. It does not address the root cause of the loop, which is the re-triggering by updated records.

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

Correct. Adding a filter ensures that only records not recently updated by Fusion are processed. This prevents Fusion from re-triggering itself on the same record.

For example, you could use a condition to check if the Last Updated By field does not equal the Fusion user or if the Last Update Date is older than a certain threshold.

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

Incorrect. Instant triggers are event-driven, and their purpose is to respond to changes immediately. Scheduling them would negate the benefit of instant triggers and does not solve the root problem.

Why Filtering Records is Best:

Targeted Control: A filter after the trigger ensures only relevant updates (e.g., those not caused by Fusion) are processed.

Prevents Loops: By excluding records updated by Fusion, the scenario avoids re-triggering itself.

Maintains Performance: Filtering prevents unnecessary processing of irrelevant records, improving efficiency.

How to Implement:

After the instant trigger module, add a filter module.

Configure the filter to check the Last Updated By field or a custom flag indicating if the update was performed by Fusion.

Example: Last Updated By Fusion User or Update Flag True.

If a custom flag is used, ensure the flag is set when Fusion updates the record.

Alternative Solutions:

Add a custom field (e.g., 'Updated by Fusion') that Fusion sets when it updates a record. This can also be used in the filter condition.

Reference: This approach aligns with Fusion best practices for preventing infinite loops caused by scenarios re-triggering themselves. Filtering ensures the scenario runs only when necessary, avoiding redundant processing and maintaining performance.

Answer : C

Step by Step Comprehensive Detailed Explanation:

Problem Summary:

The Fusion scenario updates the project condition multiple times, once for each high-priority issue.

The desired behavior is to update the project condition only once, based on the overall condition of all associated issues.

Option Analysis:

A . Change the issue search module to result set of First Matching:

This would limit the search to only the first issue. However, this does not account for all issues on the project, leading to incomplete logic for setting the project condition.

B . Add an Ignore error directive as an error handler route for the update module:

Ignoring errors does not prevent multiple updates; it only suppresses errors in the workflow.

C . Create a separate scenario to update the overall project condition:

Correct. By separating the project update logic into a different scenario, the developer can ensure the condition is updated only once after analyzing all issues. The project condition is calculated holistically, based on the state of all high-priority issues.

D . Apply the Run Once flow control function:

'Run Once' controls execution at the scenario level, not within a module's iteration. It cannot prevent multiple updates in this context.

Why Separate Scenario is Best:

Simplifies Logic: A separate scenario can be designed to run after all issues have been checked, ensuring only one update per project.

Avoids Redundancy: Prevents unnecessary API calls to update the same project multiple times.

Improves Performance: Reduces the number of operations and bundles processed in the main scenario.

Implementation:

Create a separate scenario triggered after the issue-checking scenario completes.

Use aggregate data (e.g., a data store or intermediate processing) to evaluate the overall project condition before performing a single update.

Answer : A, C

A . Expected Outcome of Test

A test case must clearly state what the expected outcome is, providing a standard against which the results can be measured.

This ensures testers can validate whether the scenario behaves as intended.

C . Clear Procedure for Completing the Test

A well-defined procedure outlines the exact steps required to execute the test, ensuring consistent and repeatable testing.

This reduces ambiguity and helps identify whether errors are due to the scenario configuration or improper test execution.

Why Not Other Options?

B . Name of Test Owner: While helpful for accountability, the name of the test owner is not a required component of the test case itself.

D . Source Code Being Tested: Fusion scenarios do not typically involve source code. Instead, the focus is on workflow execution and configuration, making this element irrelevant.

Workfront Training Materials: Test Case Design Best Practices

Adobe Workfront Fusion Documentation: Testing and Debugging Scenarios

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 : A

In this scenario, the error consistently arises due to the unavailability of a third-party service during high traffic times. This is a temporary issue and does not indicate a problem with the data or process. The recommended approach in such cases is to configure the scenario to retry failed executions:

Update Scenario Settings:

In Workfront Fusion, you can configure scenarios to automatically retry a failed execution.

This option ensures that temporary issues, like service unavailability, are retried after a delay, reducing the chances of the scenario being stopped permanently.

This is particularly useful when dealing with network traffic spikes or third-party API throttling.

Why Not Other Options?

B . Update the Module settings to automatically ignore failed executions: Ignoring failed executions would cause incomplete or incorrect data to flow through the scenario, leading to potential downstream issues.

C . Add an error handler to the Module and select a Break directive: While error handlers are useful, the Break directive stops the scenario from processing further, which is not ideal for a temporary issue.

D . Add an additional route after the failing module with a repeater: Adding a repeater increases complexity and is unnecessary when the retry option is already available in scenario settings.

Adobe Workfront Fusion Documentation: Scenario Settings and Error Handling

Experience League Community: Handling API Rate Limits and Errors in Workfront Fusion

Answer : B

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.