ACP-610 ATLASSIAN Managing Jira Projects for Data Center and Server Certification Free Practice Exam Questions (2025 Updated)

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

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

If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D. References: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]

The report that can provide an instant progress overview of all fix versions across all projects is thePie Chart Report. This report allows you to create a pie chart based on any statistic type, such as Fix Version, Project, Issue Type, etc. You can use this report to compare the relative proportions of issues in different fix versions across different projects. For example, you can create a pie chart based on the Fix Version statistic type, and select all the projects that you are responsible for. This will show you how many issues are assigned to each fix version in each project, and what percentage they represent of the total issues. You can also filter the issues by status, priority, assignee, or any other criteria. This report can help you monitor the progress of your releases and identify any potential risks or delays.To generate a Pie Chart Report, follow these steps1:

Navigate to the project that you want to report on.

From the project sidebar, select Reports.

Select Pie Chart Report from the list of reports.

Select the statistic type that you want to base your pie chart on. In this case, select Fix Version.

Select the projects that you want to include in your report. You can select multiple projects by holding down the Ctrl key (Windows) or Command key (Mac) while clicking on the project names.

Optionally, select a filter to narrow down the issues that you want to include in your report. You can use an existing filter or create a new one.

Click View to generate the report.

You can also access the Pie Chart Report from your dashboard by adding the Jira Chart gadget2. This gadget allows you to display any Jira report on your dashboard.To add the Jira Chart gadget to your dashboard, follow these steps2:

Navigate to your dashboard and click Add gadget.

Search for Jira Chart and click Add gadget.

Configure the gadget settings as follows:

Select Pie Chart as the chart type.

Select the project or filter that you want to use as the data source.

Select Fix Version as the statistic type.

Optionally, select a series to further break down the data by another statistic type, such as Status or Priority.

Click Save.

You can also edit or delete the gadget at any time by clicking on the menu icon at the top right corner of the gadget.

The correct JQL query to find issues reported by either Paul or Tessa that are still unassigned is: Reporter IN (Paul, Tessa) AND Assignee IS EMPTY. This query uses the IN operator to specify a list of values for the Reporter field, and the IS EMPTY operator to check if the Assignee field has no value. The other options are incorrect because they use invalid syntax or operators, such as “-”, NULL, or Unassigned. For more information on JQL syntax and operators, see JQL operators and Use advanced search with Jira Query Language (JQL). References: JQL operators, Use advanced search with Jira Query Language (JQL)

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

Jira administrators can create and update global priorities, which are the default set of priorities available in each project. Project administrators cannot re-order, create, or update priorities in their projects, unless they have Jira administrator access. The same set of priorities is not always available in each project, as Jira administrators can configure priority schemes to assign different priorities to different projects. References: [Configuring priorities], [Managing Jira Projects Data Center and Server: Certification Bundle]

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 epic completion date is hard to predict because the team adds new stories throughout the epic. This means that the scope of the epic is not fixed and can change over time. The Epic Report shows the progress of an epic by comparing the estimated amount of work to the completed work. The report also shows a projected completion date based on the team’saverage velocity. However, if the team keeps adding new stories to the epic, the estimated amount of work will increase and the projected completion date will be pushed further. This makes it difficult to plan and deliver the epic within a certain timeframe. References: Managing Jira Projects Data Center and Server: Certification Bundle, Epic Report

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/

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 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 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]

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

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]

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

Based on the report shown, which is a Velocity Chart, the only statement that is definitely true about the team’s performance is that they sometimes commit more work than they can complete in an iteration. This can be seen by comparing the green bars (completed work) and the gray bars (estimated work) in each sprint. For example, in Sprint 4, the team committed 10 story points but only completed 8 story points. The other statements are not necessarily true based on the report alone. For example, the team may be estimating their work accurately, but facing other challenges or impediments that prevent them from completing their work on time. Or, the team may not be committing unestimated work to an iteration, but rather re-estimating some issues during the sprint. Or, scope change may not be affecting the team’s ability to complete work on time, but rather reflecting changes in priorities or requirements. Or, the team may be using sprint duration consistently, but varying the amount of work they commit to each sprint based on their capacity or velocity. For more information on how to interpret and use the Velocity Chart, see Velocity Chart. References: Velocity Chart