ACP-610 Online Practice Questions and Answers

Correct Answer: D

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

The gadget that meets Kim's need is the Issue Statistics gadget. This gadget displays the collection of issues returned from a filter, broken down by a field. Kim can configure the gadget to use her project as the filter, and the issue type as the field. The gadget will then show the following information for issues in her project: the total count of all issues the total count of each issue type the distribution of each issue type as a percentage a graphical chart display of that percentage The other gadgets are not suitable because: The Heat Map gadget displays issues from a project or filter, grouped by a statistic type, in a heat map format. Issues can be grouped by any statistic type (e.g. Status, Priority, Assignee, etc). However, this gadget does not show the total count of all issues, nor the distribution of each issue type as a percentage. The Two Dimensional Filter Statistics gadget displays issues from a filter in a table format, where each cell shows the number of issues for a given combination of two statistics types (e.g. Status vs Priority, Assignee vs Issue Type, etc). This gadget does not show the total count of all issues, nor a graphical chart display of that percentage. The Filter Results gadget displays the results of an issue filter on the dashboard. This gadget does not show any summary or breakdown of the issues by any field, nor a graphical chart display of that percentage. The Issues in Progress gadget displays all issues that are in progress and assigned to the user viewing the dashboard. This gadget does not show any information about other issues or issue types in the project, nor a graphical chart display of that percentage. References: Use dashboard gadgets, Gadgets for Jira applications

Correct Answer: C

The board filter query that meets these requirements is (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic). This query will show all issue types from project BERT except sub-tasks, as well as only epics from project ERNIE. It will not show issues from any other projects, as it uses the OR operator to combine two conditions that specify the project names. The other queries do not meet all the requirements, as they either include sub-tasks from project BERT, exclude epics from project ERNIE, or show issues from other projects. References: Configuring filters, Advanced searching - fields reference

Correct Answer: BE

A project screen is a screen that is used to display or edit issue fields in a project. A project administrator can modify his project screen if it meets the following prerequisites: The screen is not shared with other projects or issue types. The screen does not use the default system fields. The screen scheme and the issue type screen scheme are not shared with other projects or issue types. If these conditions are met, the project administrator can perform the following actions on his project screen: Create a new tab Rename a tab Remove a tab Add an existing field Remove a field Reorder fields The project administrator cannot create a new field, set a default value for a field, or make a field required. These actions require Jira administration permissions. References: : https://support.atlassian.com/jira-software- cloud/ docs/configure-field-layouts-in-the-issue-view/ https://support.atlassian.com/jira-software-cloud/docs/what-are-issue-fields/

Correct Answer: B

Correct Answer: B

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