Adobe Workfront Core Developer Professional

Multiple choice and multiple select, delivered as a proctored exam, with scenario items that ask which configuration or API call achieves a stated outcome. Adobe publishes the current number of questions, seat time and delivery options (test centre or online proctoring) in its official exam guide - check that page before booking, because those details change.

Moderately hard for working administrators, considerably harder for people who have only used Workfront as end users. The items reward candidates who have actually built calculated fields, debugged a report returning nothing, and read an API error response. Memorising UI paths is not enough when two settings look plausible and only one gives the required result.

Adobe sets the retake policy, any waiting period between attempts and the associated fees, and those terms can change. Rather than relying on secondhand figures, read the policy statement on Adobe's certification site before you sit the exam, and assume a cooling-off window before a second attempt can be booked.

Register through Adobe's certification programme, typically via its testing partner. Book a slot when you are mentally fresh: the exam is scenario-heavy and late-day fatigue costs marks. Confirm the current scheduling, rescheduling and cancellation windows with the test provider, since Adobe publishes those terms rather than any fixed numbers quoted here.

Start with configuration and access, because object types, layouts and sharing underpin everything else. Move to custom forms and calculated fields, then reporting and dashboards, then workflow and approvals. Leave API and integrations until last but give it real time - it carries about a fifth of the weight and is where administrators most often feel unprepared.

Three recur: confusing sharing with access levels, misreading calculated-field syntax and display types, and assuming an API filter behaves like a report filter. Another is ignoring the fields parameter or paging, so calls return partial data. Practise diagnosing a report that returns nothing - usually a filter on a field the object does not carry.

Adobe does not publish a hard prerequisite, but the exam assumes working familiarity with Workfront objects, layouts, custom forms and the API. Realistically, six months or more of hands-on configuration work, including at least one integration project, gives you the context the scenario items expect.

More than reading alone provides. Build in a sandbox or preview environment: create calculated fields, split a form into sections with display logic, build a report with a prompt and chart view, attach it to a dashboard, then script an API call that creates a project from a template. That debugging intuition is what the exam tests.

Not heavily, but you must be comfortable reading JSON, constructing URLs with filter and fields parameters, and understanding authentication such as API keys or OAuth. Most items test whether you know which endpoint and which parameter to use, not whether you can write a full application from scratch.