Atlassian ACP-610 Online Practice Questions and Exam Preparation

Atlassian ACP-610 Online Questions & Answers

• Question 41:

  All projects use only a single simplified workflow which has three statuses:

  1.

  Open

  2.

  In Progress

  3.

  Closed

  Each status allows all statuses to transition to it

  You need to identify oil issues that were in the Closed status at some point in their lifecycle.

  Select the correct JQL query.

  A. status CHANGED FROM in Progress" TO Closed
  B. status WAS Closed
  C. status = Closed OR (status WAS Closed AND status - Open)
  D. status CHANGED TO Open
  B. status WAS Closed

  ---

  Explanation/Reference:

  The correct JQL query to find all issues that were in the Closed status at some point in their lifecycle is: status WAS Closed. This query uses the WAS operator to check the previous values of the status field. The other options are incorrect because they either use invalid syntax, such as CHANGED FROM or -, or they do not capture all the issues that were ever closed, such as status = Closed or status CHANGED TO Open. For more information on JQL syntax and operators, see Advanced searching - operators reference and Advanced searching - fields reference. References: Advanced searching - operators reference, Advanced searching - fields reference

• Question 42:

  Kim needs a single dashboard gadget that displays the following information for issues in her project:

  1.

  the total count of all issues

  2.

  the total count of each issue type

  3.

  the distribution of each issue type as a percentage

  4.

  a graphical chart display of that percentage

  Which gadget meets this need?

  A. Heat Map
  B. Two Dimensional Filter Statistics
  C. Filter Results
  D. Issues in progress
  E. Issue Statistics
  E. Issue Statistics

  ---

  Explanation/Reference:

  The gadget that meets Kim's need is the Issue Statistics gadget. This gadget displays the collection of issues returned from a filter, broken down by a field. Kim can configure the gadget to use her project as the filter, and the issue type as the field. The gadget will then show the following information for issues in her project: the total count of all issues the total count of each issue type the distribution of each issue type as a percentage a graphical chart display of that percentage The other gadgets are not suitable because: The Heat Map gadget displays issues from a project or filter, grouped by a statistic type, in a heat map format. Issues can be grouped by any statistic type (e.g. Status, Priority, Assignee, etc). However, this gadget does not show the total count of all issues, nor the distribution of each issue type as a percentage. The Two Dimensional Filter Statistics gadget displays issues from a filter in a table format, where each cell shows the number of issues for a given combination of two statistics types (e.g. Status vs Priority, Assignee vs Issue Type, etc). This gadget does not show the total count of all issues, nor a graphical chart display of that percentage. The Filter Results gadget displays the results of an issue filter on the dashboard. This gadget does not show any summary or breakdown of the issues by any field, nor a graphical chart display of that percentage. The Issues in Progress gadget displays all issues that are in progress and assigned to the user viewing the dashboard. This gadget does not show any information about other issues or issue types in the project, nor a graphical chart display of that percentage. References: Use dashboard gadgets, Gadgets for Jira applications

• Question 43:

  Depending on the project configuration, a project administrator might be able to perform some tasks, instead of escalating them to the Jira administrator. Identic one such task.

  A. Remove Watchers from project notifications.
  B. Remove a priority value used by the project.
  C. Update permissions for a project user.
  D. Limit who can bulk edit project issues.
  A. Remove Watchers from project notifications.

  ---

  Explanation/Reference:

  A project administrator can remove watchers from project notifications, if they have the Manage Watchers permission. This is a task that does not require Jira administrator access, and can be done by the project administrator from the issue view. Removing a priority value used by the project, updating permissions for a project user, and limiting who can bulk edit project issues are all tasks that require Jira administrator access, and cannot be done by the project administrator. References: Managing watchers, Managing Jira Projects Data Center and Server: Certification Bundle

• Question 44:

  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
  B. create a new tab
  E. remove a field

  ---

  Explanation/Reference:

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

  All stories in your project are linked to epics within the same project. Using a bulk operation, you moved some stories to another project. What happens to the epics?

  A. Epics and epic links are moved automatically.
  B. Epics and epic links are unaffected
  C. Epics are moved automatically but epic links are lost
  D. Epics are unaffected but epic links are lost.
  C. Epics are moved automatically but epic links are lost

  ---

  Explanation/Reference:

  Epics are moved automatically but epic links are lost when stories are moved to another project using a bulk operation. This is because epics are a type of issue, and issues can be moved across projects. However, epic links are a type of issue link, and issue links cannot be moved across projects. Therefore, the stories will lose their epic links after the move, and the epics will remain in the original project. References: [Moving multiple issues], [Managing Jira Projects Data Center and Server: Certification Bundle]

