ACP-620

Atlassian publishes the exam as multiple choice and multiple response questions delivered electronically, typically at a proctored test center or through online proctoring. Atlassian's certification site lists the current delivery options, appointment rules, and any identification requirements, so check there before scheduling rather than relying on secondhand descriptions.

It is a professional-level exam aimed at administrators with real configuration experience. Straightforward definition questions exist, but the harder items describe a symptom and ask you to identify the scheme or setting responsible. Candidates who have only used Jira as a project member usually find the scheme-inheritance and permission questions the most demanding.

Retake rules, waiting periods, and any associated fees are set by Atlassian and can change. Look up the current retake policy on Atlassian's official certification page before you book, and factor a possible second attempt into your scheduling and budget so a single result does not derail your plans.

There is no official study-hour figure. Most successful candidates already administer Jira at work and spend several weeks filling gaps in the domains they touch least, such as data import, automation rules, or permission scheme precedence. Track your weak domains against the published weightings and spend time proportionally rather than rereading material you already know.

Start with global administration and project configuration, because everything else depends on those concepts. Then work through issue types, fields, screens, and workflows, which form the configuration core. Finish with permission schemes, automation, data management, and integration. That order mirrors how configuration is actually built, so each topic reinforces the previous one.

Permissions are resolved through a scheme attached to a project, granted to users, groups, roles, or the reporter, and project roles are themselves populated per project. Candidates who memorize individual permission names but not that inheritance chain misjudge who can actually do something. Practicing with test users in a sandbox fixes this faster than reading.

Recognizing where a setting lives helps, but scenario questions usually test consequences rather than navigation. Knowing that a field must be on the screen, present in the field configuration, and editable in the workflow is more valuable than recalling which submenu opens the screen scheme, because that chain explains most real configuration failures.

Three recur. First, confusing team-managed and company-managed behavior. Second, forgetting that a workflow change does not affect existing issues until a transition occurs. Third, assuming a shared scheme change is isolated to one project. Candidates who have deliberately broken and repaired a sandbox instance tend to recognize these traps quickly.

No. This is independent study content produced by a third party and is not affiliated with, endorsed by, or sponsored by Atlassian. Use it alongside Atlassian's official documentation and certification pages, which remain the authoritative source for product behavior, exam logistics, and any policy details described here.