Question No : 1
Nash can view all issues but he is unable to rank the backlog in the Jira Software board.
Which permissions does Nash need to request to get the proper access? (Choose two.)

• A.Edit issues
• B.View Development Tools
• C.Manage sprints
• D.Schedule issues
• E.Browse Projects
• F.Move Issues

Show Answers

Answer:
Explanation:
Since Nash can view the issues in the Jira project, he does not need to request the Browse Projects permission anymore.
To rank issues in the backlog section, Nash needs to have both the schedule and edit issues permission. Ranking backlog here means changing the issue's Due Date. You need both permissions to change the issues' Due Date.
Schedule issues grant the ability to view or edit an issue's due date.
Edit issues grant the ability to edit issues.
Manage sprints, Move Issues, and View Development Tools are not required.
View Development Tools to grant users in a software project to view development-related information on the issue, such as commits, reviews, and build information.

Question No : 2
Razi has added and enabled the automation below. After Razi creates an issue, which of the following are true about the assignee of that issue? (Choose two.)
(Assume this automation is using the default priority, and all of the required permissions and labels exist.)
Questions and Answers PDF 12/40

• A.Issues with the highest priority and a Java label will be assigned to Unassigned.
• B.Issues with the highest priority will be assigned to Nina.
• C.Issues with a high priority will be assigned to Razi.
• D.Issues with a high priority will be assigned to Nina.
• E.Issues with a high priority will be assigned to Unassigned.
• F.Issues with a Java label will be assigned to Razi.

Show Answers

Answer:
Explanation:
An issue that matches the first rule will be assigned to Razi since Razi is the user that triggers the action.
The action here refers to creating the issue.
labels = Java OR priority > Medium will return any issues with a Java label or any issues that have high or highest priority. Therefore, issues with the highest priority will always match the first rule and ignore the second rule. Nina will not be the assignee.

Question No : 3
Which of the following are true about the roadmap? (Choose four.)

• A.Users can filter epics and issues by the assignee.
• B.Users can filter epics and issues by components.
• C.Users can leave a comment in the roadmap dashboard.
• D.Users can create a new issue from the roadmap dashboard.
• E.Users can filter epics and issues by status.

Show Answers

Answer:
Explanation:
Users can create new epics, new issues, and new comments from the roadmap dashboard.
Users can filter issues based on:
- Issue summary
- Assignee
- Status category
- Versions
- Label
- Issue type
Reference:
- Customize Your View on the Roadmap
- Create Epics on the Roadmap
If the below image is not visible, right-click the below image then click 'Open image in new tab'.

Question No : 4
As a scrum master, Sarah needs access to manage a sprint and rank an issue.
According to this table, how many roles need to be assigned to Sarah?

• A.3
• B.1
• C.4
• D.2

Show Answers

Answer:
Explanation:
To rank an issue, the user needs Schedule and Edit Issues permission. The role 'editors' is required.
To view an issue, the user needs Browse Projects permission. The role 'users' is required.
To manage sprints, the user needs Manage Sprints permission. The role 'leads' is required.
Therefore, Sarah needs 3 roles.
Administer Projects permission allows users to administer a project in Jira, which includes managing versions and components. Sarah does not need this permission.
Reference:
- Rank an issue
- Project permissions

Question No : 5
Based on the below diagram, which statements are true? (Choose three.)

• A.On July 25th, the 'To Do' status has the highest number of issues compared with other statuses.
• B.In Progress' status on July 21st and July 25th have the same number of issues.
• C.On July 25th, the 'Done' status has the highest number of issues compared with other statuses.
• D.In Progress' status on July 21st and July 25th have different number of issues.
• E.On July 25th, all statuses have the same number of issues.
• F.On July 21st, all statuses have the same number of issues.

Show Answers

Answer:
Explanation:
On July 21st, there are:
- 5 issues in 'To Do'
- 5 issues in 'In Progress'
- 5 issues in 'Done'
- 10 issues in 'Done'
Reference: View and understand the cumulative flow diagram

Question No : 6
Which of the following are the best scenarios to use Components more than Custom Field? (Choose two.)