• Question 46:

  Your team has been completing work on a fully estimated epic in each of the last four sprints.

  Your product owner wants you to predict how many additional sprints will be needed to complete it.

  Which single report can provide the information?

  A. Epic Burndown
  B. Sprint Report
  C. Release Burndown
  D. Epic Report
  A. Epic Burndown

  ---

  Explanation/Reference:

  An epic burndown chart shows the progress towards completing an epic over time. It is useful for tracking how much work is left to be done and predicting when it will be completed. The epic burndown chart is based on the estimation statistic

  that is configured for the board (either story points or issue count) and shows the total amount of work remaining in the epic at the end of each sprint. You can use this chart to estimate how many additional sprints will be needed to complete

  an epic. References: :

  https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-epic- burndown-chart/

• Question 47:

  A shareddashboard displays a gadget thatis based on a shared filter.

  Currently, each person who views the gadget sees counts of all the issues in a project by status.

  The team's requirement is that each person who views the gadget will see counts of only their assigned issues by status.

  What must you do in order to meet this requirement?

  A. Configure the 'Who can view this filter" setting.
  B. Reconfigure the dashboard viewers.
  C. Use the currentUser0JQL function in the filter.
  D. Replace it with the "Assigned to Me" gadget
  E. Modify the Assignable User permission.
  C. Use the currentUser0JQL function in the filter.

  ---

  Explanation/Reference:

  The best way to meet the team's requirement is to use the currentUser() JQL function in the filter. This function returns the current user who is viewing the gadget, and can be used to filter issues by assignee. For example, if the filter is "project = ABC and assignee = currentUser()", then each person who views the gadget will see counts of only their assigned issues by status.This way, you do not need to reconfigure the dashboard viewers or modify the Assignable User permission, which are global settings that affect all users. You also do not need to replace it with the "Assigned to Me" gadget, which does not show counts by status. Configuring the "Who can view this filter" setting does not affect the results of the filter, but only its visibility. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Advanced searching - functions reference | Jira Software Cloud]

• Question 48:

  You need a field that:

  1.

  allows different options in different projects

  2.

  allows options to be disabled where necessary

  3.

  allows only a single value

  4.

  allows a default value to be configured

  Which field meets these requirements?

  A. Select List (single choice)
  B. Checkboxes
  C. Component/s
  D. Labels
  A. Select List (single choice)

  ---

  Explanation/Reference:

  A select list (single choice) field meets the requirements because it allows different options in different projects, allows options to be disabled where necessary, allows only a single value, and allows a default value to be configured. A select list (single choice) field is a custom field that lets the user select one option from a list of predefined values. The values can be different for each project and can be enabled or disabled as needed. The field can also have a default value that is automatically selected when creating an issue12 References:

  1: What are custom fields? | Jira Software Cloud | Atlassian Support

  2: Configuring a custom field | Jira Software Cloud | Atlassian Support

• Question 49:

  The team requests that you update the name of your project. What impact will this have on Jira?

  A. The URL for issues will change.
  B. The project key will change.
  C. Issue filters may need to be updated.
  D. Issue search will not find issues from that project until Jira is re indexed.
  C. Issue filters may need to be updated.

  ---

  Explanation/Reference:

  Updating the name of your project will not affect the URL for issues, as they are based on the project key, not the name. The project key will also remain unchanged unless you explicitly change it. Issue search will still find issues from that project regardless of the name change. However, issue filters may need to be updated if they use the project name as a criterion. Therefore, the correct answer is C. References: Editing a project's details, Changing the project key, Searching for issues using filters

• Question 50:

  Auditors group contains only two members; Adam and Eve.

  You need to create a quick filter that shows overdue issues assigned to either of them

  Which JQL query is always correct?

  A. duedate
  B. due - overdueQ AND assignee in membersOfC'auditors")
  C. duedate < startOfDay() AND assignee in (Adam, Eve)
  D. due
  E. due < - "0" AND assignee - Adam OR assignee - Eve
  C. duedate < startOfDay() AND assignee in (Adam, Eve)

  ---

  Explanation/Reference:

  This JQL query is always correct because it uses the duedate field, which is a date picker that stores a date value without a time component, and the startOfDay() function, which returns the start of the current day (i.e., midnight). This query will return all issues that have a due date before today and are assigned to either Adam or Eve. The other queries are either incorrect or unreliable because they use different fields or functions that may not work as expected. For example, the due field is a date time picker that stores both a date and a time value, and the currentLogin() function returns the date and time of the current user's last login, which may vary depending on the user and their timezone. References: : https:// support.atlassian.com/jira-software- cloud/docs/advanced-search-reference-jql-fields/#Advancedsearchingfieldsreference- DuedateDuedate https://support.atlassian.com/jira-software-cloud/docs/advanced-search- reference-jql-functions/ #Advancedsearchingfunctionsreference-startOfDaystartOfDay