Free ATLASSIAN ACP-610 Practice Exam with Questions & Answers

Sub-tasks are a type of issue that can be used to break down a parent issue into smaller and more manageable pieces. Sub-tasks can be displayed as cards in the Active sprints view of a Scrum board, which allows you to track their progress and status. However, sub-task estimations are not rolled up and displayed on the parent card, as they use a different field than the parent issue. Sub-tasks can be created by anyone who has the Create Issue permission in the project, not only by board administrators. Sub-tasks cannot be displayed as cards in the Backlog view, as they are only visible under their parent issues. Sub-tasks will not automatically get resolved when the parent is moved to the Done column, as they have their own workflow transitions and conditions. Therefore, the correct answer is C. References: [Working with sub-tasks], [Configuring columns]

 The Velocity Chart shows the amount of work completed by a team in each sprint. The green area represents the completed work, and the gray area represents the estimated work. The difference between the green and gray areas indicates a scope change, which means that issues were added or removed from the sprint after it started. In Combo Sprint 4, we can see that the green area is larger than the gray area, which means that more work was completed than estimated. This implies that some issues were added to the sprint after it started, or that some issues were re-estimated with higher values. Therefore, option C is correct. References: Velocity Chart, Managing Jira Projects Data Center and Server: Certification Bundle

• Savresh needs Assignable User permission. This permission determines which users can be assigned to issues in a project1. If Savresh does not have this permission, they will not be able to re-assign issues to themselves, even if they can create and assign issues to others.
• Testers need Assign Issues permission. This permission determines which users can assign issues to other users or to themselves1. If the Testers group does nothave this permission, they will not be able to re-assign issues to anyone, including Savresh.

A custom field is a field that is not part of the default set of Jira system fields. Creating a new custom field requires Jira administration permissions, so Max cannot perform action 1. However, adding an existing custom field to a transition screen does not require Jira administration permissions, as long as the screen is not shared with other projects or issue types. Therefore, Max can perform action 2 if he has the “Administer Projects” permission and the screen meets the prerequisites for editing. References: : https://support.atlassian.com/jira-software-cloud/docs/what-are-custom-fields/ https://support.atlassian.com/jira-software-cloud/docs/configure-screens/

The Version Report and the Sprint Health Gadget are two gadgets that can show the information that the product owner needs. The Version Report shows the progress of a version by comparing the estimated amount of work to the completed work. The report also shows a projected release date based on the team’s average velocity. The product owner can use this report to monitor the overall progress of the next release and determine if it will ship on time. The Sprint Health Gadget shows a snapshot of key sprint information such as time elapsed, percentage of scope change, sprint goal, and team members’ availability. The product owner can use this gadget to see how each scrum team is performing in their current sprint and identify any issues or risks. References: Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget

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 Velocity Chart is the best report to compare work committed and work completed in sprints over time. It shows the average amount of work that a team can complete in a sprint, based on the historical data of previous sprints. It also shows how much work was planned and how much was actually completed in each sprint. By looking at the Velocity Chart, a team can see if they are overestimating or underestimating their capacity, and adjust their planning accordingly. Therefore, option E is correct. References: Velocity Chart, Managing Jira Projects Data Center and Server: Certification Bundle

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/

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

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