ACP-620 V1

Nina recently joined as a finance manager. Her team already has a few Jira projects running that is related to finance projects. She needs to create a new project using the same configurations as the other finance projects.

Below is the configuration she used to create the project.

What will happen to Nina’s Jira project (RMC) if the team that is managing the USC project changed their Jira configuration?
A . Any changes with the other team’s Jira project will automatically apply to Nina’s Jira project.
B. Nina has permission to accept the configuration changes if she needs them.
C. All answers are incorrect.
D. Nothing will happen. Jira will only apply the configuration changes at the initial Jira project creation.

View Answer

Answer: D

Explanation:

In Jira, when you create a project by sharing configurations with another project, only the configurations at the time of creation are shared. Any subsequent changes to the original project’s configurations won’t affect the project that was created with shared configurations. This allows project configurations to evolve independently over time, even if they started from a common point.

Which of the following are true about epic? (Choose two.)
A . An epic can have another epic. (Epic Link)
B. An epic cannot have its own issue screen.
C. An epic cannot convert to a sub-task.
D. Users need to enable Kanban Backlog to use Epic in the Kanban Board.
E. Users can customize Epic’s colour in both Kanban and Scrum projects.
F. An epic can have issues that belong to more than one project.

View Answer

Answer: C,F

Explanation:

Options C An epic cannot convert to a sub-task.

Sub-tasks are intended to be smaller parts of a standard issue, not a larger construct like an epic. While you can convert issues to epics and vice versa, it’s not possible to convert an epic directly into a sub-task, as they serve different functions and have different hierarchical levels.

Options F An epic can have issues that belong to more than one project.

In Jira, an epic is a large body of work that can be broken down into a number of smaller stories, or sometimes called "issues". It’s possible for these issues to belong to more than one project, which allows for cross-project tracking and management.

Which of the following are part of the Jira Automation rules? (Choose three.)
A . Listeners
B. Conditions
C. Triggers
D. Actions
E. Requirements
F. Steps

View Answer

Answer: B,C,D

Explanation:

Automation rules are made up of three parts:

Triggers (When):

Every rule starts with a trigger. They kick off the execution of your rules. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed.

Conditions (If/Else-if/Else):

Users can specify conditions that must be met for their rule to continue running. For example, their rule will only escalate an issue if it is a high priority. If a condition fails, no actions following it will be performed. The exception is with the If/else block condition. Not all rules need to have conditions. Conditions can be placed anywhere in the rule chain.

Actions (Then):

Actions are the doers of your rule. They allow you to automate tasks and make changes within your site and can perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks.

Razi’s team and Dom’s team are working on the same backlog, but they have their own active sprint.

Which of the following are true about parallel sprints? (Choose three.)
A . If users want to complete active sprint A with unresolved issues, they cannot move it to active sprint B.
B. Project administrators can disable the parallel sprint feature for their projects.
C. Users cannot complete multiple active sprints at once.
D. Users can run up to 2 parallel sprints only.
E. Users cannot have a separate velocity chart for each team.

View Answer

Answer: A,C,E

Explanation:

The parallel sprints feature lets users enable multiple active sprints that are running parallel to each other. For example, if they have two teams working on the same backlog, each team can now work on their own active sprint simultaneously.

Users can only complete one sprint at a time.

Atlassian does not mention whether there are limits on how many sprints users can run in parallel, however it is possible for users to run more than two parallel sprints.

Users cannot have a separate velocity chart for each team.

Sprint feature can be enabled/disabled from the global settings. Only Jira administrators have access to control it.

If there are unresolved issues in the current active sprint and users want to complete the sprint, users can only move them to inactive sprint or backlog. They cannot move them to other active sprints.

__________ shows user how their team is progressing against the work for an epic.

Cumulative flow diagram
A . Epic burndown report
B. Burndown chart
C. Velocity chart
D. Control chart

View Answer

Answer: A

Explanation:

The Epic Burndown report shows you how your team is progressing against the work for an epic. An epic is a large user story that can be broken down into a number of smaller stories. The report will show data based on the estimation statistic that your board is using.

Which field is suitable for the requirements below? (Choose two.)

– Can be shared globally

– Users can select only a single value

– Must have a default value

– Can have different options for different projects.
A . Radio Button
B. Components
C. Text Field (single line)
D. Checkboxes
E. Labels
F. Select List (single choice)

View Answer

Answer: A,F

Explanation:

Both these fields allow users to select a single value and can have a default value. These field types can also be used across different projects. Additionally, the options available in the select list or radio buttons can vary depending on the configuration of the field context, allowing different options for different projects.

According to the components below, who will be the assignee if a user created a ticket with all these components?

Project lead: Razi

Project default assignee: Project Lead

A . Nina
B. Razi
C. Nick
D. Dom
E. Unassigned

View Answer

Answer: C

Explanation:

A component default assignee will override the project’s overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that is first alphabetically.

As a project manager, Dom is responsible in monitoring all issues that have been assigned to his team are on track and the Time Estimation for each issue is correctly measured.

Which of the following is the best report that he can use to ensure Time Estimation and Time Spent by his team on issues are on track?
A . Single Level Group By Report
B. Pie Chart Report
C. Resolution Time Report
D. Time Tracking Report
E. Average Age Report
F. Time Since Issues Report

View Answer

Answer: D

Explanation:

Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues.

– Identify which issues have exceeded the original estimation.

– Identify which issues are still on track.

– Identify which issues are correctly measured.

– Identify accuracy of the overall time estimation.

– Identify the current team’s progression on issues that they are currently working on.

Razi accidentally deleted a column from the board. Assuming he has full access to manage the board, which of the following is true?

A. The user cannot delete a column that contains at least one status.

B. Statuses associated with that column will be deleted.

C. Some issues will be deleted.

D. All answers are incorrect.

E. The number of issues in the report will change.

View Answer

Answer: A

Explanation:

A. The user cannot delete a column that contains at least one status.

When you delete a column in a Jira board, the statuses associated with that column are not deleted; instead, they just become unmapped from that board. So, this action does not delete the actual statuses (option B) or the issues (option C) associated with that status.

It’s also important to note that deleting a column will not directly change the number of issues in reports (option E) – this is determined by the issues themselves, not the board’s columns. However, it could affect how those issues are visualized on the board and in certain reports that are based on board configuration.

Thus, option D is incorrect, because there is a correct answer: option A. The user can indeed delete a column that contains at least one status – but as mentioned, the status will simply become unmapped from the board, not deleted.

Dom created an issue in Project A. Now he wants to move the issue to Project B.

According to the information below, which of the following fields will retain their values after moving the issue to Project B? (Choose two.)

Project A custom fields:

– Custom Field A – Text Field (single line)

– Custom Field B – Text Field (single line)

– Custom Field C – Version picker

Project B custom fields:

– Custom Field A – Text Field (single line)

– Custom Field C – Version picker

A. Custom Field A

B. Components

C. Fix Versions

D. Labels

E. Custom Field C

F. Custom Field B

View Answer

Answer: A,D

Explanation:

Component and version fields are project fields; not global fields. Therefore, those data will be permanently lost if users move issues between projects. This includes the Version Picker custom field. Other incompatible fields will also appear empty, even if users choose to retain their values.

In this example, only Labels and Custom Field A will retain their values:

– Labels’ values are shared globally.

– Custom Field A is compatible with Project B. Thus, Jira will retain its value.

– Project B does not have Custom Field B. Thus, Jira will not retain its value.

– Custom Field C is a version picker. Jira will not retain the version’s value.