ACP-610 Online Practice Questions and Answers

Correct Answer: A

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.

Correct Answer: E

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. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

Correct Answer: CD

The two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint. References: Viewing the Velocity Chart, Scope change

Correct Answer: B

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. References: Managing Jira Projects Data Center and Server: Certification Bundle, Configuring projects | Administering Jira applications Data Center and ..., [Working with issues | Jira Software Cloud]

Correct Answer: D

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

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

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. References: [Working with sub-tasks], [Configuring columns]

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.