Question 1

Jon notices that an issue was created incorrectly in project

Accepted Answer

C

Explanation: 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. Reference: [Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

Question 2

Some issues in your project have labels and others do not.
Some tasks in your project are identified by a distinct label: daily_business. You need to prevent
these issues from being displayed on the team's Scrum board
Which solution meets this requirement?

Accepted Answer

D

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

Question 3

Quang can transition issues from Resolved to Done using the workflow button on issues in his
project. However, he cannot drag then from Resolved to Done on the project's Kanban board Identify
a possible reason why.

Accepted Answer

C

Explanation: 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. Reference: Configuring columns, Moving an issue

Question 4

Your team uses a custom field of type Labels to track keywords associated with incoming requests.
Issues can have multiple keywords, and new keywords can be added at any time. They want to see
keywords displayed prominently when viewing all cards on a board. Which configuration meets this
need?

Accepted Answer

A

Explanation: The best configuration to meet the team’s need of displaying keywords prominently when viewing all cards on a board is card layout. Card layout allows you to customize what fields are shown on each card on a board, and you can choose to show any custom field of type Labels on the cards. Swimlanes are used to group issues into horizontal lanes based on certain criteria, such as assignee, priority, or query, but they do not show labels on each card. Card colours are used to highlight issues based on certain attributes, such as issue type, priority, or query, but they do not show labels on each card either. Issue detail view is used to show more information about an issue when you select it on a board, but it does not affect how cards are displayed on the board. Therefore, the correct answer is A. Reference: [Configuring card layout], [Configuring swimlanes], [Configuring card colours], [Using boards]

Question 5

The MR manager is unsure whether she wants a Scrum or Kanban board for her project. Identify one difference between the boards.

Accepted Answer

E

Explanation: 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. Reference: Configuring estimation and tracking, Estimating an issue

Question 6

The ‘’Open issues filter of your project shows bugs, along with epics and stones.
You then view the project's Scrum board where you only see epics and stories but not bugs.
Which configuration is responsible for this behavior?

Accepted Answer

A

Explanation: :

Question 7

A project administrator wants to modify his project screen. The project screen meets all the prerequisites for him to be able to edit it. Which two actions can he perform? (Choose two.}

Accepted Answer

B, E

Explanation: 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. Reference: : 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/

Question 8

A Scrum team working on multiple epics complains that they are constantly being pushed to
complete more work than they think can be completed. Apparently, the product owner has
constantly overloaded each of the past 8 sprints. Which single report can instantly prove their
statement?

Accepted Answer

A

Explanation: :

Question 9

A scrum team asks you for a single comprehensive list of issues that were completed in the last
sprint-Additionally, they need to know:
• the story points associated with each completed issue
• the issue type of each completed issue
• the description of each issue that has not been completed
Which report or gadget provides the required information?

Accepted Answer

B

Explanation: 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]

Question 10

An issue was created with the following attributes: • Issue type: Story • Priority: Blocker • Labels: Tools, DevOps • Reporter: A.Grant An excerpt of the board's swimlane configuration is shown. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Atlassian_ACP-610/page_8_img_1.jpg In which swimlane will the issue appear?

Accepted Answer

B

Explanation: The issue will appear in the Expedite swimlane, because it matches the query priority = Blocker. Swimlanes are used to group issues on the board based on a common attribute, such as assignee, epic, or a custom query. The board’s swimlane configuration shows that the first swimlane is Expedite, which has the query priority = Blocker. This means that any issue with a blocker priority will be placed in this swimlane, regardless of its other attributes. The other swimlanes have different queries that do not match the issue’s attributes, such as type, labels, or reporter. Therefore, the issue will not appear in those swimlanes. The last swimlane is Everything Else, which is the default swimlane for any issue that does not match any of the previous queries. However, since the issue matches the Expedite query, it will not fall into this swimlane either. Hence, the correct answer is B. Reference: [Configuring swimlanes], [Using swimlanes]

Question 11

You need to find all issues that were not competed in some past sprint, and that are now part of an active sprint. Identify two functions that you need to use in your JQL query. (Choose two.)

Accepted Answer

A, E

Explanation: The two functions that are needed to use in the JQL query to find all issues that were not completed in some past sprint, and that are now part of an active sprint are closedSprints() and openSprints(). The closedSprints() function returns all issues that are assigned to a completed sprint. The openSprints() function returns all issues that are assigned to an incomplete sprint. By combining these two functions with the NOT operator, we can filter out the issues that belong to both a completed sprint and an incomplete sprint, and only get the issues that were not completed in some past sprint, and that are now part of an active sprint. For example, the JQL query could be: project = XYZ AND issuekey NOT IN (closedSprints() AND openSprints()) This query will return all issues in project XYZ that are not in both a closed sprint and an open sprint, meaning they are either in a closed sprint only or an open sprint only. Since we are looking for issues that are now part of an active sprint, we can assume they are in an open sprint only. Reference: Advanced search reference - JQL functions, Modifying closedSprints() to return previous two Sprints, JQL - Explanation of what closedSprints() does

Question 12

Analyze the Epic Report shown. https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/Atlassian_ACP-610/page_16_img_1.jpg Identify why the epic completion date is hard to predict.

Accepted Answer

D

Explanation: 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’s average 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. Reference: Managing Jira Projects Data Center and Server: Certification Bundle, Epic Report

Question 13

You are reviewing the Velocity Chart for your team and notice that they completed more story points
than they committed in their last sprint. You are definitely the only person who can add issues to
sprints in your project. How did your learn complete more story points than they committed?

Accepted Answer

C

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

Question 14

You want to remove some epics from your personal Scrum board, without impacting any other boards. Identify the correct solution.

Accepted Answer

D

Explanation: :

Question 15

The head of customer service wants to identity potential bottlenecks in the support workflow of her teams in the last three months. Which report provides this information?

Accepted Answer

C

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

Free Atlassian ACP-610 Actual Exam Questions