Atlassian ACP-610 Online Practice Questions and Exam Preparation

Atlassian ACP-610 Online Questions & Answers

• Question 61:

  You are a project administrator of DEV.Omar is a Jira administrator. Identify two project settings that Omar can update in DEV but you cannot. (Choose two.)

  A. Notification scheme
  B. Project shortcuts
  C. Key
  D. Description
  E. Name
  F. Versions
  A. Notification scheme
  C. Key

  ---

  Explanation/Reference:

  As a project administrator of DEV, you can update some project settings such as project shortcuts, description, name, and versions. However, you cannot update the notification scheme or the key of the project, as these are global settings that require Jira administratorpermissions. Therefore, the correct answer is A and C. References: Managing project permissions, Managing project notifications, Changing the project key

• Question 62:

  Development team A is consistently overestimating the work they can complete per sprint. They want to be able to compare work committed and work completed in sprints over time. Which single report provides this information?

  A. Control Chart
  B. Sprint Report
  C. Cumulative Flow Diagram
  D. Created vs Resolved Issues Report
  E. Velocity Chart
  E. Velocity Chart

  ---

  Explanation/Reference:

  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

• Question 63:

  The extract of a permission scheme for a project is shown below.

  

  Clare is joining your team and needs to:

  1.

  analyze incoming requests with her initials tagged to a label

  2.

  re-assign requests to subject matter experts

  Which project role does Clare need?

  A. Assigners
  B. Viewers
  C. Administrators
  D. Assignables
  E. Workers
  F. Editors
  A. Assigners

  ---

  Explanation/Reference:

  The project role that Clare needs is Assigners. This is because the Assigners role has been granted two permissions that Clare needs: Browse Projects and Assign Issues. The Browse Projects permission allows Clare to see the project and its issues, and the Assign Issues permission allows Clare to re-assign issues to subject matter experts. The other roles do not have both of these permissions. For example, the Viewers role only has the Browse Projects permission, but not the Assign Issues permission. The Administrators role has both permissions, but also has other permissions that Clare does not need, such as Administer Projects and Delete Issues. The Assignables role only has the Assignable User permission, which allows users to be assigned issues, but not to assign issues to others. The Workers role only has the Work On Issues permission, which allows users to log work on issues, but not to assign issues to others. The Editors role only has the Edit Issues permission, which allows users to modify issue details, but not to assign issues to others. For more information on how project permissions and roles work, see Understand project permissions and roles and Manage project permissions. References: Manage project permissions, Understand project permissions and roles

• Question 64:

  The `'Open issuesfilter 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?

  A. board filter query
  B. issue type scheme
  C. board filter shares
  D. swim lanes
  E. board sub-filter
  A. board filter query

• Question 65:

  A scrum team asks you for a single comprehensive list of issues that were completed in the last sprint-Additionally, they need to know:

  1.

  the story points associated with each completed issue

  2.

  the issue type of each completed issue

  3.

  the description of each issue that has not been completed

  Which report or gadget provides the required information?

  A. Burndown Chart report
  B. Sprint Report
  C. Created vs Resolved
  D. Chart gadget
  E. Filter Results gadget
  F. Sprint Health Gadget
  B. Sprint Report

  ---

  Explanation/Reference:

  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]

• Question 66:

  You just started working as a scrum master in the Engine team.

  The first thing you do is to analyze the Velocity Chart of the team's scrumboard as shown

  

  A. Issues not completed in Combo Sprint 3 were completed in Combo Sprint 4.
  B. Combo Sprint 1 has been deleted after it was completed.
  C. There was a scope change during Combo Sprint 4.
  D. The team only completed 2 out of 6 Story Points in Combo Sprint 3.
  E. All issues in Combo Sprint 3 were estimated before the sprint was started.
  C. There was a scope change during Combo Sprint 4.

  ---

  Explanation/Reference:

  The Velocity Chart shows the amount of work completed by a team in each sprint. The green area represents the completed work, and the gray area represents the estimated work. The difference between the green and gray areas indicates a scope change, which means that issues were added or removed from the sprint after it started. In Combo Sprint 4, we can see that the green area is larger than the gray area, which means that more work was completed than estimated. This implies that some issues were added to the sprint after it started, or that some issues were re-estimated with higher values. Therefore, option C is correct. References: Velocity Chart, Managing Jira Projects Data Center and Server: Certification Bundle

• Question 67:

  Which statementis definitely true about priorities in Jira?

  A. Project administrators can re-order existing priorities in their projects.
  B. Project administrators can create new priorities in their projects.
  C. The same set of priorities is always available in each project.
  D. Jira administrators can create and update global priorities.
  D. Jira administrators can create and update global priorities.

  ---

  Explanation/Reference:

  Jira administrators can create and update global priorities, which are the default set of priorities available in each project. Project administrators cannot re-order, create, or update priorities in their projects, unless they have Jira administrator access. The same set of priorities is not always available in each project, as Jira administrators can configure priority schemes to assign different priorities to different projects. References: [Configuring priorities], [Managing Jira Projects Data Center and Server: Certification Bundle]

• Question 68:

  Your team uses Story Points for estimation and tracking.

  You performed several actions in the active sprint.

  Which two actions are reflected as scope change? (Choose two.)

  A. Added a fix version on a committed story.
  B. Estimated a story in the backlog.
  C. Dragged on estimated story from the backlog to the sprint.
  D. Modified the estimate value on a committed story.
  E. Added another 5ub-task to a committed story.
  F. Logged work on several committed stories.
  C. Dragged on estimated story from the backlog to the sprint.
  D. Modified the estimate value on a committed story.

  ---

  Explanation/Reference:

  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

• Question 69:

  Jon notices that an issue was created incorrectly in project A. He needs to move it to project B. Which permissions are required to complete that move?

  A. Move Issues. Transition Issues
  B. Administer Projects. Assign Issues
  C. Move Issues, Create Issues
  D. Administer Projects, Create Issues
  C. Move Issues, Create Issues

  ---

  Explanation/Reference:

  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]

• Question 70:

  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?

  A. The sprint was completed early.
  B. An epic with a story point estimate was completed during the sprint.
  C. Someone increased the story point value on an issue mid-sprint.
  D. A sub-task was in an unmapped status at the start of the sprint.
  E. A new sub-task was created drying the sprint
  C. Someone increased the story point value on an issue mid-sprint.

  ---

  Explanation/Reference:

  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