AD0-E902 Adobe Workfront Fusion Developer Professional Exam Topics and Questions

This is the largest slice of the exam, and it earns that weight. Foundational technical concepts covers the building blocks you touch in every scenario you will ever build: data transformation, routing, flow control, error visibility, and the settings that govern how a scenario actually runs. If your mental model of any one of these is slightly off, the exam will find it. The questions are situational, so knowing the theory without being able to apply it to a specific scenario setup will not be enough.

– Data transformation and mapping

The exam will give you a field in one format and ask which function, or combination of functions, gets it into the format a downstream module expects. You need to know not just that a function exists, but what it produces and when it breaks. Nesting functions is a separate skill: the question will show you several expressions and you have to spot which one is syntactically correct and logically sound. The Mapping Panel is where all of this lives, and the exam treats selecting the right expression as a distinct task from selecting the right module. Timezone handling sits in this space too. The exam distinguishes between the timezone set on the user profile, the timezone visible at the organization level, and the scenarios where you must override the timezone at the module level. Those three layers are testable independently, and conflating them is a common source of wrong answers.

– Routing, flow control, and set-get patterns

Routing questions present a scenario with multiple paths and ask you to choose the right flow control module or the right combination of them. The trap is assuming that any module that looks like a router will do the job: the exam cares about which specific module fits the described behavior. The set-get pattern is tested in its own right. When data produced in one route is needed in a separate route, you cannot just map it across. The exam expects you to know how to use the set variable and get variable modules to make that data available without re-fetching it. Questions in this area describe a scenario and ask you to provide the solution, so you need to be able to reason through the data flow, not just recognize the module names.

– Workfront modules, scenario settings, and templates

Selecting the right Workfront module or action for a described need is a recurring item type. The exam does not just ask you to name modules; it places you in a scenario and asks which module, or which combination, achieves the stated outcome. Scenario settings are tested as a distinct area: the options that control scheduling, sequential processing, data loss behavior, and similar controls are all fair game. Templates are covered from both directions: knowing when to use an existing template for a business need and knowing how to produce one. Teams and access control round out this group. The exam expects you to know how teams are used to restrict or share access to connections and other Fusion features, which is a governance question as much as a technical one.

– Troubleshooting, executions, and the Dev Tool

The Fusion Dev Tool is explicitly on the syllabus, and the exam tests it in a specific way: given a troubleshooting situation, you need to identify the correct use of the tool to diagnose an error or to inspect calls and responses to third-party systems. Knowing the tool exists is not enough; you need to know which part of it to use and what it will tell you. Viewing and resolving incomplete executions is a related but separate skill. The exam will describe an execution state and ask what action is appropriate. Identifying system and feature limitations is also tested here: some questions describe a scenario and ask you to spot what cannot work, which requires knowing the boundaries of what Fusion can do rather than what it can.

How Foundational technical concepts is tested

At 39% of the exam, this topic will appear in roughly two out of every five items you see. Most of them are scenario-based: you are given a description of a Fusion setup and asked to select a module, an expression, a setting, or a troubleshooting action. The demand is applied knowledge, not recall. Items in the data transformation area reward candidates who can trace what a function does to a specific value, not just name the function category. Nesting questions reward the ability to read an expression and evaluate whether it is correctly formed. Flow control items reward knowing why one module fits and another does not, given the described routing behavior. The most common place candidates lose marks is in questions that offer two plausible-looking options: one that names the right concept but applies it incorrectly, and one that is correct. Reading the scenario details carefully, rather than pattern-matching to a familiar term, is what separates a right answer from a near-miss here.

After grounding yourself in the building blocks, the next challenge is knowing how to assemble them well. Scenario design and architecture is about decision-making at the structural level: how you look up data, how you handle bundles as they move through aggregators, how you document what you build, and how you recover when things go wrong at the system level. The questions here reward candidates who think about maintainability and efficiency, not just whether a scenario runs.

– Data lookup, JSON parsing, and bundle flow

The exam tests JSON parsing as a sequenced process: given a list of steps, you choose the correct order. Getting one step out of sequence is enough to make the whole thing wrong, so the order matters as much as knowing the steps exist. Data lookup questions ask you to match a business requirement to the correct lookup method, which means knowing the difference between what a search module returns and what a direct lookup returns. Bundle flow through aggregators is tested with numbers: the exam will describe how many bundles a search module produces and ask you to explain what the aggregator does to that count and what the bundle inspector will display. This is an area where candidates who have only read about aggregators, rather than observed them, tend to lose marks.

