AD0-E911 Adobe Workfront Project Manager Certified Professional Exam Topics and Questions

Intake and planning carries the largest share of the exam, and it tests something many Workfront users underestimate: the decisions made before a project starts. This topic asks you to judge situations, not recall menus. You will be placed in scenarios where the wrong sharing permission, the wrong task setting, or a missed risk flag costs the project before a single task is underway. Know the decision logic, not just the feature names.

– Receiving, reading, and routing work requests

Workfront surfaces incoming work through multiple channels: request queues, email notifications, in-app notifications, and the Notifications panel. The exam expects you to match the channel to the context, not just list them. When a request arrives, the next judgment call is the custom data attached to it. Custom forms on requests carry the information a project manager needs to decide whether to convert the request, reject it, or ask for more detail. Knowing which fields matter for which decision is what the scenario questions test. Sharing permissions tie directly into this: a requestor, a reviewer, and a project manager each need a different access level, and granting too much or too little has consequences the exam will make you trace through.

– Task settings and timeline control

Planning a task to land in a specific window requires more than setting a start date. Task constraints, duration types, and planned versus projected dates all interact, and the exam will give you a scenario where the wrong combination pushes a deadline. The question is always about consequence: if you set this constraint in this situation, what happens to the timeline? Alongside individual task settings, you need to know how to locate key data on a project quickly. Workfront organises information across project details, updates, documents, and custom fields, and finding the right data point in the right place is a practical skill the exam probes through scenario questions.

– Risk tracking, object hierarchy, and resources

Workfront has a dedicated mechanism for logging and monitoring project risks, and the exam expects you to know where it lives and what it tracks, not just that it exists. Object hierarchy matters here too: portfolios sit above programs, programs above projects, projects above tasks, and tasks above issues. That chain determines where data rolls up and where permissions inherit. Getting the hierarchy wrong in a scenario question produces the wrong answer about where to look or what action to take. Resource visibility is the final thread: identifying which field displays a specific assigned resource is a precision question. Workfront surfaces resource assignments in several places, including the Workload Balancer, task details, and project team views, and the exam distinguishes between them.

– Reports and dashboards for intake personas

The exam pairs personas with the tools they actually use. During intake and planning, a project manager, a portfolio manager, and a resource manager each rely on different reports and dashboards. You are not expected to build complex reports from scratch in these questions, but you are expected to identify which report type or dashboard view answers a specific business question for a specific role. Built-in report types such as project, task, issue, and utilisation reports each surface different data, and knowing which one a planning-stage persona would reach for is the practical skill being measured.

How Intake and planning is tested

At 40% of the exam, this topic will appear in roughly two out of every five questions you face. The items are almost entirely scenario-based: you are given a situation involving a request, a user role, a timeline constraint, or a reporting need, and you must select the action or setting that fits. The trap in most of these questions is surface familiarity. Candidates who have used Workfront day-to-day often pick the option that feels right rather than the one that is technically correct for the described scenario. Task constraint questions are a common loss point because the wrong constraint looks reasonable until you think through what it does to dependent tasks. Sharing permission questions catch candidates who conflate view access with contribute access, or who forget that permissions on a project do not automatically extend to its documents. Items in this topic reward precise knowledge of where Workfront stores specific data and what each setting controls downstream. Spending time on the decision logic behind each feature, rather than the feature itself, is where preparation pays off.

If Intake and planning tests your setup decisions, Execute tests everything that happens once the project is live. At half the exam, this topic is where most marks are won or lost. It spans a wider range of Workfront features than any other topic, from Gantt charts and Workload Balancer to proofing, financial data, and custom dashboards. The breadth is deliberate: execution is where a project manager touches the most tools, and the exam reflects that reality.

– Milestones, approvals, and date types

