Atlassian ACP-610 Practice Exams
Last updated on Oct 22,2026- Exam Code: ACP-610
- Exam Name: Managing Jira Projects for Data Center and Server
- Certification Provider: Atlassian
- Latest update: Oct 22,2026
You have all the necessary permissions to transition issues on your board. There are no conditions or validators. One column has two statuses mapped to it You want to drag an issue into that column.
Which statement is true?
- A . You cannot drop it into either status.
- B . You can drop it only into the bottom status.
- C . You can drop it only into the top status.
- D . You can drop it into either pop-up window.
- E . You can drop it into either status
All projects use a shared permission scheme.
The Browse Projects permission needs to be updated so that project administrators can manage access to their own projects.
What entry must be added to the Browse Projects permission?
- A . Application Access
- B . Project Lead
- C . Single User Project Role
- D . Group
Your team is using a Scrum board and has many issues planned for future sprints.
You need to configure a secondary board that:
• excludes those planned issues from the board but not from the reports
• hides issues in real time when users select multiple conditions
Which two board configurations satisfy the requirements? (Choose two.)
- A . swimlanes
- B . board sub-filter
- C . board filter
- D . column constraint
- E . quick filters
B, E
Explanation:
To exclude the planned issues from the board but not from the reports, you need to use a board sub-filter. A board sub-filter is an additional JQL query that is applied to the board filter to further refine the issues displayed on the board. The sub-filter does not affect the reports, which are based on the board filter only. To hide issues in real time when users select multiple conditions, you need to use quick filters. Quick filters are buttons that allow users to dynamically change the view of the board by applying one or more JQL queries. Users can select or deselect quick filters to show or hide issues that match the criteria.
Reference: Configuring filters, Configuring quick filters
Project DEV was just created and has zero issues. It uses the simplified workflow that is not shared.
You are a project administrator in DEV.
Which workflow change im.si definitely he escalated to a Jira administrator?
- A . remove the in Progress status
- B . update the Priority field during a transition
- C . add two existing statuses
- D . delete a Global transition
- E . change the initial status of the workflow
D
Explanation:
A global transition is a transition that can be triggered from any status in the workflow. Deleting a global transition may affect the workflow logic and the ability to move issues between statuses. Therefore, only a Jira administrator can delete a global transition. The other actions can be performed by a project administrator in a simplified workflow that is not shared.
Reference:
https://support.atlassian.com/jira-software-cloud/docs/what-are-workflows/ https://support.atlassian.com/jira-software-cloud/docs/configure-a-simplified-workflow/
Which statement is true about Jira attachments?
- A . Users can search for issues that contain attachments
- B . Users need Work On Issues permission to remove attachments.
- C . Users need Edit Issues permission to add attachments.
- D . Project administrators can disable attachments through project settings.
A
Explanation:
Jira attachments are files that users can attach to issues to share information with their team. Users can search for issues that contain attachments by using the attachments field in the advanced search.
For example, attachments is not EMPTY will return all issues that have at least one attachment.
Therefore, option A is true.
Some issues in your project have labels and others do not.
Some tasks in your project are identified by a distinct label: daily_business. You need to prevent these issues from being displayed on the team’s Scrum board.
Which solution meets this requirement?
- A . • Create a quick filter
• Add: NOT labels="daily_business_ - B . • Update the board sub-filter
• Add; AND NOT labels = daily business - C . • Update the board filter
• Add: AND labels NOT IN (daily.business, EMPTY: - D . • Update the board filter
• Add: AND (labels != daily, business OR labels IS EMF
D
Explanation:
The solution that meets this requirement is to update the board filter and add: AND (labels != daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from the board filter, which determines which issues are displayed on the board. It will also include issues that have no labels at all, as some issues in your project may not have labels. The other solutions do not meet this requirement, as they either do not exclude issues with daily_business label, or exclude issues with no labels.
Reference: Configuring filters, Advanced searching – operators reference
Some issues in your project have labels and others do not.
Some tasks in your project are identified by a distinct label: daily_business. You need to prevent these issues from being displayed on the team’s Scrum board.
Which solution meets this requirement?
- A . • Create a quick filter
• Add: NOT labels="daily_business_ - B . • Update the board sub-filter
• Add; AND NOT labels = daily business - C . • Update the board filter
• Add: AND labels NOT IN (daily.business, EMPTY: - D . • Update the board filter
• Add: AND (labels != daily, business OR labels IS EMF
D
Explanation:
The solution that meets this requirement is to update the board filter and add: AND (labels != daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from the board filter, which determines which issues are displayed on the board. It will also include issues that have no labels at all, as some issues in your project may not have labels. The other solutions do not meet this requirement, as they either do not exclude issues with daily_business label, or exclude issues with no labels.
Reference: Configuring filters, Advanced searching – operators reference
add the new custom field to a transition screen
What can Max do?
- A . neither action
- B . only action 2
- C . both actions
- D . only action 1
B
Explanation:
A custom field is a field that is not part of the default set of Jira system fields. Creating a new custom field requires Jira administration permissions, so Max cannot perform action 1. However, adding an existing custom field to a transition screen does not require Jira administration permissions, as long as the screen is not shared with other projects or issue types. Therefore, Max can perform action 2 if he has the “Administer Projects” permission and the screen meets the prerequisites for editing.
Reference:
https://support.atlassian.com/jira-software-cloud/docs/what-are-custom-fields/
https://support.atlassian.com/jira-software-cloud/docs/configure-screens/
Savresh can create issues and assign them to anyone in the Testers group. However, they cannot re-assign issues to Savresh.
What are two possible reasons for this? (Choose two.)
- A . Savresh needs to be a component lead.
- B . Testers need Edit Issues permission.
- C . Savresh needs to be a project lead.
- D . Testers need Assignable User permission.
- E . Testers need Assign Issues permission.
- F . Savresh needs Assignable User permission.
EF
Explanation:
Savresh needs Assignable User permission. This permission determines which users can be assigned to issues in a project1. If Savresh does not have this permission, they will not be able to re-assign issues to themselves, even if they can create and assign issues to others.
Testers need Assign Issues permission. This permission determines which users can assign issues to other users or to themselves1. If the Testers group does not have this permission, they will not be able to re-assign issues to anyone, including Savresh.
Your Scrum board has the following filter query:
project in (ENG. DEV) and type in (Bug. Task) ORDER BY Priority ASC
You have the necessary permissions but you are unable to drag an issue into a future sprint in the backlog.
- A . Identify the reason.
- B . The filter should be in DESC order.
- C . Stories are missing from the query.
- D . Ranking is disabled.
- E . The query should only have one project.
- F . The active sprint has not yet been completed.
D
Explanation:
The reason why you are unable to drag an issue into a future sprint in the backlog is that ranking is disabled. Ranking is a feature that allows you to order issues based on their relative priority or importance. Ranking is enabled by adding “ORDER BY Rank ASC” or “ORDER BY Rank DESC” to your board filter query. Ranking is required for Scrum boards, as it determines the order of issues in your backlog and sprints. If ranking is disabled, you cannot drag and drop issues in your backlog or plan future sprints.
Reference: Ranking an issue, Configuring filters