ACP-610 Sample Questions Answers

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/

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

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

The solution that meets this requirement is to update the board filter and add: AND (labels != daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from the board filter, which determines which issues are displayed on the board. It will also include issues that have no labels at all, as some issues in your project may not have labels. The other solutions do not meet this requirement, as they either do not exclude issues with daily_business label, or exclude issues with no labels. References: Configuring filters, Advanced searching - operators reference

A possible reason why Sam can only see some of the issues on the project’s Kanban board but sees all of them in the issue search is that the column mapping of the board does not include all the statuses of the different workflows used by the issue types. Column mapping determines which statuses are mapped to which columns on a board, and only issues with mapped statuses are displayed on the board. If an issue type has a workflow with a status that is not mapped to any column, then it will not appear on the board. Board permissions, issue-level security, and workflow conditions do not affect the visibility of issues on a board, as they apply to both the board and the issue search. Therefore, the correct answer is B. References: [Configuring columns], [Configuring workflows]

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

 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 …

The project role that Clare needs is Assigners. This is because the Assigners role has been granted two permissions that Clare needs: Browse Projects and Assign Issues. The Browse Projects permission allows Clare to see the project and its issues, and the Assign Issues permission allows Clare to re-assign issues to subject matter experts. The other roles do not have both of these permissions. For example, the Viewers role only has the Browse Projects permission, but not the Assign Issues permission. The Administrators role has both permissions, but also has other permissions that Clare does not need, such as Administer Projects and Delete Issues. The Assignables role only has the Assignable User permission, which allows users to be assigned issues, but not to assign issues to others. The Workers role only has the Work On Issues permission, which allows users to log work on issues, but not to assign issues to others. The Editors role only has the Edit Issues permission, which allows users to modify issue details, but not to assign issues to others. For more information on how project permissions and roles work, see Understand project permissions and roles and Manage project permissions. References: Manage project permissions, Understand project permissions and roles

The Cumulative Flow Diagram is the report that provides the information that the head of customer service wants. The Cumulative Flow Diagram is a tool that visualizes the quantity and distribution of work items along different stages of a process. The report shows how many work items are in each stage at any given time, and how they flow from one stage to another. The report can help identify potential bottlenecks in the support 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 “Waiting for Customer” stage, it may indicate that the customers are not responding quickly enough or that the support team is not following up effectively. The report can also help monitor the overall progress and performance of the support teams by showing the total number of work items created, resolved, and remaining over time. References: Managing Jira Projects Data Center and Server: Certification Bundle, Cumulative Flow Diagram

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

The best configuration to meet the team’s need of displaying keywords prominently when viewing all cards on a board is card layout. Card layout allows you to customize what fields are shown on each card on a board, and you can choose to show any custom field of type Labels on the cards. Swimlanes are used to group issues into horizontal lanes based on certain criteria, such as assignee, priority, or query, but they do not show labels on each card. Card colours are used to highlight issues based on certain attributes, such as issue type, priority, or query, but they do not show labels on each card either. Issue detail view is used to show more information about an issue when you select it on a board, but it does not affect how cards are displayed on the board. Therefore, the correct answer is A. References: [Configuring card layout], [Configuring swimlanes], [Configuring card colours], [Using boards]

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]

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

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/

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]

Jira attachments are files that users can attach to issues to share information with their team. Users can search for issues that contain attachments by using the attachments field in the advanced search. For example, attachments is not EMPTY will return all issues that have at least one attachment. Therefore, option A is true.

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]