ACP-610 Online Practice Questions and Answers

Correct Answer: BC

Two project roles that must be granted to view code commits in the DEV project are:

Developers

Administrators

According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role

(Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.

The other options are not correct because:

Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project. Sprinters do not have the View Development Tools permission in the DEV permission scheme,

so they cannot see code commits in the DEV project. Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

Correct Answer: A

A project administrator can remove watchers from project notifications, if they have the Manage Watchers permission. This is a task that does not require Jira administrator access, and can be done by the project administrator from the issue view. Removing a priority value used by the project, updating permissions for a project user, and limiting who can bulk edit project issues are all tasks that require Jira administrator access, and cannot be done by the project administrator. References: Managing watchers, Managing Jira Projects Data Center and Server: Certification Bundle

Correct Answer: D

Correct Answer: C

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. References: Viewing the Velocity Chart, Scope change

Correct Answer: E

The Velocity Chart is the best report to compare work committed and work completed in sprints over time. It shows the average amount of work that a team can complete in a sprint, based on the historical data of previous sprints. It also

shows how much work was planned and how much was actually completed in each sprint. By looking at the Velocity Chart, a team can see if they are overestimating or underestimating their capacity, and adjust their planning accordingly.

Therefore, option E is correct. References: Velocity Chart, Managing Jira Projects Data Center and Server:

Certification Bundle

Correct Answer: D

The epic completion date is hard to predict because the team adds new stories throughout the epic. This means that the scope of the epic is not fixed and can change over time. The Epic Report shows the progress of an epic by comparing the estimated amount of work to the completed work. The report also shows a projected completion date based on the team'saverage velocity. However, if the team keeps adding new stories to the epic, the estimated amount of work will increase and the projected completion date will be pushed further. This makes it difficult to plan and deliver the epic within a certain timeframe. References: Managing Jira Projects Data Center and Server: Certification Bundle, Epic Report

Correct Answer: B

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. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

Correct Answer: C

Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B. Move Issues permission allows him to initiate the move operation, while Create Issues permission allows him to create the issue in the destination project. Transition Issues permission is not relevant for moving issues, as it only affects workflow transitions. Administer Projects permission is not required for moving issues, unless the issue type or workflow needs to be changed during the move. Assign Issues permission is not required for moving issues, unless the assignee needs to be changed during the move. References: [Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

Correct Answer: B

Correct Answer: B

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. References: [Ranking an issue], [Configuring filters]