Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Atlassian Exam ACP-100 Topic 5 Question 109 Discussion

Actual exam question for Atlassian's ACP-100 exam
Question #: 109
Topic #: 5
[All ACP-100 Questions]

Critical production bugs in a Jira Software project are hidden with an issue security scheme that has a single

security level.

Only project administrators are listed in the security level and granted the Set Issue Security permission.

A new requirement states that a few other Jira Core users, who have Browse Projects permission, should be able to see the hidden issues. These users will vary per issue and be selected from across various groups.

What needs to be added to the security level?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Ashton
8 days ago
Group is the way to go, no doubt about it. Keeps things simple and maintainable. Option F is the winner!
upvoted 0 times
...
Allene
10 days ago
Ooh, B, User custom field value, sounds like a creative solution. But I'm not sure how well that would scale in the long run. I'll stick with F, Group.
upvoted 0 times
...
Xuan
11 days ago
Haha, imagine if the answer was E, Single Users. That would be a nightmare to manage! I'm going with C, Group custom field value.
upvoted 0 times
...
Antione
14 days ago
I think D, Project role, is the best choice here. You can easily assign the necessary permissions to specific roles and avoid managing individual users.
upvoted 0 times
...
Elmira
17 days ago
I believe adding Group custom field value is the best choice as it allows flexibility in selecting users from different groups.
upvoted 0 times
...
Joaquin
22 days ago
I think Project role could also be a good option to add to the security level.
upvoted 0 times
...
Rebbecca
23 days ago
I agree with Tamekia, adding Group custom field value would allow us to select users from different groups.
upvoted 0 times
...
Tamekia
26 days ago
I think we should add Group custom field value to the security level.
upvoted 0 times
...
Coral
1 months ago
Option F is the way to go. Group access is the easiest way to manage this requirement. Plus, it's more secure than individual users.
upvoted 0 times
Arminda
2 days ago
I agree, using groups for security levels makes it easier to manage permissions for multiple users.
upvoted 0 times
...
Marvel
5 days ago
Option F is the way to go. Group access is the easiest way to manage this requirement. Plus, it's more secure than individual users.
upvoted 0 times
...
Maybelle
23 days ago
C) Group
upvoted 0 times
...
Whitley
24 days ago
B) Group
upvoted 0 times
...
Long
28 days ago
A) Group
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77