Atlassian ACP-610 Online Practice Questions and Exam Preparation

Atlassian ACP-610 Online Questions & Answers

• Question 51:

  Anu has access to the DEV project and its Scrum board.

  She also needs to plan, start, and complete sprints, and to edit sprint goals and dates

  Where must Anu be added onto?

  A. the group that has Schedule Issues permission
  B. the list of board administrators for the Scrum board
  C. a project role that has Start/Complete Sprints permission
  D. a project role that has Manage Sprints permission
  E. a project role that has Administer Projects permission
  D. a project role that has Manage Sprints permission

  ---

  Explanation/Reference:

  Anu needs to be added to a project role that has Manage Sprints permission. This permission allows Anu to plan, start, and complete sprints, as well as edit sprint goals and dates on a Scrum board. The other options are not correct for Anu's needs. The group that has Schedule Issues permission does not allow Anu to manage sprints, but only to rank issues on a Scrum board. The list of board administrators for the Scrum board does not grant Anu any permissions, but only allows Anu to configure the board settings. A project role that has Start/Complete Sprints permission does not allow Anu to edit sprint goals and dates, but only to start and complete sprints on a Scrum board. A project role that has Administer Projects permission does not allow Anu to manage sprints, but only to administer the project settings. For more information on how to manage sprints on a Scrum board, see Manage sprints and Manage project permissions. References: Manage sprints, Manage project permissions

• Question 52:

  Your project will be audited. You need to grant specific permissions to the auditors through a project role.

  The auditors do not have any Jira global permissions granted.

  Which two permissions can be granted through a project role? (Choose two.)

  A. see issues with a security level
  B. see issues that have been archived
  C. share a dashboard with other auditors
  D. subscribe other auditors to a search result
  E. use bulk change to update seven issues
  A. see issues with a security level
  C. share a dashboard with other auditors

  ---

  Explanation/Reference:

  https://support.atlassian.com/jira-software-cloud/docs/understand-project- permissions-and-roles/ The two permissions that can be granted through a project role are:

  A. see issues with a security level

  C. share a dashboard with other auditors

  These permissions are related to the project level and can be configured by the project administrator using the permission scheme or the dashboard settings.According to the documentation1, a project role can be granted the following

  permissions:

  Browse Projects: View the project and its issues.

  Create Issues: Create new issues.

  Edit Issues: Edit existing issues.

  Schedule Issues: Edit the Due Date of an issue, or rank issues on a Scrum board. Move Issues: Move issues from one project to another, or change the issue type.

  Assignable User: Be assigned issues.

  Assign Issues: Assign issues to other users.

  Resolve Issues: Resolve or reopen issues, or set a resolution when closing issues.

  Close Issues: Close issues.

  Modify Reporter: Modify the Reporter field of an issue.

  Delete Issues: Delete issues from the project.

  Link Issues: Link issues to each other, or create sub-tasks under an issue. Set Issue Security: Set a security level on an issue to control who can see it. View Voters and Watchers: View the list of voters and watchers for an issue. Manage

  Watchers: Add or remove watchers for an issue. View Read-Only Workflow: View the workflow diagram for an issue, but not edit it. Manage Sprints: Start, complete, or edit sprints on a Scrum board. Additionally, a project role can be given

  access to share a dashboard with other users or groups2. To do this, the project administrator needs to:

  Go to Dashboards > View all dashboards

  Find the dashboard to share and click > Share

  Click Edit permissions

  Under Add Permissions, select Group or Project Role Choose the auditors project role from the dropdown menu Click Add

  The other options are not correct because:

  B. see issues that have been archived is not a permission that can be granted through a project role.Archived issues are hidden from all users except Jira administrators3. To view archived issues, the auditors would need to have the

  Administer Jira global permission, which is not related to project roles. D. subscribe other auditors to a search result is not a permission that can be granted through a project role.Subscribing other users to a search result is a feature that

  requires the Manage Group Filter Subscriptions global permission4. This permission is not related to project roles and can only be granted by Jira administrators to individual users or groups.

  E. use bulk change to update seven issues is not a permission that can be granted through a project role.Bulk change is an operation that requires the Bulk Change global permission5. This permission is not related to project roles and can

  only be granted by Jira administrators to individual users or groups.

• Question 53:

  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
  B. security level access

  ---

  Explanation/Reference:

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

  Which statementis true about Jira attachments?

  A. Users can search for issues that contain attachments
  B. Users need Work On Issues permission to remove attachments.
  C. Users need Edit Issues permission to add attachments.
  D. Project administrators can disable attachments through project settings.
  A. Users can search for issues that contain attachments

• Question 55:

  Review the Version Report: A. The release date that has been added to this version should be reconsidered.

  

  B. More than 20 story points were burned when this chart was reviewed in July 2015.
  C. Only three issues have been completed in the version, so a predicted end date is not possible.
  D. The team should use time-based estimation, not story points.
  E. There are too many unestimated issues in this version, so any predictions are inaccurate.
  B. More than 20 story points were burned when this chart was reviewed in July 2015.

• Question 56:

  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.)

  A. closedSprints()
  B. futures prints()
  C. completed()
  D. remaming()
  E. openSprints()
  A. closedSprints()
  E. openSprints()

  ---

  Explanation/Reference:

  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 thatare 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. References: Advanced search reference - JQL functions, Modifying closedSprints() to return previous two Sprints, JQL

  -of what closedSprints() does

• Question 57:

  A Jira administrator just created a new project based on the "Task management" project template. Which Jira feature is enabled in this project by default?

  A. Epic issue type
  B. ranking of standard issue types
  C. Issue analysis reports
  D. Release Hub
  B. ranking of standard issue types

  ---

  Explanation/Reference:

  The "Task management" project template is designed for managing simple tasks and tracking progress. By default, this template enables ranking of standard issue types, which allows you to order issues by priority on a board. The other features mentioned in the options are not enabled by default in this template. Therefore, the correct answer is B. References: Creating a project, Ranking an issue

• Question 58:

  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
  C. Close Issues
  D. Transition Issues
  E. Schedule Issues

  ---

  Explanation/Reference:

  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

• Question 59:

  You want to update a workflow that is not shared.

  You are a project administrator and "Extended project administration" is enabled.

  Which two actions can you complete? (Choose two.)

  A. Add a field to a transition screen.
  B. Add a condition to limit who can approve issues,
  C. Add new transitions to the workflow.
  D. Delete transitions from the workflow.
  E. Delete the Review status from Jira
  C. Add new transitions to the workflow.
  D. Delete transitions from the workflow.

• Question 60:

  Your company recently created an internal IT project to track hardware requests. View the project configuration below: Project: Hardware request Project lead: Allen Frank Default Assignee: Project lead

  

  To test thetriaging process you create the first issue in the project and select the Macbook 13" component. You don t update the assignee field and leave it to the default value of Automatic.

  Based on the current configuration, which value will the assignee field show after creating the test issue?

  A. Allen Frank
  B. Mac Taylor
  C. Automatic
  D. Louise Lin
  E. Unaligned
  B. Mac Taylor

  ---

  Explanation/Reference:

  Based on the current configuration, the assignee field will show Mac Taylor after creating the test issue. This is because the Macbook 13" component has Mac Taylor as the component lead and the component/s field has been configured to override the project's default assignee when using a certain component. Therefore, when creating an issue with the Macbook 13" component, the assignee field will automatically be set to Mac Taylor, regardless of the default assignee of the project or the value of the assignee field before creating the issue34 References:

  3: What are components? | Jira Software Cloud | Atlassian Support

  4: How to enable and edit component/s , affects Version/s and fix version ...