Atlassian Atlassian Certifications ACP-610 Questions & Answers

• Question 41:

  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

  Correct Answer: B

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

  Bob can see only 20 out of 50 issues in a particular scrum project.

  Browse Projects permission is granted to a single group. What does Bob need to see all the issues?

  A. project permission

  B. security level access

  C. global permission

  D. board access

  Correct Answer: B

  Bob needs security level access to see all the issues in the scrum project. Security levels are a way of restricting the visibility of certain issues within a project to specific users or groups. If Bob does not have the appropriate security level for some issues, he will not be able to see them. Browse Projects permission alone is not enough to see all the issues in a project that hassecurity levels configured. Project permission, global permission, and board access are not related to issue visibility within a project. References: Configuring issue-level security, Managing Jira Projects Data Center and Server: Certification Bundle

• Question 43:

  Which statement is definitely true about sub-tasks being used on a Scrurn board?

  A. Sub-task estimations are rolled up and displayed as the Original Estimate on the parent card.

  B. Sub-tasks can only be created by board administrators

  C. Sub-tasks can be displayed as cards in the Active sprints view.

  D. Sub-tasks can be displayed as cards in the Backlog view.

  E. Sub-tasks will automatically get resolved when the parent is moved to the Done column.

  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]

• Question 44:

  The release manager is requesting a list of all issues included in a particular sprint. Which report will provide this information?

  A. Control Chart

  B. Release Burndown

  C. Version Report

  D. Sprint Report

  E. Average Age Report

  Correct Answer: D

  A Sprint Report is the best report to provide a list of all issues included in a particular 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 release manager can easily view the list of incomplete issues in the Issue Navigator by clicking on the View in Issue Navigator link at the bottom of the report. 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 45:

  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.

  Correct Answer: C

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

  Quang is a project administrator. He added several fields to his project screen. All team members have Edit Issues permission in this project. Which field can definitely be set allproject team member-."1

  A. Attachment

  B. Assignee

  C. Fix Version/s

  D. Labels

  E. Issue Type

  Correct Answer: D

  The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how toconfigure fields in Jira, see Configuring fields and screens. References: Configuring fields and screens

• Question 47:

  A team currently uses a single project to track both features and tasks. They will be adopting aqile practices, as follows:

  1.

  Features will be developed during three week iterations.

  2.

  Tasks will be handled based on priority and rank and released incrementally as needed.

  they want to use agile boards with minimal disruption to their current configuration. Which solution will meet their requirements?

  A. a Kanban board in the current project with separate swimlanes per issue type

  B. two Scrum boards for the current project, one for each issue type

  C. a Scrum board in the current project with two quick fillers to show each issue type separately

  D. a second project for tasks with a shared configuration and separate boards per project

  E. a Kanban board for tasks and a Scrum board for features in the current project

  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]

• Question 48:

  Project DEV was just created and has zero issues. It uses the simplified workflow that is not shared.

  You are a project administrator in DEV.

  Which workflow change im.si definitely he escalated to a Jira administrator?

  A. remove the in Progress status

  B. update the Priority field during a transition

  C. add two existing statuses

  D. delete a Global transition

  E. change the initial status of the workflow

  Correct Answer: D

  A global transition is a transition that can be triggered from any status in the workflow. Deleting a global transition may affect the workflow logic and the ability to move issues between statuses. Therefore, only a Jira administrator can delete a global transition. The other actions can be performed by a project administrator in a simplified workflow that is not shared. References: : https://support.atlassian.com/jira-software-cloud/docs/what- are-workflows/ https://support.atlassian.com/ jira-software-cloud/docs/configure-a-simplified- workflow/

• Question 49:

  A project administrator wantsto 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.}

  A. create a new field

  B. create a new tab

  C. set a default value for a field

  D. make a field required

  E. remove a field

  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/

• Question 50:

  Jon can already see issues in a particular project. But he also needs to:

  1.

  work on setting Due Date on issues

  2.

  transition issues from the Resolved column to the Closed column

  His project was created using the Scrum project template and the simplified workflow has not been modified. Which three additional permissions does he definitely need? (Choose three.)

  A. Work On Issues

  B. Browse Projects

  C. Close Issues

  D. Transition Issues

  E. Schedule Issues

  Correct Answer: CDE

  To perform the tasks that Jon needs, he requires three additional permissions: Close Issues, Transition Issues, and Schedule Issues. The Close Issues permission allows Jon to transition issues from the Resolved column to the Closed column on the Scrum board. The Transition Issues permission allows Jon to move issues through any workflow transition on the Scrum board. The Schedule Issues permission allows Jon to set or edit the Due Date of an issue. The other permissions are not additional or necessary for Jon's tasks. The Work On Issues permission allows Jon to log work on an issue, but not to set or edit the Due Date. The Browse Projects permission is already granted to Jon, since he can see the issues in the project. For more information on how to manage project permissions, see Manage project permissions and Understand project permissions and roles. References: Manage project permissions, Understand project permissions and roles