Free ACP-610 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

As a project administrator of DEV, you can update some project settings such as project shortcuts,

description, name, and versions. However, you cannot update the notification scheme or the key of

the project, as these are global settings that require Jira administrator permissions. Therefore, the

correct

answer

is

A

and

C. Reference: Managing

project

permissions, Managing

project

notifications, Changing the project key

:

The reason why your team completed more story points than they committed in their last sprint is

that someone increased the story point value on an issue mid-sprint. This will increase the total story

points completed at the end of the sprint, but not affect the total story points committed at the start

of the sprint. Therefore, it will result in a positive scope change. The other reasons mentioned in the

question do not explain why your team completed more story points than they committed, as they

either do not affect story points at all, or affect both committed and completed story points

equally. Reference: Viewing the Velocity Chart, Scope change

The Cumulative Flow Diagram is the report that provides the needed insight to see if frequent scope

change mid-sprint is causing bottlenecks. The Cumulative Flow Diagram shows the quantity and

distribution of work items along different stages of a process over time. The report can help identify

potential bottlenecks in the workflow by showing where work items accumulate or stagnate over

time. For example, if the report shows a sudden increase or a wide band of work items in the “In

Progress” stage, it may indicate that the team is overloaded with work or facing some blockers. If the

team often accepts new requests from outside groups during an active sprint, the report can show

how this affects the flow of work and the completion of the sprint goal. Reference: Managing Jira

Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Atlassian_ACP-610/page_21_img_1.jpg

A Sprint Report is the best report to provide a single comprehensive list of issues that were

completed in the last 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 team can see the story points associated with each completed issue, as well as the issue type of

each completed issue. They can also see the description of each issue that has not been completed

by clicking on the issue key or summary. 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]

:

When a project is created with a shared configuration, it inherits the configurations of an existing

project. This includes the workflow, issue types, screens, fields, permissions, notifications, and

schemes associated with them. However, the component lead assignments and versions are specific

to each project and are not shared. Therefore, the correct answer is C and E. Reference: Creating a

project, Configuring projects

:

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

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

The statement that is definitely true is that changes to the rank of integration issues on Jo’s board are

reflected on Sam’s board. This is because ranking is a global attribute that affects how issues are

ordered across projects and boards based on their relative priority. When Jo updates his Scrum

board’s saved filter to include integration issues from Sam’s project, he can rank them along with his

own issues on his board. These changes will also affect how these issues are ranked on Sam’s board,

as they share the same rank field value. The other statements are not necessarily true or false, as

they depend on other factors such as permissions, workflow configurations, or board settings.

Therefore, the correct answer is B. Reference: [Ranking an issue], [Configuring filters]

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]

A Kanban board is the best option for Gen to prioritize and triage support requests using drag-and- drop. A Kanban board allows Gen to quickly assign issues to herself or other team members by dragging them to the appropriate column. She can also transition issues to In Progress by moving them across the workflow. Additionally, she can instantly associate issues with Epics by dragging them to the Epic panel on the right side of the board. A Kanban board also provides a visual overview of the current status and progress of the support requests. Reference: Managing Jira Projects Data Center and Server: Certification Bundle, Configuring projects | Administering Jira applications Data Center and …, [Working with issues | Jira Software Cloud]

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]

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]