ACP-120 study plan

Map the Jira Cloud admin navigation paths for global settings, system settings, and application access.

Create 6 sandbox users and 3 groups, then assign application access and global permissions per group.

Configure at least two global permission entries and verify effective access by logging in as each test user.

Distinguish which settings a Cloud admin controls directly versus which are Atlassian-managed (mail, attachments, timeouts).

Create one team-managed and one company-managed project from the same template and list the scheme-level differences.

Configure project details, project lead, default assignee, and project role membership in the company-managed project.

Swap a project's issue type scheme, workflow scheme, and permission scheme, recording what changes when a scheme is shared.

Archive and restore a project to confirm the effect on issues and scheme associations.

Create two custom fields (a select list and a number field) and set required versus optional rules in the field configurations.

Build a custom screen and screen scheme, then map create, edit, and view operations for two issue types.

Assemble a field configuration scheme that hides a field on one issue type while showing it on another, then verify in the UI.

Configure field contexts so one select-list field offers different options across two projects.

Build a custom permission scheme granting Create/Edit/Transition to one project role and nothing to a second role, then verify with two test users.

Test the Anyone, Application access, and project role grantees and document the most-permissive-wins rule with evidence.

Create an issue security scheme with two levels tied to different groups or roles, then confirm visibility as a non-member.

Compare permission inheritance through project roles versus groups and state when each is the right choice.

Create a custom workflow with 5 statuses, 6 transitions, and correct status categories, then associate it through a workflow scheme.

Add a condition, a validator, and a post function (field update) to two transitions and verify each blocks or fires as intended.

Add a transition screen and a global transition, then map statuses to board columns to confirm the mapping holds.

Publish a draft workflow change and confirm existing issues follow the updated workflow.

Build 4 automation rules (auto-assign, scheduled field update, comment trigger, status-change notification) and verify each in the audit log.

Use smart values and a JQL condition inside at least one rule and confirm the branch and condition logic executes correctly.

Configure one scheduled rule and one event-driven rule, then state how trigger scope changes what the rule can act on.

Bulk-edit a set of issues and import a CSV of new issues, then verify field mapping and capture any import errors.

Configure a notification scheme and trigger events to confirm which roles receive which emails.

Adjust one user's notification preferences and compare the delivered mail against the scheme-driven default.

Document where notifications can be suppressed at the user level versus the admin level, including reply-to and own-change settings.

Re-test the weakest domain from weeks 1-6 and log every objective you still miss.

Complete two full-length timed practice exams and score each attempt by domain.

Re-run every hands-on deliverable from weeks 1-7 that is tied to a domain scored below 80%.

Recite from memory the permission hierarchy order and the rules governing shared versus dedicated workflow schemes.

Condense all prior deliverables into a single final review sheet covering traps and scheme dependencies.