I recently cleared ACP-120 (Jira Administration for Cloud) with 3 weeks of preparation.
This post isn’t a brag or a study dump - it’s meant to share how I aligned my thinking with how Atlassian frames Jira Cloud administration, because that’s what the exam really tests.
I already had hands-on Jira admin experience. The challenge was unlearning a few Server/DC habits and fully embracing Cloud-first decision making.
Think in Terms of Least Privilege (Very Important)
One of the biggest patterns in ACP-120 is avoiding over-permission.
Typical scenario:
Project Leads need to manage components but must not touch workflows or permission schemes.
Correct Cloud approach:
✔ Create a custom project role
✔ Map it in the permission scheme
Why this matters:
- Giving Jira Admin or Org Admin access is almost never correct
- ACP-120 consistently favors project roles + schemes
- This applies to many permission-related questions
Once I started thinking this way, a lot of “confusing” questions became straightforward.
Automation Is Powerful - but Scope Matters
Automation is frequently tested in ACP-120, but the focus is scope control, not just where rules are created.
What actually matters is:
- How the rule scope is defined
- Whether projects are explicitly excluded
- Whether conditions limit execution
This reinforces a key ACP-120 principle:
Jira Cloud prefers centralized capability with controlled execution, not hard restrictions.
Project Types Are About Governance, Not Features
ACP-120 doesn’t ask “what can this project do?”
It asks why you’d choose one over another.
Scenario:
A team wants:
- Full control over workflows and issue types
- No dependency on Jira admins
- Fast iteration
✔ Team-managed project is the correct answer.
Reason:
- No shared schemes
- Independent configuration
- Designed for autonomy
This pattern shows up repeatedly in different forms.
Permission Troubleshooting: Start Simple
Another common trap is overthinking troubleshooting questions.
Scenario:
A user can see an issue but cannot edit it.
First thing to check:
✔ Edit Issue permission
Not:
- Workflow conditions
- Field configurations
- Issue security
ACP-120 expects a logical troubleshooting order, not deep dives right away.
Issue Security ≠ Permissions
This distinction is tested more often than people expect.
Scenario:
Certain issues should only be visible to a subset of users.
Configure an Issue Security Scheme
Key takeaway:
- Permission schemes = what actions users can perform
- Issue security = who can see specific issues
Mixing these up can cost easy marks.
OTHER IMPORTANT TOPICS
- Workflow Conditions/Validators
- Status Properties
- Component Assignee
- Global Permissions
How I Structured My 3 Weeks
Week 1
- Jira Cloud fundamentals
- Admin vs Project Admin responsibilities
- Company-managed vs Team-managed projects
- Automation for Jira
Week 2
- Permission schemes & project roles
- Automation rules and rule actors
- Issue security concepts
- Global Permissions
Week 3
- Mock tests
- Reviewing why answers were wrong
- Reinforcing Cloud limitations and best practices
I focused more on clarity and consistency than long study hours.
Final Thoughts
ACP-120 doesn’t test UI navigation
It tests whether you can:
- Make good Cloud admin decisions
- Apply least privilege
- Respect Cloud limitations
- Think the way Atlassian expects admins to think
- Follow the exam syllabus ( university.atlassian.com/student/page/832603-acp-120-jira-administration-for-cloud-exam )
If you work hands-on with Jira Cloud, 3 focused weeks are enough.
Hope this helps anyone planning their ACP-120 attempt.
Happy to answer questions or discuss preparation strategies in the comments.
