Download Jira Issue Security Skillbuilder Practice Exam and more Exams Technology in PDF only on Docsity!
Question 1. Which Jira permission determines whether a user can initially see a project before issue‑level security is applied? A) Browse Projects B) Create Issues C) View Development Tools D) Manage Sprints Answer: A Explanation: The Browse Projects permission is checked first; only users with it can see the project. Issue security then further restricts visibility of individual issues. Question 2. What is the primary purpose of an Issue Security Scheme? A) To define workflow transitions B) To group projects by component C) To control which users can view issues at a given security level D) To assign default assignees Answer: C Explanation: An Issue Security Scheme contains levels that specify which users, groups, or roles may view issues assigned to that level. Question 3. In Jira, the “Security Level” field is considered a: A) Custom field B) System field
C) Agile field D) Notification field Answer: B Explanation: “Security Level” is a built‑in system field used to store the security level selected for an issue. Question 4. Which of the following entities cannot be added directly to an Issue Security Level? A) Project Role B) Group C) Issue Type D) Single User Answer: C Explanation: Issue Types define the kind of issue, not visibility. Security Levels accept users, groups, project roles, reporters, assignees, and user‑picker fields. Question 5. If a project has no default security level set in its scheme, what happens when a user without “Set Issue Security” creates an issue? A) The issue is created with no security level and is visible to all who can browse the project. B) The issue creation fails. C) Jira automatically assigns the highest security level. D) The issue is hidden from all users.
Question 8. Which permission allows a user to change the security level of an existing issue? A) Edit Issues B) Set Issue Security C) Manage Project Role D) Assign Issues Answer: B Explanation: The “Set Issue Security” permission specifically controls who can modify the Security Level field on an issue. Question 9. In a workflow post function, which option correctly sets the security level to “Confidential” after a transition? A) Update Issue Field → Security Level → Confidential B) Add Comment → Confidential C) Change Reporter → Confidential D) Set Issue Type → Confidential Answer: A Explanation: The post function “Update Issue Field” can be used to set the Security Level field to a specific level such as “Confidential”. Question 10. Which of the following best describes the principle of least privilege in the context of Jira issue security?
A) Giving every user admin rights. B) Assigning the highest possible security level to all issues. C) Granting users only the minimum permissions needed to perform their tasks. D) Allowing all users to view all issues. Answer: C Explanation: Least privilege means users receive only the access necessary, which is enforced via issue security levels. Question 11. Which JQL clause returns issues that are assigned to the security level “HR Only”? A) level = "HR Only" B) security = "HR Only" C) issueSecurity = "HR Only" D) securityLevel = "HR Only" Answer: B Explanation: The JQL field “security” is used to filter issues by their assigned security level. Question 12. What happens to sub‑tasks when the parent issue’s security level is changed? A) Sub‑tasks retain their original security level. B) Sub‑tasks are automatically deleted.
Answer: A Explanation: Screens are configured via Screen Schemes; adding the Security Level field to the Edit screen makes it visible when editing an issue. Question 15. Why is the Security Level field typically not added to the Create Issue screen by default? A) Because Jira does not allow any custom fields on Create screens. B) To prevent users without “Set Issue Security” from setting a level they may not be authorized for. C) Because it is a hidden field. D) Because it conflicts with the Issue Type field. Answer: B Explanation: Without the “Set Issue Security” permission, users could set inappropriate levels; therefore, it is omitted from the Create screen unless a workflow post function sets it. Question 16. In Jira Service Management, which element can be configured to automatically apply a specific security level to incoming requests? A) SLA policies B) Request Type configuration C) Customer portal theme D) Knowledge base article Answer: B
Explanation: Request Types can be set to assign a default security level when a request is created. Question 17. If a user can browse a project but cannot see any issues, which of the following is the most likely cause? A) The user lacks the “Create Issues” permission. B) All issues are assigned a security level that does not include the user. C) The project’s workflow is disabled. D) The user’s browser is not supported. Answer: B Explanation: Issue Security Levels restrict visibility after the Browse Projects check; if the user is not in any level, they see no issues. Question 18. Which tool can help verify why a particular user cannot view an issue? A) Issue Navigator B) Permission Helper C) REST API Explorer D) Agile Board Settings Answer: B Explanation: The Permission Helper (or Permission Checker) shows which permissions are missing for a user on a specific issue.
B) Reporter (special field) C) Current Assignee D) User Picker custom field Answer: B Explanation: The “Reporter” option in a security level automatically includes the user who created the issue. Question 22. What effect does setting a default security level have on issues created via the REST API by a user lacking “Set Issue Security”? A) The API call fails. B) The issue is created with the default security level. C) The issue is created with no security level. D) The issue is assigned the highest security level. Answer: B Explanation: The default level is applied automatically when the creator cannot set a level manually. Question 23. Which permission must be granted to a user to allow them to change the security level of issues they do not own? A) Edit Own Issues B) Set Issue Security C) Assign Issues
D) Manage Project Role Answer: B Explanation: “Set Issue Security” controls who can modify the security level regardless of issue ownership. Question 24. In a JQL search, a user without access to the “Legal Review” security level runs: security = "Legal Review". What will they see? A) All issues with that level. B) No results, because they lack visibility. C) An error message. D) Only issues they reported. Answer: B Explanation: JQL respects security; users only see results they have permission to view. Issues they cannot see are omitted. Question 25. Which of the following is NOT a recommended practice when designing Issue Security Schemes? A) Use project roles instead of static groups. B) Keep the number of security levels minimal. C) Create a separate scheme for every issue type. D) Use clear, descriptive names for levels. Answer: C
Question 28. Which of the following statements about the “Browse Projects” permission is true? A) It overrides all issue security levels. B) It is checked before any issue‑level security is evaluated. C) It is only relevant for administrators. D) It controls who can edit issues. Answer: B Explanation: Jira first checks “Browse Projects” to determine if a user can see the project; then issue security further filters visible issues. Question 29. If a project’s Issue Security Scheme contains a level named “Executive”, but no users or groups are assigned to it, what is the effect? A) All users can see issues with this level. B) No one can see issues with this level, even admins. C) Only users with “Administer Projects” can see them. D) Issues automatically revert to the default level. Answer: B Explanation: Without any entities assigned, the level grants visibility to nobody, effectively hiding the issue from all users. Question 30. Which of the following can be used to audit which Issue Security Schemes are associated with projects? A) System Dashboard
B) Issue Security Scheme Report (available in Administration > Issues) C) Project Archive D. Audit Log for Workflow Transitions Answer: B Explanation: The Issue Security Scheme Report lists all schemes and the projects they are linked to. Question 31. In a workflow, which validator would prevent a transition if the issue’s security level is not “Public”? A) Permission Validator B) Value Field Validator for Security Level ≠ Public C) Sub‑task Validator D) Date Validator Answer: B Explanation: A Field Value Validator can enforce that the Security Level field matches a specific value before allowing the transition. Question 32. Which of the following is a visual cue in the Jira UI indicating an issue is secured? A) A red exclamation mark B) A lock icon next to the issue key C) A green checkmark
Explanation: Granting “Set Issue Security” to the “Team Lead” role enables them to choose or change the security level on issues they handle. Question 35. In Jira Service Management, a customer portal user can see a request only if: A) The request’s security level includes the “Customers” role. B) The request is marked as “Public”. C) The user is an admin. D) The request type is “Incident”. Answer: A Explanation: Customer portal visibility respects issue security; the security level must include a role or group that contains the portal user. Question 36. What is the impact of assigning a group with 500 members to a security level? A) The group is automatically split into smaller groups. B) Jira may experience performance degradation when evaluating visibility. C) Only the first 100 members are considered. D) The group is ignored for security purposes. Answer: B Explanation: Large groups increase the load on permission checks, potentially affecting performance; using project roles is more efficient.
Question 37. Which of the following actions can a user with “Set Issue Security” permission NOT perform? A) Change the security level on an existing issue. B) Delete a security level from the scheme. C) Set the security level during issue creation via a workflow. D) View the lock icon on secured issues. Answer: B Explanation: Modifying the scheme (adding/removing levels) is an admin task, not controlled by the “Set Issue Security” permission. Question 38. When configuring a security level, the “Reporter” option is useful for: A) Granting visibility to the issue’s creator regardless of other assignments. B) Automatically assigning the issue to the reporter. C) Preventing the reporter from seeing the issue. D) Setting the issue’s priority. Answer: A Explanation: Selecting “Reporter” adds the issue’s creator to the list of users who can view the issue. Question 39. Which JQL function can be used to find issues where the current user is included in the security level? A) security = currentUser()
D) Changing the issue type automatically. Answer: B Explanation: Workflow conditions control transition permissions based on group membership, not issue visibility, which is handled by security levels. Question 42. In the Permission Helper, if the “Browse Projects” check passes but the “Issue Security” check fails, what does this indicate? A) The user lacks project permissions. B) The issue’s security level does not include the user. C) The issue is deleted. D) The workflow is broken. Answer: B Explanation: The helper separates project‑level and issue‑level checks; a failure on “Issue Security” means the user isn’t granted visibility by the level. Question 43. Which of the following is a consequence of adding the Security Level field to a screen that is used for creating issues? A) Users without “Set Issue Security” can set any level they choose. B) The issue creation will fail for all users. C) The field will be hidden automatically. D) The screen will be disabled. Answer: A
Explanation: If the field is present on the Create screen, users who can see it may set a level even without the permission, potentially violating security policies. Question 44. When a Jira administrator copies an existing Issue Security Scheme, what is duplicated? A. All security levels and their associated users/groups/roles. B. Only the scheme name. C. Only the default security level. D. No levels; the new scheme is empty. Answer: A Explanation: Copying a scheme clones its levels and assignments, allowing quick reuse. Question 45. Which of the following best explains why “Project Role” is preferred over “Group” for security level assignments? A) Roles can be scoped per project, providing finer granularity. B) Groups cannot be used in security levels. C) Roles automatically grant admin rights. D) Groups are hidden from the UI. Answer: A Explanation: Project roles are defined per project, making them more flexible than global groups for controlling issue visibility.
