Atlassian ACP-610 Practice Exams
Last updated on Oct 21,2026- Exam Code: ACP-610
- Exam Name: Managing Jira Projects for Data Center and Server
- Certification Provider: Atlassian
- Latest update: Oct 21,2026
Question #11
The release manager is requesting a list of all issues included in a particular sprint.
Which report will provide this information?
- A . Control Chart
- B . Release Burndown
- C . Version Report
- D . Sprint Report
- E . Average Age Report
Correct Answer: D
D
Explanation:
A Sprint Report is the best report to provide a list of all issues included in a particular sprint. A Sprint Report shows the scope, status, and completion date of each sprint. It also displays a breakdown of the completed, incomplete, and added issues in the sprint. The release manager can easily view the list of incomplete issues in the Issue Navigator by clicking on the View in Issue Navigator link at the bottom of the report. A Sprint Report also helps to track the team’s performance and identify any scope changes during the sprint.
Reference: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]
D
Explanation:
A Sprint Report is the best report to provide a list of all issues included in a particular sprint. A Sprint Report shows the scope, status, and completion date of each sprint. It also displays a breakdown of the completed, incomplete, and added issues in the sprint. The release manager can easily view the list of incomplete issues in the Issue Navigator by clicking on the View in Issue Navigator link at the bottom of the report. A Sprint Report also helps to track the team’s performance and identify any scope changes during the sprint.
Reference: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]
Question #12
Which statement is definitely true about sub-tasks being used on a Scrurn board?
- A . Sub-task estimations are rolled up and displayed as the Original Estimate on the parent card.
- B . Sub-tasks can only be created by board administrators
- C . Sub-tasks can be displayed as cards in the Active sprints view.
- D . Sub-tasks can be displayed as cards in the Backlog view.
- E . Sub-tasks will automatically get resolved when the parent is moved to the Done column.
Correct Answer: C
C
Explanation:
Sub-tasks are a type of issue that can be used to break down a parent issue into smaller and more manageable pieces. Sub-tasks can be displayed as cards in the Active sprints view of a Scrum board, which allows you to track their progress and status. However, sub-task estimations are not rolled up and displayed on the parent card, as they use a different field than the parent issue. Sub-tasks can be created by anyone who has the Create Issue permission in the project, not only by board administrators. Sub-tasks cannot be displayed as cards in the Backlog view, as they are only visible under their parent issues. Sub-tasks will not automatically get resolved when the parent is moved to the Done column, as they have their own workflow transitions and conditions. Therefore, the correct answer is C.
Reference: [Working with sub-tasks], [Configuring columns]
C
Explanation:
Sub-tasks are a type of issue that can be used to break down a parent issue into smaller and more manageable pieces. Sub-tasks can be displayed as cards in the Active sprints view of a Scrum board, which allows you to track their progress and status. However, sub-task estimations are not rolled up and displayed on the parent card, as they use a different field than the parent issue. Sub-tasks can be created by anyone who has the Create Issue permission in the project, not only by board administrators. Sub-tasks cannot be displayed as cards in the Backlog view, as they are only visible under their parent issues. Sub-tasks will not automatically get resolved when the parent is moved to the Done column, as they have their own workflow transitions and conditions. Therefore, the correct answer is C.
Reference: [Working with sub-tasks], [Configuring columns]
Question #13
Your team failed to meet their last sprint commitment and you want to investigate further.
You need an agile report that:
• shows you a list of the incomplete issues in the sprint
• allows you to quickly view that list in the Issue Navigator
Which report meets this need?
- A . Burndown Chart
- B . Control Chart
- C . Cumulative Flow Diagram
- D . Sprint Report
- E . Velocity Chart
Correct Answer: D
D
Explanation:
A Sprint Report is also the best report to meet this need. As explained above, a Sprint Report shows a list of the incomplete issues in the sprint and allows you to quickly view that list in the Issue Navigator. A Sprint Report can help you investigate why your team failed to meet their last sprint commitment by showing you how many issues were added or removed during the sprint, how many issues were completed or not completed, and how much work was carried over to the next sprint.
Reference: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]
D
Explanation:
A Sprint Report is also the best report to meet this need. As explained above, a Sprint Report shows a list of the incomplete issues in the sprint and allows you to quickly view that list in the Issue Navigator. A Sprint Report can help you investigate why your team failed to meet their last sprint commitment by showing you how many issues were added or removed during the sprint, how many issues were completed or not completed, and how much work was carried over to the next sprint.
Reference: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]
Question #14
A product owner is responsible for two scrum teams.
He needs to:
• see a snapshot displaying key sprint information like time elapsed and percentage of scope change
• monitor the overall progress of the next release to determine if it will ship on time
Which two gadgets will show this information? (Choose two.)
- A . Version Report
- B . Issues in progress
- C . Sprint Health Gadget
- D . Activity Stream
- E . Projects
- F . Filter Results
Correct Answer: A, C
A, C
Explanation:
The Version Report and the Sprint Health Gadget are two gadgets that can show the information that the product owner needs. The Version Report shows the progress of a version by comparing the estimated amount of work to the completed work. The report also shows a projected release date based on the team’s average velocity. The product owner can use this report to monitor the overall progress of the next release and determine if it will ship on time. The Sprint Health Gadget shows a snapshot of key sprint information such as time elapsed, percentage of scope change, sprint goal, and team members’ availability. The product owner can use this gadget to see how each scrum team is performing in their current sprint and identify any issues or risks.
Reference: Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget
A, C
Explanation:
The Version Report and the Sprint Health Gadget are two gadgets that can show the information that the product owner needs. The Version Report shows the progress of a version by comparing the estimated amount of work to the completed work. The report also shows a projected release date based on the team’s average velocity. The product owner can use this report to monitor the overall progress of the next release and determine if it will ship on time. The Sprint Health Gadget shows a snapshot of key sprint information such as time elapsed, percentage of scope change, sprint goal, and team members’ availability. The product owner can use this gadget to see how each scrum team is performing in their current sprint and identify any issues or risks.
Reference: Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget
Question #15
You manage a Scrum project with two development teams.
Issues are associated with each team using a custom field called Jean.
Parallel sprints have been disabled.
Which setup will provide each team with an individual Burndown Chart?
- A . a single Scrum board with quick filters
- B . a single Scrum board using the Team field as the Estimation Statistic
- C . two Scrum boards using the Team field as the Estimation Statistic
- D . two Scrum boards using the Team field in their board filters
Correct Answer: D
D
Explanation:
If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D.
Reference: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]
D
Explanation:
If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D.
Reference: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]
Question #15
You manage a Scrum project with two development teams.
Issues are associated with each team using a custom field called Jean.
Parallel sprints have been disabled.
Which setup will provide each team with an individual Burndown Chart?
- A . a single Scrum board with quick filters
- B . a single Scrum board using the Team field as the Estimation Statistic
- C . two Scrum boards using the Team field as the Estimation Statistic
- D . two Scrum boards using the Team field in their board filters
Correct Answer: D
D
Explanation:
If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D.
Reference: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]
D
Explanation:
If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D.
Reference: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]
Question #17
The ‘’Open issues filter of your project shows bugs, along with epics and stones.
You then view the project’s Scrum board where you only see epics and stories but not bugs.
Which configuration is responsible for this behavior?
- A . board filter query
- B . issue type scheme
- C . board filter shares
- D . swim lanes
- E . board sub-filter
Correct Answer: A
Question #18
Quang is a project administrator. He added several fields to his project screen. All team members have Edit Issues permission in this project.
Which field can definitely be set all project team member-."1
- A . Attachment
- B . Assignee
- C . Fix Version/s
- D . Labels
- E . Issue Type
Correct Answer: D
D
Explanation:
The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how to configure fields in Jira, see Configuring fields and screens.
Reference: Configuring fields and screens
D
Explanation:
The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how to configure fields in Jira, see Configuring fields and screens.
Reference: Configuring fields and screens
Question #19
You are Tasked with restoring archived sub-tasks in a project.
The project to which the sub-tasks belong has since been archived, as well.
Which is the toned course of action?
- A . restore the parent issues only
- B . restore the project only
- C . restore the parent issues, then the sub-tasks
- D . restore the project, then the sub-tasks
- E . restore the project, then the parent issues
Correct Answer: D
D
Explanation:
The best course of action is to restore the project, then the sub-tasks. This is because sub-tasks cannot exist without their parent issues, and parent issues cannot exist without their project. Therefore, restoring the project first will ensure that the parent issues are also restored, and then restoring the sub-tasks will re-attach them to their parent issues. Restoring the parent issues only will not restore the sub-tasks, as they are still archived. Restoring the project only will not restore the sub-tasks, as they need to be restored separately. Restoring the parent issues, then the sub-tasks will not work, as the parent issues cannot be restored without their project. Restoring the project, then the parent issues is unnecessary, as the parent issues are already restored with the project.
Reference: [Restoring an archived issue], [Managing Jira Projects Data Center and Server: Certification Bundle]
D
Explanation:
The best course of action is to restore the project, then the sub-tasks. This is because sub-tasks cannot exist without their parent issues, and parent issues cannot exist without their project. Therefore, restoring the project first will ensure that the parent issues are also restored, and then restoring the sub-tasks will re-attach them to their parent issues. Restoring the parent issues only will not restore the sub-tasks, as they are still archived. Restoring the project only will not restore the sub-tasks, as they need to be restored separately. Restoring the parent issues, then the sub-tasks will not work, as the parent issues cannot be restored without their project. Restoring the project, then the parent issues is unnecessary, as the parent issues are already restored with the project.
Reference: [Restoring an archived issue], [Managing Jira Projects Data Center and Server: Certification Bundle]
Question #20
Bethany knows the URL of an issue that she wants to restore in a particular project.
What are the minimum two permissions that she needs to restore the issue? (Choose two.}
- A . Restore Issues
- B . Browse Project Archive
- C . Move Issues
- D . Edit Issues
- E . Browse Projects
Correct Answer: A, B
A, B
Explanation:
To restore an issue from the project archive, Bethany needs two permissions: Restore Issues and Browse Project Archive. The Restore Issues permission allows Bethany to restore issues that have been archived in a project. The Browse Project Archive permission allows Bethany to view the archived issues in a project. Without these permissions, Bethany will not be able to access or restore the archived issue, even if she knows the URL. The other permissions are not relevant for restoring an issue. The Move Issues permission allows Bethany to move issues from one project to another. The Edit Issues permission allows Bethany to modify the details of an issue. The Browse Projects permission allows Bethany to see the project and its issues, but not the archived ones. For more information on how to archive and restore issues, see Archive and restore issues and Manage project permissions.
Reference: Archive and restore issues, Manage project permissions
A, B
Explanation:
To restore an issue from the project archive, Bethany needs two permissions: Restore Issues and Browse Project Archive. The Restore Issues permission allows Bethany to restore issues that have been archived in a project. The Browse Project Archive permission allows Bethany to view the archived issues in a project. Without these permissions, Bethany will not be able to access or restore the archived issue, even if she knows the URL. The other permissions are not relevant for restoring an issue. The Move Issues permission allows Bethany to move issues from one project to another. The Edit Issues permission allows Bethany to modify the details of an issue. The Browse Projects permission allows Bethany to see the project and its issues, but not the archived ones. For more information on how to archive and restore issues, see Archive and restore issues and Manage project permissions.
Reference: Archive and restore issues, Manage project permissions