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?
Correct 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. References: * Adobe Workfront Fusion Documentation: Scenario Settings and Error Handling * Experience League Community: Handling API Rate Limits and Errors in Workfront Fusion
Question 17
A Fusion user must archive the last five versions of a scenario for one year. What should the user do?
Correct 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. * Version Control: Allows the user to manually manage and organize multiple scenario versions over time. * Implementation Steps: * Go to the scenario in Workfront Fusion. * Use theDownload Blueprintoption to save a copy of the scenario. * Label and organize the blueprints by version and date for easy retrieval later.
Question 18
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?
