ACP-420 is Atlassian's Managing Jira Service Projects for Cloud exam: 75 questions in 180 minutes, and you need 50 correct to pass. The fastest way to understand it is not to memorise the eight domains as a list, but to follow one customer request from the moment it is raised until it shows up on a dashboard.
Atlassian prices the exam at $249 plus tax, runs it proctored online, and keeps the certification valid for 24 months, according to the Managing Jira Service Projects for Cloud certification page. The scope is narrow on purpose. It covers Jira Service Management Cloud, company-managed projects only, so team-managed project quirks are not what you are being tested on.
Picture a simple case. An employee at a mid-sized company cannot get into the VPN and opens a request on the IT help center. That one ticket will touch every part of the exam before it closes.
What does the ACP-420 exam actually measure?
It measures whether you can configure a service project so that the right people reach the right request type, the work lands in the right queue, and the team can prove it met its targets. Most questions describe a team's requirement and ask which setting delivers it.
The current blueprint is version 2, dated April 2025. You can read every objective in the official ACP-420 exam topics PDF. Here are the eight domains and their approximate weights:
- Configure customer facing features: about 21%
- Configure agent facing features: about 19%
- Distinguish among users, project roles, and permissions: about 16%
- Configure the customer portal and notifications: about 12%
- Manage automation rules: about 11%
- Utilize specialized capabilities for adding context to tickets: about 9%
- Configure reporting: about 7%
- Manage the knowledge base: about 5%
The top three domains make up 56% of the exam. That matters later, when you plan your study weeks.
Stop 1: who is allowed to raise the ticket?
Before the VPN request even exists, the exam wants to know who can see the portal and who can act on what arrives. This is the permissions domain, roughly 16% of the questions.
Get clear on the two sides. External users are customers, organizations, request participants, stakeholders and reporters. Internal users are agents, collaborators, watchers, assignees, project admins, Jira admins and org admins. A collaborator can join internal discussion on a ticket but is not a full agent, and the exam likes to test that line.
Self-check questions for this stop:
- Can customers sign themselves up, or must an admin add them? Where is that set?
- What changes when customer access without login is allowed in global settings?
- How do you let one organization's members see each other's requests, but not other organizations' requests?
- Which project role do you use to add an agent, and how would issue-level security hide a sensitive HR ticket from most of the team?
If a customer reports "I can't see my request", work through product access, then project role, then permission scheme, then issue-level security. The blueprint lists that troubleshooting path almost word for word.
Stop 2: what does the customer see on the portal?
The customer sees a help center, a portal group called something like "Access and accounts", and a request type named "Can't connect to VPN". Building that experience is the largest slice of the exam: customer facing features at about 21%, plus the portal and notifications at about 12%.
For request types, know how each one maps to an underlying issue type and why hiding a request type from the portal is done by removing its portal groups. Know where a field is made required, in the field configuration or in the request type, and how the customer-facing status name can differ from the workflow status agents see.
Forms add a second layer. You should be comfortable building a form from a template, using sections with conditional logic, linking form fields to Jira fields, and attaching forms either by hand or through automation. Small form preferences show up too, such as locking a form after submission or saving a PDF each time it is resubmitted.
Email is the other front door. Expect questions on adding a custom email account, choosing which request type email creates, and using an allowlist or blocklist for domains. Approvals sit here as well: a preset list of approvers versus letting the customer choose one.
On the portal side, review branding, announcements, help-content links, portal translations and the virtual agent. The virtual agent needs a default request type and intents, and its standard flows (greet, escalate, resolve, match intent, auto-close) can be reworded. For a domain-by-domain checklist of all of this, the ACP-420 syllabus breakdown on CertFun lists every sub-objective in one place.
Stop 3: how does the ticket reach an agent on time?
The VPN ticket now lands in a queue, starts an SLA clock and may page someone on call. This is the agent facing features domain, about 19% of the exam.
Queues are JQL filters. The exam expects you to turn a requirement such as "show the IT team every open access request that is close to breaching" into a queue, using SLA functions in the JQL, and to group and reorder queues sensibly.
SLAs are where many candidates lose easy marks. An SLA has start, pause and stop conditions, goals that can differ by priority or request type, and a calendar that decides which hours count. Atlassian's own guide on how to create service level agreements to manage goals is worth working through in a free cloud site, because the exam asks you to troubleshoot SLAs that "aren't counting", and that skill only comes from seeing it happen.
The same domain covers the features tab. Know when to switch on service requests, incidents, problems, changes and post-incident reviews, plus on-call schedules, rotations, routing rules and escalation policies, and how alert priorities map to incident priorities.
Stop 4: what context gets attached to the ticket?
The agent looks at the request and needs context: which laptop, which service, which entitlement. That is the specialized capabilities domain, about 9%.
Note the wording for Assets. You must use object schemas, object types, objects and attributes, and reference Assets custom fields in request types, forms and queues, but you are not expected to configure Assets itself. Services work differently. You do enable and configure them, including service tiers, owners, change approvers, responders and stakeholders, and tiers can drive automation and alerts.
Products and entitlements are the third piece. If only customers with a valid product entitlement may raise a certain request type, making the Entitlement field required is the setting that enforces it.
Stop 5: what happens when the same ticket arrives 50 times a week?
When the VPN problem repeats, the team should stop handling it by hand. Two domains cover this: automation at about 11% and the knowledge base at about 5%.
Automation questions are scenario-based. You decide when a rule beats a plain notification, configure triggers, conditions and actions, and handle service-specific triggers such as "SLA threshold breached", "Approval completed" and "Forms submitted". Smart values for strings, dates and lists appear, as do auto-resolve and auto-close rules. When a rule fails, you check the audit log and the automation service status page, and you transfer rule ownership so error alerts reach the right person.
The knowledge base side is smaller but quick to learn. Link a Confluence space to the project, control who can view and edit articles, set article suggestions per request type, and restrict suggestions to specific labels. A good "VPN troubleshooting" article that the portal suggests before the request is submitted is the cheapest ticket you will ever close.
Stop 6: how does the team prove it is working?
Reporting closes the loop, and at about 7% it is a small domain with a precise toolset. You need JQL with service-specific functions such as approved, breached and entitlement, saved filters shared with the right people, and dashboards built from service management gadgets.
Customer satisfaction settings belong here too. The exam frames this as analysis: given SLA performance, CSAT scores and knowledge base reports, which project setting would you change? Go back to Stop 3 and Stop 5 for the answer, because reporting questions often point to a fix in another domain.
How should you split 180 minutes and your study weeks?
On exam day you have 2.4 minutes per question, which is generous. The bigger risk is the pass mark. Fifty out of 75 is about 67%, so you can miss 25 questions, but not by skipping whole domains.
Study by weight and by stop. Spend the first block on Stops 1 to 3, which carry about 68% of the exam between them, and build each setting in a free Jira Service Management Cloud site rather than only reading about it. Then cover automation, context and the knowledge base, and finish with reporting.
When you want to test yourself, a set of free ACP-420 sample questions shows how Atlassian phrases its scenarios. Read the explanation for every miss, then rebuild that setting in your test site.
Atlassian also offers a free on-demand collection to become an effective Jira Service Management project admin, which follows the same admin tasks this exam measures.
If you are still new to the agent side of service management, this short CertFun video on the related ACA-925 agent exam is a quick refresher on how agents work tickets before you configure the project around them.
The agent-level exam has its own ACA-925 blueprint guide, which is a sensible first step if you have never worked a queue yourself.
Frequently asked questions
1. How many questions are on the ACP-420 exam, and what is the passing score?
The exam has 75 questions and a 180-minute limit. Atlassian states the passing score as 50 correct answers, which is about 67%.
2. How much does the ACP-420 exam cost?
Atlassian lists the exam at $249 plus tax. It is delivered online with a remote proctor.
3. Does ACP-420 cover team-managed projects?
No. The exam covers Jira Service Management Cloud with company-managed projects only, so focus your practice on company-managed service projects.
4. How long is the ACP-420 certification valid?
Atlassian certifications are valid for 24 months. After that you need to renew to keep the credential active.
5. Which ACP-420 domain should I study first?
Start with configure customer facing features (about 21%), configure agent facing features (about 19%) and users, roles and permissions (about 16%). Together they make up 56% of the exam.
Before you book
Run the VPN ticket through your own test site one last time: raise it as a customer, watch it land in a queue, let an SLA breach, fire an automation rule, and find it in a report. If every stop behaves the way you expected, you are ready. When you want a timed run first, the ACP-420 practice exam mirrors the 75-question format.
Top comments (0)