Milestones in Workfront are more than markers on a timeline. The exam tests whether you can read milestone data to assess progress and communicate status, not just attach a milestone to a task. Approval tracking is a related skill: given a project, task, or issue, you need to identify whether an approval process is currently active and what that means for the work item's status. Date types are where many candidates lose marks. Workfront uses planned, projected, and actual dates, and each tells a different story. Planned dates reflect the schedule; projected dates are Workfront's forward-looking estimate based on current progress; actual dates record what happened. Confusing projected with planned in a scenario question leads to the wrong diagnosis of a schedule problem.

– Task constraints, Gantt charts, and Workload Balancer

Task constraints return in the Execute topic, but now in the context of a live project where changes ripple. The exam presents scenarios where a constraint is applied or changed mid-project and asks you to trace the effect on the timeline. Gantt chart questions ask you to read object relationships: which tasks are predecessors, which are children, and how the chart communicates lag or overlap. These are reading questions as much as knowledge questions. Workload Balancer questions focus on assignment decisions: given a resource situation, determine how to redistribute work so that no one is over-allocated. The exam expects you to know what the Balancer shows and what actions it enables, not just that it exists.

– Teams, communication, and documents

Workfront distinguishes between Workfront teams and Workfront groups, and the exam tests that distinction with precision. Teams are used for work assignment and routing; groups are organisational units tied to administration and access. Knowing which one applies in a given scenario is a one-mark question you do not want to drop. Communication questions ask how a project manager notifies team members of assignments, updates, or completed work, and Workfront provides several mechanisms: updates, notifications, and tagging. Document and proofing questions require you to know the steps for uploading a document and initiating a proof workflow. The exam does not test deep proofing configuration, but it does expect you to understand the sequence and what each step produces.

– Financials, framework methodologies, Condition versus Progress Status, and dashboards

Financial data in Workfront sits in specific locations: project finances, task costs, and billing records are not the same thing, and the exam will ask you to locate a particular financial element in a scenario. Framework methodology questions cover the methodologies Workfront supports natively, including waterfall and Agile-style boards, and what each one enables for a project manager. Condition and Progress Status are a frequent trap: Condition is a manually set field reflecting the project manager's assessment; Progress Status is calculated by Workfront based on dates and completion. Swapping them in a scenario produces a wrong answer. Dashboard and reporting questions at this stage involve execution personas and ask you to identify which report or dashboard serves a specific need, as well as the steps to build a custom one.

How Execute is tested

Half the exam comes from this topic, which means the range of item types is wider here than anywhere else. Some items ask you to identify: which financial field, which team type, which date. Others ask you to apply judgment: given this resource situation, how do you use the Workload Balancer? Given this Gantt chart, what does the relationship between these two objects mean for the schedule? The Condition versus Progress Status distinction appears more often than candidates expect, and items reward knowing that one is system-calculated while the other is a manager's manual input. Milestone questions reward knowing what milestone data communicates to stakeholders, not just where to set it. The dashboard and reporting items are the most open-ended: they describe a persona's need and ask what report or dashboard configuration satisfies it. Candidates who have only used pre-built reports struggle here. The items reward understanding the logic behind report filters and groupings, not memorising a list of standard reports.

After the breadth of Execute, Closeout is narrow by design. At 10% of the exam it will not make or break your score on its own, but the questions it produces are precise and unforgiving. This topic asks you to think about endings: what a status change triggers, what gets locked, and how you determine whether a project actually succeeded. Candidates who treat this as a light topic and skim it often drop marks they could have kept with an hour of focused preparation.

How Closeout is tested

Closeout items tend to be short and direct, which makes them feel easier than they are. One line of questions turns on object status: when a project is set to Complete, or a task is marked as such, specific actions are triggered and others are blocked. Items reward knowing what those triggers are and in which direction they flow. A candidate who knows that closing a project locks certain financial data, for example, will handle these items confidently; one who treats status as a label rather than a functional state will not. The second line of questions asks you to identify which project elements serve as success measures. Workfront surfaces several: planned versus actual hours, budget versus actual cost, task completion rates, and milestone achievement. Items reward selecting the element that answers the specific success question in the scenario, not listing every available metric. Because this topic has only two areas, each one carries significant weight within the topic's share of the exam. Missing both lines of questioning costs the full 10%.