Atlassian ACP-610 Practice Test - Questions Answers, Page 3

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.Reference:Creating a project,Ranking an issue

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.Reference:Editing a project's details,Changing the project key,Searching for issues using filters

When you move an epic between projects that share an issue type scheme, all standard issues in the epic are moved along with it. This means that any issue type that is not a sub-task or an epic will be moved to the new project. Sub-task issues in the epic will not be moved unless their parent issues are also in the epic. Story issues in the epic will be moved only if they are standard issue types, not sub-tasks. Issues linked to the epic through issue links will not be moved as they are not part of the epic hierarchy. Therefore, the correct answer is A.Reference:Moving an issue,Working with epics

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.Reference: [Working with sub-tasks], [Configuring columns]

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.Reference: [Configuring columns], [Configuring workflows]

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.Reference: [Configuring card layout], [Configuring swimlanes], [Configuring card colours], [Using boards]

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.Reference: [Ranking an issue], [Configuring filters]

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.Reference: [Creating a board], [Using a Scrum board], [Using a Kanban board]

To exclude the planned issues from the board but not from the reports, you need to use a board sub-filter. A board sub-filter is an additional JQL query that is applied to the board filter to further refine the issues displayed on the board. The sub-filter does not affect the reports, which are based on the board filter only. To hide issues in real time when users select multiple conditions, you need to use quick filters. Quick filters are buttons that allow users to dynamically change the view of the board by applying one or more JQL queries. Users can select or deselect quick filters to show or hide issues that match the criteria.Reference:Configuring filters,Configuring quick filters