Important Adobe AD0-E902 Exam Questions

Answer: C, C

Explanation:

Step by Step Comprehensive Detailed Explanation:

Scenario Context:

The goal is to assign a user to all tasks on a project where the role is Copywriter.

The chosen method should minimize the number of operations to ensure efficiency.

Option Analysis:

A . Searching for all assignments in the project where the role is Copywriter and add the user to each assignment:

This approach involves searching assignments, iterating through them, and adding the user individually. Each iteration generates multiple operations, making it less efficient.

B . Searching for Tasks in the project with the Copywriter role and assign the user to each task:

Similar to Option A, this approach also requires iterating through tasks and assigning users one by one, resulting in a higher number of operations.

Answer: A, C

Explanation:

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.

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

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

Answer: B

Explanation:

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

Explanation:

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 the Scenario Settings by clicking the gear icon.

Enable the option Store Incomplete Executions under 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.

Reference and Supporting Documentation:

Adobe Workfront Fusion Official Documentation: Scenario Settings

Workfront Community: Handling Incomplete Executions

Answer: B

Explanation:

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