ACP-610 Practice Exam Questions with Answers Managing Jira Projects for Data Center and Server Certification

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

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.

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]

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

One difference between Scrum and Kanban boards is that only Scrum boards support selecting an estimation method. Estimation is a way of measuring how much work is required to complete an issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on managing the flow of work rather than planning sprints. References: Configuring estimation and tracking, Estimating an issue

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]

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/

Three versions will be available in the versions panel of the project backlog: epsilon, delta, and gamma. These are the three unreleased versions in the project, as shown in the image. The versions panel only shows unreleased versions, as they are used to plan and track the progress of upcoming releases. Released and archived versions are not shown in the versions panel, as they are considered completed and no longer relevant for planning purposes. References: [Working with versions], [Managing Jira Projects Data Center and Server: Certification Bundle]

The statement that is definitely true is that changes to the rank of integration issues on Jo’s board are reflected on Sam’s board. This is because ranking is a global attribute that affects how issues are ordered across projects and boards based on their relative priority. When Jo updates his Scrum board’s saved filter to include integration issues from Sam’s project, he can rank them along with his own issues on his board. These changes will also affect how these issues are ranked on Sam’s board, as they share the same rank field value. The other statements are not necessarily true or false, as they depend on other factors such as permissions, workflow configurations, or board settings. Therefore, the correct answer is B. References: [Ranking an issue], [Configuring filters]

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

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

 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 …

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

The Cumulative Flow Diagram is the report that provides the needed insight to see if frequent scope change mid-sprint is causing bottlenecks. The Cumulative Flow Diagram shows the quantity and distribution of work items along different stages of a process over time. The report can help identify potential bottlenecks in the workflow by showing where work items accumulate or stagnate over time. For example, if the report shows a sudden increase or a wide band of work items in the “In Progress” stage, it may indicate that the team is overloaded with work or facing some blockers. If the team often accepts new requests from outside groups during an active sprint, the report can show how this affects the flow of work and the completion of the sprint goal. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

Heat map

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.