– Triggers, scheduling, and scenario optimization

The difference between instant and scheduled triggers is a specific, testable distinction. The exam expects you to know not just that both exist, but what each one does to the execution timing and how that affects the scenario's behavior in practice. Optimization questions present a working scenario and ask you to identify what could be simplified or restructured for easier maintenance. These items reward knowing what good design looks like, not just what functional design looks like. Reducing data flow is a related angle: the exam will describe a scenario and ask where an opportunity exists to process fewer operations or pass less data between modules. Both of these question types require you to evaluate a design critically rather than confirm that it works.

– Documentation, archiving, and error origins

Fusion best practices for documenting scenarios are explicitly tested. The exam expects you to know the accepted approaches, which means knowing what information belongs in scenario documentation and where it lives. Archiving is tested with a constraint: when a scenario needs to be preserved for longer than the standard execution history window, there is one correct method, and the exam will ask you to identify it. Error origin questions are scenario-specific: given a 403 Forbidden response, you need to correctly identify where the error is coming from and what is causing it. Tracking that Fusion processed a record, as opposed to a user, and capturing when that happened, is a business requirement the exam translates into a technical question about which approach is correct.

How Scenario design and architecture is tested

At 35%, this topic sits just behind Foundational technical concepts in volume. Items here tend to be evaluative: you are not asked to recall a fact in isolation, but to assess a design or a situation and choose the best response. The bundle inspector questions are a good example. They describe a specific scenario state and ask you to reason through what the numbers mean, which rewards candidates who understand the underlying bundle model rather than those who have memorized definitions. Optimization and simplification items are traps for candidates who look for the option that adds something rather than the one that removes it. The archiving question is a known single-answer item: there is one way to preserve a scenario blueprint beyond the standard window, and any other option is wrong. Error origin questions reward reading the error type carefully before jumping to a cause. Candidates lose marks here by attributing a 403 to the wrong layer of the system, which is a fast mistake to make under time pressure.

Testing and error handling shifts the focus from building scenarios to verifying and protecting them. The domain covers what a proper test plan and test case look like, how to add custom error handling inside a scenario, and how to manage the incomplete executions that result when something goes wrong at runtime. At 16%, this topic is smaller than the first two, but the items in it are precise: they reward knowing the specific elements and directives Fusion provides, not general quality assurance knowledge.

How Testing and error handling is tested

Items in this topic split between knowledge questions and applied scenario questions. The test plan and test case questions ask you to identify what belongs in each, which means knowing the specific elements the Fusion context defines, not a generic QA framework. Directive questions present a scenario involving an unreliable service and ask you to select the appropriate error handling directive: the exam distinguishes between the available directives, so knowing that error handling exists is not enough. Custom error handling questions ask about the process for adding it, which is a procedural question with a correct sequence. Incomplete executions are tested from the resolution side: the exam describes a state and asks how to track, read, or resolve it. Missing required data questions present a scenario and ask which approaches are valid for handling the invalid input. Candidates lose marks here by selecting an option that sounds reasonable but does not match the mechanism Fusion actually provides. Precision about which tool does which job is what these items reward.

The final topic is the narrowest by weight, but it is not easy to bluff. Working with APIs covers what you do when Fusion's built-in modules run out: rate limit errors from third-party services, new Workfront functionality not yet surfaced in the native module, and systems with no dedicated app at all. The items here expect you to know the HTTP app and the Workfront API reference well enough to choose the right module and the right approach for each situation.

How Working with APIs is tested

With four sub-topics and a 10% weight, this topic contributes a small but focused set of items. Each sub-topic maps to a recognizable question type. The 429 Too Many Requests question asks you to identify a solution, which means knowing what Fusion provides to handle rate limiting rather than describing the HTTP status code. The new Workfront functionality question asks you to identify both the correct reference and the correct module type, so you need to know where to find the API documentation and which module consumes it. The HTTP app question presents a third-party system with no dedicated app and asks you to select the right module from within that app, which requires knowing the module options and what each one is for. The CRUD question asks you to distinguish those four operations from other REST API capabilities, which is a conceptual boundary question. Candidates lose marks here by confusing the HTTP module options or by selecting the Workfront module when the scenario calls for the HTTP module, and vice versa.