ACP-610 Online Practice Questions and Answers

Correct Answer: C

The Cumulative Flow Diagram is the report that provides the information that the head of customer service wants. The Cumulative Flow Diagram is a tool that visualizes the quantity and distribution of work items along different stages of a process. The report shows how many work items are in each stage at any given time, and how they flow from one stage to another. The report can help identify potential bottlenecks in the support 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 "Waiting for Customer" stage, it may indicate that the customers are not responding quickly enough or that the support team is not following up effectively. The report can also help monitor the overall progress and performance of the support teams by showing the total number of work items created, resolved, and remaining over time. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

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: A

An epic burndown chart shows the progress towards completing an epic over time. It is useful for tracking how much work is left to be done and predicting when it will be completed. The epic burndown chart is based on the estimation statistic

that is configured for the board (either story points or issue count) and shows the total amount of work remaining in the epic at the end of each sprint. You can use this chart to estimate how many additional sprints will be needed to complete

an epic. References: :

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-epic- burndown-chart/

Correct Answer: E

One difference between Scrum and Kanban boards is that only Scrum boards support selecting an estimation method. Estimation is a way of measuring how much work is required to complete an issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on managing the flow of work rather than planning sprints. References: Configuring estimation and tracking, Estimating an issue

Correct Answer: E

The solution that will meet the team's requirements of using agile boards with minimal disruption to their current configuration is to use a Kanban board for tasks and a Scrum board for features in the current project. This way, they can use different agile methodologies for different issue types without creating a new project or changing their existing configuration. They can use a Kanban board for tasks to handle them based on priority and rank and release them incrementally as needed. They can use a Scrum board for features to develop them during three week iterations with sprints and backlogs. The other solutions are either not feasible or not optimal for their needs. Therefore, the correct answer is E. References: [Creating a board], [Using a Scrum board], [Using a Kanban board]

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: D

A Control Chart is the best report to provide the information that Darren wants. A Control Chart shows the cycle time or lead time for your team's issues, broken down by the time spent in each status. It helps you identify whether data from the

current process can be used to determine future performance. Less time in the Waiting for Support status indicates optimal team performance, as it means that the issues are being addressed promptly and efficiently. A Control Chart also

provides a way to dynamically analyze not only specific days but also specific time frames, by using the date range selector and the zoom feature. You can also filter the chart by issue type, assignee, label, or any other field. References:

Managing Jira Projects Data Center and Server:

Certification Bundle, [Control Chart | Jira Software Cloud]

Correct Answer: C

Thecomponent configuration of the project shows that each component has a different default assignee. The default assignee is the user who will be automatically assigned to an issue when that component is selected. The image shows that

the default assignee for the Signoff component is Project admin. Therefore, if Dave creates an issue and selects Signoff as the component, the issue will be assigned to Project admin.

The other options are not correct because:

If UX is selected, the issue will not be assigned to admin, but to Unassigned. The image shows that the default assignee for the UX component is Unassigned, which means that no user will be automatically assigned to an issue with that

component.

If Login and Signoff are selected, the issue will not be assigned to Project admin, but to Project lead. The image shows that the default assignee for multiple components is Project lead, which means that if more than one component is

selected, the issue will be assigned to Project lead. If Test is selected, the issue will not be assigned to Project lead, but to Unassigned. The image shows that the default assignee for the Test component is Unassigned, which means that no

user will be automatically assigned to an issue with that component.

Correct Answer: C

If Quang can transition issues from Resolved to Done using the workflow button on issues in his project, but cannot drag them from Resolved to Done on the project's Kanban board, a possible reason is that the statuses are mapped to the same column. The columns on a Kanban board represent the stages of work in a project. Each column can have one or more statuses mapped to it. To move an issue from one column to another, you need to drag and drop it to a column that has a different status mapped to it. If the statuses are mapped to the same column, you cannot move the issue by dragging it on the board, but you can still use the workflow button to change its status. References: Configuring columns, Moving an issue

Correct Answer: E

Three versions will be available in the versions panel of the project backlog:

epsilon, delta, and gamma. These are the three unreleased versions in the project, as shown in the image. The versions panel only shows unreleased versions, as they are used to plan and track the progress of upcoming releases. Released

and archived versions are not shown in the versions panel, as they are considered completed and no longer relevant for planning purposes. References: [Working with versions], [Managing Jira Projects Data Center and Server: Certification

Bundle]