ACP-120

Proctored, computer-based delivery with multiple-choice and multiple-response questions. Some items ask you to pick more than one correct option. Atlassian publishes the current delivery details, including remote versus test-centre proctoring, on its certification site - confirm there before you schedule, since logistics change.

The certification body publishes the current question count and time limit, and they are subject to change. Do not plan around numbers quoted in forums or older prep material. Check Atlassian's official certification page when you book so your pacing strategy reflects the real exam.

Fees and the scaled passing score are set by Atlassian and published on its certification site. They vary by region and currency and are revised periodically, so any figure you read secondhand may be stale. Treat the official page as the only reliable source.

It is a professional-level exam, not an entry ticket. Candidates who pass typically have real administrative responsibility for a Cloud site - owning schemes, user management, and workflows - rather than only using Jira as a project member. Expect scenario reasoning across several configuration layers at once, not single-fact recall.

Retakes are permitted under Atlassian's policy, which sets the waiting period and any repeat-attempt limits. The exact terms are published by the certification body rather than fixed here. Read them before your first attempt so an unexpected result does not catch you without a plan.

Start with the scheme model itself - how project, issue, workflow, permission, and notification schemes attach to projects - because nearly every other objective depends on it. Then go deep on permission schemes and issue-level security, which carry the heaviest weight, followed by workflows, fields and screens, project types, and automation.

Assume not unless the official exam guide states otherwise. Treat every multiple-response item as all-or-nothing: read each option independently, eliminate the ones that are true in general but wrong for the stated scenario, and only then commit. Guessing a third option on a two-answer item usually costs you the point.

Memorising menu paths instead of understanding inheritance and precedence. Confusing project roles with groups, or global permissions with scheme permissions. Forgetting that scheme changes can silently affect other projects sharing it. And skipping automation, where smart values and rule component order are routinely underestimated.

Enough to design rules confidently: triggers, conditions, actions, branches, smart values, and the difference between project-scoped and global rules. You should be able to read a rule description and predict whether it fires, in what order, and which actor's permissions it uses - that last point trips up many candidates.

No. The credential is Cloud-focused, and several familiar Data Center features work differently or are handled by separate Cloud products. Study Cloud documentation and a live Cloud sandbox. Where documentation offers a Cloud/Data Center toggle, keep it on Cloud throughout your preparation.