DEV Community

Cover image for ACP-620 Practice Questions, 10 Answers Explained
Mihai Perdum
Mihai Perdum

Posted on Originally published at leanzero.net

ACP-620 Practice Questions, 10 Answers Explained

This page has ten free ACP-620 practice questions, and the exam they prepare you for is about to be retired. On 8 September 2026, a post on the Atlassian Community titled Certification updates: Upcoming changes to the Jira Cloud Administration exams announced that Managing Jira Projects for Cloud (ACP-620), Atlassian's certification exam for Jira project admins, goes away in January 2027. "If you would like to earn the Managing Jira Projects for Cloud before the retirement," it says, "be sure to plan on taking it before January 8th, 2027." The exam has been half price since that day, and Atlassian's certification page lists it at $124.

So you have a few weeks and a discount, and what candidates have always asked for is practice. In October 2020 one of them wrote in the thread ACP-620 Prep that "other than the few sample questions (7 odd), I was wondering if there are other sample questions I can access" (by April 2021 another candidate counted 41 in Atlassian's course). The ten below come two per exam topic. Further down, each one gets its answer, the reason every other option is wrong, and the sentence from Atlassian's Jira Cloud documentation that settles it, with a link so you can check us. We also tried five of them on our own test site.

Before you start, you should know where these come from. We wrote them at LeanZero, from the documentation. They're unofficial, LeanZero isn't affiliated with or endorsed by Atlassian, and none of them is taken from the exam. And I haven't sat ACP-620 myself. I hold four other Atlassian certifications, ACP-120 among them (I wrote up how I studied for those four).

How to use these practice questions: answer first, then read the doc quote

The questions are in one block and the answers in the next, so you can't see an answer by accident. Pick an option for each and say out loud why the others are wrong. Atlassian's exam topics PDF gives the same advice for its own sample questions: "Try all the sample questions and read all the explanations for every response option." A wrong option usually describes something real in Jira that belongs to a different setting, and I think most of the learning is in spotting which one.

One word will trip you up in the quotes. Atlassian's documentation now says "space" where our questions (and most admins) still say "project". They're the same thing. The documentation also says "work item" for what used to be called an issue. JQL, which several questions use, is Jira Query Language, the text you type to search for work items.

ACP-620 sample questions 1 to 10, grouped by exam topic

These are unofficial practice questions. Each has one correct option.

Project creation

Question 1. A Jira admin changes a project's key from MRW to MGP. A week later, you try to create a new, unrelated project and enter MRW as its key. What happens?

Option
A Only the original key-changer can reuse it.
B The new project gets MRW; it's freed instantly.
C You can, once MGP has been archived.
D You can't; the old key stays reserved.

Question 2. You are a Jira admin and want to stop all team-managed project creation site-wide, so you revoke the "Create team-managed projects" global permission from every group on the site. Does this fully prevent anyone from creating a new team-managed project?

Option
A No; Administer Jira holders still can.
B No; JSM projects are exempt from this.
C No; any project admin still can.
D Yes; revoking it removes the capability.

Board configuration

Question 3. You configure a company-managed board's swimlanes using the Queries (JQL) grouping method and try to delete the default 'Everything Else' swimlane to give it its own custom JQL query instead. What will you find?

Option
A It accepts a custom JQL query like Expedite.
B Deletable if a replacement catch-all swimlane exists.
C Always at the bottom, undeletable, with no JQL.
D The delete control is greyed out for both defaults.
E Deletion is possible only on team-managed boards.

Question 4. A company-managed Scrum board maps the Canceled status to a middle column instead of the board's right-most column. When the sprint closes, Jira reports incomplete work items even though the team considers those canceled items finished. What explains why Jira reports these work items as incomplete?

Option
A Only the left-most column counts as complete.
B Any status named Canceled is excluded from completion.
C The team lacks the Administer projects permission.
D Only the right-most column counts as complete.
E Status category decides completion, not position.

Managing projects

Question 5. You are a project admin on a company-managed project and open the release dialog for a version that still has 6 unresolved work items in it. What happens when you proceed with the release?

Option
A Jira makes you resolve the 6 work items before it will release.
B The release requires the global Administer Jira permission.
C Jira automatically moves them to Unreleased.
D You choose what happens to the unresolved items as part of the release.

Question 6. A security scheme in a company-managed project hides a highly sensitive bug from everyone except the Legal Only level, and then the bug moves into a separate company-managed project with no security scheme at all. What happens to its visibility?

Option
A The bug has no security level and is visible to Browse Projects users.
B The bug keeps its original level and remains hidden.
C The bug gets the default level and is visible to admins only.
D The move of the bug is blocked outright.

Automation

Question 7. The JQL query in a Lookup work items action matches 340 work items. How many of them can its lookupIssues list contain?

Option
A All 340 matching items, because the Scheduled trigger limit applies.
B Zero matching items, because every lookup exceeding 100 is rejected.
C Only the first 100 matching items.
D The first 999 matching items.

Question 8. An automation rule branches over a work item's six open subtasks, and each branch sets a field before checking whether another branch has already completed that step. What should you expect when the rule runs?

Option
A The main branch waits for all six of the branches to finish before continuing.
B The branches run in parallel with no guarantee of which one finishes first.
C The branches run one after another whenever all of them target subtasks.
D The branches run in parallel and pass field changes reliably to one another.
E The branches run in serial order so only one subtask is updated at a time.

Reporting

Question 9. You type a saved filter as status = Open ORDER BY created ASC AND priority = High, and Jira rejects it as invalid. Why?

Option
A Jira ignores anything typed after ORDER BY.
B ASC and DESC belong before the field name.
C ORDER BY must be the query's final clause.
D ORDER BY takes a single sort field.

Question 10. You need a JQL clause that excludes every work item with the Payments component while still including work items that have no component. Which clause returns that set?

Option
A component != Payments AND component is EMPTY
B component not in (Payments, EMPTY)
C component != Payments OR resolution is EMPTY
D component != Payments OR component is EMPTY

Answers to the ten ACP-620 practice questions, with the doc quote for each

We ran questions 3, 4, 5, 9 and 10 on a test site, in made-up demo projects, and you'll find the screens with their answers. The other five rest on the documentation sentence, because showing them live needs changes that are slow or risky to undo, like revoking a global permission or moving a secured work item.

Question 1 is D: the old project key stays reserved

Jira keeps MRW as a previous key of the renamed project, and that keeps old links working. A is wrong because who is asking makes no difference. B is wrong because a key change doesn't free the old key. C is wrong because archiving isn't one of the ways the key comes back.

"You won't be able to create a new space with the old space key. The old space key will only be available if you delete the space it was previously associated with."
(Atlassian's page on editing a project's details)

Further down the same page there's a second way to get the key back, and it's easy to miss: "Only organization, site, and Jira admins can delete a space key." An admin can delete the previous key from the project that holds it, and then MRW is free again.

Question 2 is A: Jira admins can always create team-managed projects

People with the Administer Jira global permission keep the ability whatever you revoke, so D overstates it. B is wrong because the documentation names no exemption for Jira Service Management (JSM) projects. C is wrong because the exception is a global permission, and being the admin of one project doesn't give it to you.

"People with the Administer Jira global permission can always create team-managed spaces, even when all other access to the Create team-managed spaces permission is removed."
(Atlassian's article on disabling team-managed projects)

Question 3 is C: Everything Else can be renamed and never deleted

Everything Else catches the work items that match none of the swimlanes above it, so it has no query of its own. A describes Expedite, the other default, which does carry a query. B invents a condition the page doesn't have. D is wrong because Expedite can be edited and deleted like any query swimlane. E is wrong because the page names no board type on which Everything Else can be deleted.

"Everything Else — this swimlane is always at the bottom of the screen, and cannot be deleted. It acts as a "catch-all" for work items that don't match the JQL of any of the swimlanes above it; hence, it has no JQL specified."
(Atlassian's page on configuring swimlanes)

The Swimlanes settings of a new Kanban board in Jira. Select method is set to Query. A table lists one swimlane, Expedite, with the JQL query priority = Highest and the description All issues with the highest priority. Its actions menu is open and offers Edit and Delete. Below the table is a required text field labelled Name of swimlane for other work items, filled with Everything Else.

The screen agrees with the answer, and it's laid out differently from the way the documentation describes it. The dropdown says Query where the documentation says Queries. Everything Else sits under the table as a required text field, so renaming that last swimlane is all you can do with it.

We also saw a difference between two new boards. A new Kanban board showed Expedite as soon as we chose Query. A new Scrum board showed an empty table and only the Everything Else field. Both boards started on the method None.

Question 4 is D: the last column decides what's complete

At sprint close Jira looks at which column the work item sits in. A has the board backwards. B is wrong because the name of a status doesn't matter, and Canceled counts as complete once you map it to the last column. C is wrong because a permission has nothing to do with how completion is counted.

A purple robot at left scratches its head over a pile of cards marked with red crosses while a small red robot sweeps past a row of six open cardboard boxes, a yellow sunflower-headed robot stamps a crossed card and a blue robot drops a crossed card into the last box, on a flat green background.

"Jira only considers work items in the right-most column of your board as complete."
(Atlassian's page on configuring columns)

E is the option I think plenty of working admins would pick, because a green Done status feels finished. So we tested it. We built a Scrum board with the columns To Do, Done and In Progress, in that order, which put the Done status (green category) in the middle. The sprint had three work items, one in Done and two in In Progress, and then we completed it.

The Complete sprint dialog in Jira. It reads: This sprint contains 2 completed work items and 1 open work item. Completed work items includes everything in the last column on the board, In Progress. Open work items includes everything from any other column on the board. Move these to a new sprint or the backlog. Below are a Move open work items to dropdown set to New sprint, a ticked Create a retrospective for this sprint box and a Complete sprint button.

Jira counted the two In Progress items as completed and the Done item as the 1 open work item, and it moved the Done item to the next sprint. The dialog even names the rule: "Completed work items includes everything in the last column on the board". We didn't open the sprint report afterwards.

Question 5 is D: the release dialog makes you choose

Jira doesn't block the release (A) and doesn't move anything by itself (C). B is wrong because project admin rights or the Manage versions permission are enough. The page quoted below also says "You must have Space admin or Manage versions permissions to create or edit a version."

"Choose what to do with any unresolved work items, and enter a release date."
(Atlassian's page on releasing a version)

A Jira release page for version 2.4.0 with the dialog Release 2.4.0 open. The dialog says This release contains 6 unresolved work items and offers two radio buttons, Move unresolved work items to with a Select version dropdown, and Ignore unresolved work items. Below are a Release date field, a ticked Create release notes box, a greyed Release button and Cancel.

We built a version called 2.4.0 with six open work items and opened the dialog. The two choices are worded Move unresolved work items to (with a version picker) and Ignore unresolved work items, and the field is required. The dialog also has a ticked Create release notes box that the documentation sentence doesn't mention. We pressed Cancel.

Question 6 is A: with no security scheme, the bug becomes visible

A security level only exists inside a security scheme, the list of levels a project uses to hide single work items. With no scheme in the destination, the level can't travel with the bug (B) and there's no default level to give it (C). Jira doesn't stop the move either (D). So the bug becomes visible to everyone who can browse the destination project.

"When you move work from one space to another, the work item will be assigned to the default work item security level in the new space. If that space has no security scheme, this work will be visible to anyone with access to the space."
(Atlassian's page on security schemes)

Question 7 is C: a lookup holds the first 100 work items

Lookup work items is the automation action that runs a search and hands the results to later steps as the {{lookupIssues}} list. It has its own cap of 100. B is wrong because a bigger result isn't rejected, the action just uses the first 100. A and D both borrow from a different limit. The page quoted below has a row called "Work items searched" with the number 999, and that row is about a scheduled JQL search. (Atlassian's automation pages now say "flow" for what our questions call a rule.) So a rule that summarises a search matching 340 work items works from the first 100 of them.

"When entering a JQL query for the Lookup work items action, only the first 100 work items will be used."
(Atlassian's page on automation service limits)

Question 8 is B: branches run in parallel, in no set order

A branch is the part of a rule that repeats its steps for each related work item, in this case each subtask. Those repeats run side by side, so one branch can't count on what another has done, and that's what's wrong with D. A is wrong because the main part of the rule carries on without waiting. C claims subtasks are a special case, and they're the documentation's own example of parallel branches. E says serial order, and the sentence below says parallel.

"Branches on multiple issues (such as 4 sub-tasks) will run in parallel with no guarantee one will finish before the next one starts. Therefore, you cannot rely on changes between branches."
(Atlassian's page on automation branches)

This page still says "issues" and "sub-tasks", Atlassian's older wording for work items and subtasks.

Question 9 is C: the sort clause goes last

A is wrong because Jira doesn't ignore the extra clause, it refuses the whole query. B and D are both wrong, and we checked them on the test site: status = Open ORDER BY created, priority DESC has two sort fields with the direction after the field, and Jira accepts it. The documentation's entry for the ORDER BY keyword says:

"Used to specify the fields by whose values the search results will be sorted. This requirement needs to be placed at the end of the JQL query, otherwise the JQL will be invalid."
(Atlassian's page on JQL keywords)

The Jira work item search in JQL mode with the query status = Open ORDER BY created ASC AND priority = High. The query box is outlined in red, the word AND is underlined, and a message below reads JQL error Expecting ',' but got 'AND'. (line 1, character 36) next to a Fix error button. The result list is empty.

I'd remember this screen for the exam and for work. Jira's message is Expecting ',' but got 'AND'. (line 1, character 36). After ORDER BY, Jira reads only a list of sort fields separated by commas, so when it meets AND it asks for a comma. If the error message was all you had, you'd go looking for a missing comma. Move the priority clause in front of ORDER BY and the query works.

Question 10 is D: != skips work items with no component

The != operator doesn't match work items where the field is empty, so you have to ask for the empty ones yourself.

"The "!=" operator will not match a field that has no value (i.e. a field that is empty). For example, component != fred will only match work items that have a component and the component is not "fred". To find work items that have a component other than "fred" or have no component, you would need to type: component != fred or component is empty."
(Atlassian's page on JQL operators)

We made six test work items for this one: two with the Payments component, two with Checkout and two with no component. Then we counted what each option returns.

A cobalt-blue robot at a counting table scoops up the star-marked cards with a metal scoop while two blank cards slide off the table edge toward the floor and a violet robot at right holds a clipboard and throws both hands up, one fallen card landing in a green bin, on a flat sunflower-yellow background.

Clause Work items returned (of 6) What happened
component != Payments with nothing added 2 The two Checkout items. The two with no component are missing.
A. ... AND component is EMPTY 0 No work item can have another component and no component at once.
B. component not in (Payments, EMPTY) 2 Listing EMPTY inside NOT IN doesn't bring the empty ones back.
C. ... OR resolution is EMPTY 6 Every test item was unresolved, so the two Payments items came back in.
D. ... OR component is EMPTY 4 The two Checkout items and the two with no component.

Option C is the risky one in real life. It returns results and looks plausible in a filter, while it answers a different question.

What we found while checking the ten

  1. All 10 quoted sentences were still on Atlassian's pages, word for word, when we fetched them on 19 November 2026.
  2. Question 4: the Complete sprint dialog counted a Done work item in a middle column as open, and 2 In Progress items in the last column as completed.
  3. Question 9: Jira's error never mentions ORDER BY. It asks for a comma at character 36.
  4. Question 10: the bare != clause returned 2 of 6 test work items, and the correct one returned 4.
  5. Question 3: a new Kanban board had the Expedite swimlane and a new Scrum board didn't.

How ACP-620 exam questions are weighted across the five exam topics

These figures come from Atlassian's certification page and the exam topics PDF it attaches (version 3, August 2026). The exam has 63 questions and runs 180 minutes. The passing score is "38 correct". It's proctored online, and Atlassian says the certification "is only applicable to users of Cloud implementations of Jira". You book it through the Schedule your exam link on that page.

Exam topic Weight on the page Range in the PDF
Board configuration 29% 25-35%
Managing projects 25% 25-35%
Reporting 19% 15-20%
Automation 14% 15-20%
Project creation 13% 10-15%

Automation is the odd row, at 14% on the page and 15-20% in the PDF. Both are Atlassian's numbers and I don't know which one the exam follows. Boards and day-to-day project management are at least half the exam on both counts, so I'd spend most of the time you have left on those two.

Neither document states the question format (how many questions ask for one answer and how many for several) or a pass mark as a percentage. I also didn't count the sample questions in Atlassian's own prep course, which sits behind a login.

Is it still a good idea to sit an exam that's being retired? The announcement answers part of that. A certification is valid for 24 months, the post says current holders get their dates "extended for an additional two years", and Managing Jira Projects for Cloud "will continue to be included in the Expert Designation". If 8 January is too soon for you, the same post says critical content from ACP-620 moves into Jira Administration for Cloud (ACP-120), which gets a new version in January 2027. Atlassian hasn't listed the new topics yet.

These are not ACP-620 dumps: original questions, checked against the docs

Search for practice material and some of what you'll find is question dumps, pages that claim to hold questions recalled from the exam. Ours come from the other direction. Each question starts from a sentence in Atlassian's documentation, and we only publish one after its quote has been found on the live page.

We composed 503 ACP-620 questions and 430 are published today. The rest were held back or withdrawn in review, and 5 of them went because the live product contradicted what we'd written. One of ours had named a board quick filter "Only My Work items", and on the live board we checked it's called "Assigned to me". Documentation moves too: on 18 November 2026 we re-quoted 7 questions and withdrew 2 because Atlassian's pages had changed.

Our final review pass re-checks every answer and every wrong option against the live Atlassian page. 330 of the 430 published questions have been through it, and the other 100, added in September, haven't yet. The ten questions on this page all come from the 330. The ACP-620 card on our site carries an Experimental badge. We added it in September because we count this pool as less mature than the other four.

When a reader finds a bad question, we fix it in the open, the way we did with four bad questions in the ACP-120 set.

Take the free ACP-620 practice exam next: the 20-question quick mock

Ten questions show you the kind of detail the documentation hides. They won't tell you if you're ready. For that, the ACP-620 practice exam on our site draws from all 430 questions. A quick mock is 20 questions. A full paper is 63, weighted with the page figures from the table above, and you can set a time limit at the exam's pace, 180 minutes for 63 questions. Every option has its own explanation and every answer links to its documentation sentence, same as on this page.

The top of the LeanZero ACP-620 practice exam page, with the LeanZero logo in the header, the breadcrumb Home, Certifications, ACP-620, a badge reading ACP-620, free practice, the heading Jira Project Administration, the line Quick mocks and full-length papers, weighted to the official blueprint and cited to the docs, and the buttons Go to the exam and How the key works.

It's free, with one condition I want you to read before you type your address. You ask for an access key by email, and the first time you use the key your address joins our newsletter list. The form says it like this: "Using the practice exams requires a subscription to our newsletter. You can unsubscribe at any time; that also ends exam access." Your answers, flags and notes stay in your browser. The same key opens every Atlassian and Claude practice exam on the certifications page.

With the weeks left, I'd do it this way. Take one quick mock cold and look at your weakest topic. Read the documentation pages behind the questions you missed, then open your own Jira and try the thing, the way we did with the sprint and the ORDER BY query. Pick your exam date now, with 8 January in mind, and use the full papers to see how far you are from it.

And tell me which of the ten caught you. My guess is question 4 for Scrum people and question 10 for everyone who writes filters, but I'd like to know if I'm wrong. If you think one of our questions or answers is off, email me at [email protected] and I'll check it against the page.


Originally published on leanzero.net. More Atlassian, Forge and local-AI write-ups at leanzero.net/blog, and if you're planning a migration or a Forge app, that's what we do: leanzero.net/services.

Top comments (0)