• A.The Jira administrator will manage the new field.
• B.All Jira projects can add this new field to their issue screen.
• C.The project administrator will manage the new field.
• D.The assignee must be automatically populated based on the selected value.
• E.The user can only select a single option from the new field.

Show Answers

Answer:
Explanation:
Components:
Users should use components when they want to auto-assign an issue to a specific user. An issue can have more than one component. Project administrators have the proper access to manage the project component. Since components only belong to a Jira project, users cannot share the component globally with other Jira projects.
Custom fields:
Users should use custom fields if they want the field to be used globally. The custom field has a few field types that can only accept a single value. Jira administrators have global permission to manage the custom field.

Question No : 7
Sarah's team has 10 completed issues in the current active sprint.
As a Jira administrator, what is the minimum permission Sarah needs to complete the sprint?

• A.Manage Sprints
• B.Schedule Issues
• C.Transition Issues
• D.Move Issues
• E.Browse Projects
• F.Edit Issues

Show Answers

Answer:
Explanation:
To complete a sprint, users must be a Jira Administrator. Non-administrator users need Manage Sprints permission to manage the sprint. Since the user is a Jira administrator, Manage Sprints permission is not required.
Browse Projects is the required permission to view the issues.
Move Issues permission is for moving issues to another project, which is not required in managing the sprint. Transition Issues grants users the ability to transition issues' status, which is not required in managing the sprint.
When completing a sprint, users need Edit and Schedule Issues permission if there are incomplete issues. The incomplete issues need to be moved to the backlog or to the next sprint. If all issues are completed, these two permissions are not required.
Reference:
- Complete a sprint
- Project permissions
- Permissions for company-managed projects
Without the Manage Sprints permission. (Non-admin)
Without the Edit Issues permission if there are incomplete issues.
Without the Schedule Issues permission if there are incomplete issues.

Question No : 8
contain one or more rules defined by users. If automation will not execute the tasks. do not match with the rules,

• A.Requirements
• B.Actions
• C.Listeners
• D.Conditions
• E.Triggers

Show Answers

Answer:
Explanation:
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.
Automation rules are made up of three parts:
- Triggers (When)
- Conditions (If/Else-if/Else)
- Actions (Then)
Reference:
- What are automation rules?
- Automation conditions

Question No : 9
Sarah is working on a financial project that involves sensitive information which should not be openly available to any users. She wants to create a new team-managed project for her assignment.
Suggest the best access level for Sarah's project.
Note:
- Company-managed projects are formerly known as classic projects.
- Team-managed projects are formerly known as next-gen projects.

• A.Limited
• B.Individual
• C.Private
• D.Open
• E.Restricted
• F.Public

Show Answers

Answer:
Explanation:
Since Sarah's project contains sensitive information, she should use private level access for her project. By using this access level, Sarah can control who can have access to manage issues in her project.
These are the three access levels in team-managed Jira projects:
Open - Anyone with access to the site can search, view, create, or edit this project's issues.
Limited - Anyone with access to the site can search, view, and comment on this project's issues. Only people added to the project can create and edit its issues.
Private - Only admins and people added to the project can search, view, create, or edit its issues.

Question No : 10
Razi works on multiple Jira projects. Although he can confirm the status properly mapped to the board column, he claims that a few issues are still missing from the Scrum board.
Which of the following are the possible root causes? (Choose three.)

• A.Missing 'Browse Projects' permission.
• B.The board sub-filter is hiding some issues.
• C.Missing 'View Development Tools' permission.
• D.Users selected one of the quick filter.
• E.The board filter is hiding some issues.

Show Answers

Answer:
Explanation:
View Development Tools permission is not related with hidden issues. This permission allows users to view the development panel, which displays information from Bitbucket, GitHub, Fisheye, Crucible, and Bamboo.
Board Sub-Filter only exists in the Kanban Board. This user is using a Scrum board.
These are the possible reasons why issues would be missing from the Jira board:
- The JQL from Board Filter or Sub-Filter excludes some issues.
- Users selected Quick Filter that filtered out some of the issues.
- Users do not have the Browse Projects permission to view the issues.
- Some issues have Issue Level Security.
- Some issues are mapped to the Unmapped Statuses column.