Question 1

Issue linking used to work fine in both team-managed and company-managed project. After a recent change, all users have reported that they are not able to link issues anymore. Even automation rules are failing to link issues.

What is the most possible reason

Options :

A : “Link issues” global permission was revoked for all groups

B : All link types were deactivated

C : All link types were renamed

D : “Issue linking” was deactivated

Answer: D

Question 2

Leila is the Board administrator of the company-managed project “SAT”.

Leila is unable to update the component lead.

Below is an extract from the “SAT” project permission scheme:

Permission Users/Groups/Project roles

-------------------------------------------------------------------------------------

Administer Projects Project Role (atlassian-addons-project-access)

Project Role (Administrators)

--

Browse Projects Project Role (Scrum Team)

Project Role (Scrum Master)

Project Role (Product Owner)

--

Edit issue Project Role (Product Owner)

Project Role (Scrum Team)

--

Resolve issues Project Role (Scrum Team)

Project Role (Scrum Master)

--

Close issues Project Role (Product Owner)

--

“SAT” project configuration must be updated so Leila can update the component lead.

Identify the correct update?

Options :

A : Add Leila to the “Product Owner” project role

B : Add Leila to the “Scrum Master” project role

C : Add Leila to the “Scrum Team” project role

D : Add Leila to the “Administrators” project role

E : Add Leila as Project lead

Answer: D

Question 3

All company-managed projects share the same permission scheme and workflow scheme. New requirements state: Only auditors should be able to use the 'Needs Audit' workflow transition. All auditors work across all the projects. How should auditors be configured?

Options :

A : As a User custom field

B : As a group

C : As a Group custom field

D : As single users

Answer: B

Question 4

You have two issue types in your company-managed project “DEV”: Task and Story.

Identify which requirements can be met through changes to field configurations? (choose two)

Options :

A : For the Story issue type, the “Description” system field should have a default value of “As a <user>, I want <x> because <y>”.

B : For the Task issue type, the default value for the “Priority” system field should be “Low”

C : For both issues types, the “Labels” system field should be hidden when creating but accessible when editing an issue

D : For the story issue type, the “Definition of Ready” paragraph custom field should display colored and bold text

E : For both issue types, hide the assignee field if a component has been selected when creating an issue

Answer: A,B

Question 5

Amelia is the project administrator of the company-managed project “FIX” which uses three issue types: Epic, Story and Task.

“FIX” users have a new requirement and need the following configuration shown below:

Issue type Priority(System Field) Business Value(CF) Score(CF)

-----------------------------------------------------------------------------------------

Epic Hidden Required, Options(B1,B2,B3) Required

Story Shown and optional Required, Options(B10,B20,B30) Hidden

Task Required Hidden Hidden

Which configuration update will meet all these requirements above ?

Options :

A : Configure two field configurations and two field contexts

B : Configure one field configuration

C : Configure three field configurations and add two field contexts

D : Configure three field configurations and add three field contexts

E : It is not possible to meet all requirements

Answer: A

Higher Test Marks with Free Online ACP-120 Exam Practice

Buying Options: