Atlassian ACP-610 Online Practice Questions and Exam Preparation

Atlassian ACP-610 Online Questions & Answers

• Question 31:

  You need to assign team members to view code commits in the DEV project. An excerpt of the DEV permission scheme is shown.

  

  Which two project roles must they be granted? (Choose two.)

  A. Users
  B. Administrators
  C. Developers
  D. Sprinters
  E. Managers
  B. Administrators
  C. Developers

  ---

  Explanation/Reference:

  Two project roles that must be granted to view code commits in the DEV project are:

  Developers

  Administrators

  According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role

  (Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.

  The other options are not correct because:

  Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project. Sprinters do not have the View Development Tools permission in the DEV permission scheme,

  so they cannot see code commits in the DEV project. Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

• Question 32:

  Gen prioritizes and triages support requests as soon as they come in. She now wants to use drag-and-drop to:

  1.

  quicklyassign and transition them to in Progress

  2.

  instantly associate them with Epics

  Which board view will meet these requirements?

  A. Scrum backlog
  B. Kanban board
  C. Kanban backlog
  D. Active sprints
  B. Kanban board

  ---

  Explanation/Reference:

  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]

• Question 33:

  You manage a Scrum project with two development teams.

  Issues are associated with each team using a custom field called Jean.

  Parallel sprints have been disabled.

  Which setup will provide each team with an individual Burndown Chart?

  A. a single Scrum board with quick filters
  B. a single Scrum board using the Team field as the Estimation Statistic
  C. two Scrum boards using the Team field as the Estimation Statistic
  D. two Scrum boards using the Team field in their board filters
  D. two Scrum boards using the Team field in their board filters

  ---

  Explanation/Reference:

  If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that

  shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and

  thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D. References:

  [Creating a board], [Configuring filters], [Viewing the Burndown Chart]

• Question 34:

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

  A. Exclude them via a quick filter.
  B. Mark them as Done via the Epics panel
  C. Exclude them via the board filter
  D. Exclude them via the board sub filter.
  E. Transition them into an unmapped status.
  D. Exclude them via the board sub filter.

• Question 35:

  All projects use a shared permission scheme.

  The Browse Projects permission needs to be updated so that projectadministratorscan manage access to their own projects.

  What entry must be added to the Browse Projects permission?

  A. Application Access
  B. Project Lead
  C. Single User Project Role
  D. Group
  B. Project Lead

• Question 36:

  Analyze the component configuration of a project as shown.

  

  Dave creates an issue and wants to use the auto-assignment feature of Jira. Which statement is definitely correct?

  A. If UX is selected, the issue will be assigned to admin.
  B. If Login and Signoff are selected, the issue will be assigned to Project admin.
  C. If Signoff is selected, the issue will be assigned to Project admin.
  D. If Test is selected, the issue will be assigned to Project lead.
  C. If Signoff is selected, the issue will be assigned to Project admin.

  ---

  Explanation/Reference:

  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.

• Question 37:

  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
  D. Labels

  ---

  Explanation/Reference:

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

  Bethany knows the URL of an issue that she wants to restore in a particular project.

  What are the minimum two permissions that she needs to restore the issue? (Choose two.}

  A. Restore Issues
  B. Browse Project Archive
  C. Move Issues
  D. Edit Issues
  E. Browse Projects
  A. Restore Issues
  B. Browse Project Archive

  ---

  Explanation/Reference:

  To restore an issue from the project archive, Bethany needs two permissions: Restore Issues and Browse Project Archive. The Restore Issues permission allows Bethany to restore issues that have been archived in a project. The Browse Project Archive permission allows Bethany to view the archived issues in a project. Without these permissions, Bethany will not be able to access or restore the archived issue, even if she knows the URL. The other permissions are not relevant for restoring an issue. The Move Issues permission allows Bethany to move issues from one project to another. The Edit Issues permission allows Bethany to modify the details of an issue. The Browse Projects permission allows Bethany to see the project and its issues, but not the archived ones. For more information on how to archive and restore issues, see Archive and restore issues and Manage project permissions. References: Archive and restore issues, Manage project permissions

• Question 39:

  Your team works in a project that uses only one workflow, a simplified workflow. The configuration of the corresponding Kanban board is shown:

  

  Which statement is definitely true?

  A. Bugs can be dragged from "In Progress" to "In Test" on this board.
  B. All team members can transition issues from Backlog to In Test.
  C. Issues can be transitioned freely between all workflow statuses
  D. A resolution will be set once an issue is dragged to Done
  A. Bugs can be dragged from "In Progress" to "In Test" on this board.

  ---

  Explanation/Reference:

  The statement that is definitely true is that bugs can be dragged from "In Progress" to "In Test" on this board. This is because the board configuration shown in the image has two columns: "In Progress" and "Done". The "In Progress" column has three statuses mapped to it: "To Do", "InProgress", and "In Test". The "Done" column has one status mapped to it: "Done". Therefore, issues can be moved from one status to another within the same column by dragging them on the board. However, issues cannot be moved from one column to another by dragging them on the board, as this would require a workflow transition that is not available in a simplified workflow. A simplified workflow is a default workflow that allows any user with the Edit Issues permission to add or remove statuses on the fly. To move an issue from one column to another, you need to use the workflow button on the issue detail view and select a transition that matches the status of the destination column. References: Configuring columns, Using a simplified workflow

• Question 40:

  A Scrum board contains issues from a single project. An extract of the project's permission scheme is shown.

  

  Who can definitely see the Scrurn board and rank issues?

  A. any member of Developers role with Jira Software application access
  B. any logged in user
  C. member of both Developers role and Product Owner role
  D. any member of Developers role
  B. any logged in user

  ---

  Explanation/Reference:

  The only users who can definitely see the Scrum board and rank issues are the members of the Developers role with Jira Software application access. This is because the Browse Projects permission, which allows users to see the project and its issues, is granted to the Developers role, and the Schedule Issues permission, which allows users to rank issues on a Scrum board,is granted to any logged in user who has Jira Software application access. The other options are incorrect because they either do not have Jira Software application access, which is required for both permissions, or they do not belong to the Developers role, which is required for the Browse Projects permission. For more information on project permissions and roles, see Understand project permissions and roles and Manage project permissions. References: Manage project permissions, Understand project permissions and roles