All projects use a shared permission scheme.
The Browse Projects permission needs to be updated so that projectadministratorscan
manage access to their own projects.
What entry must be added to the Browse Projects permission?
A. Application Access
B. Project Lead
C. Single User Project Role
D. Group
You need to find all issues that were not competed in some past sprint, and that are now part of an active sprint. Identify two functions that you need to use in your JQL query. (Choose two.)
A. closedSprints()
B. futures prints()
C. completed()
D. remaming()
E. openSprints()
Explanation: The two functions that are needed to use in the JQL query to find all issues
that were not completed in some past sprint, and that are now part of an active sprint are
closedSprints() and openSprints(). The closedSprints() function returns all issues that are
assigned to a completed sprint. The openSprints() function returns all issues thatare
assigned to an incomplete sprint. By combining these two functions with the NOT operator,
we can filter out the issues that belong to both a completed sprint and an incomplete sprint,
and only get the issues that were not completed in some past sprint, and that are now part
of an active sprint. For example, the JQL query could be:
project = XYZ AND issuekey NOT IN (closedSprints() AND openSprints())
This query will return all issues in project XYZ that are not in both a closed sprint and an
open sprint, meaning they are either in a closed sprint only or an open sprint only. Since we
are looking for issues that are now part of an active sprint, we can assume they are in an
open sprint only. References: Advanced search reference - JQL functions, Modifying
closedSprints() to return previous two Sprints, JQL - Explanation of what closedSprints()
does
The team wants to flag issues using a category. Their requirements are:
• more than one category value can be selected on an issue
• new category values can be added by any user
• category values can be selected via a dropdown menu
• category values can be re-used across all projects
Which field meets their requirements?
A. text field
B. component
C. user picket
D. label
E. checkboxes
Explanation: The label field meets the team’s requirements for flagging issues using a category. Labels are a type of custom field that allow users to add one or more descriptive tags to issues. Users can add new labels on the fly, and select existing labels from a dropdown menu. Labels can be re-used across all projects, and can be searched and filtered easily. A text field does not allow multiple values or a dropdown menu. A component does not allow multiple values or adding new values by any user. A user picker does not allow multiple values or adding new values byany user. Checkboxes do not allow adding new values by any user.
Depending on the project configuration, a project administrator might be able to perform some tasks, instead of escalating them to the Jira administrator. Identic one such task.
A. Remove Watchers from project notifications.
B. Remove a priority value used by the project.
C. Update permissions for a project user.
D. Limit who can bulk edit project issues.
Explanation: A project administrator can remove watchers from project notifications, if they have the Manage Watchers permission. This is a task that does not require Jira administrator access, and can be done by the project administrator from the issue view. Removing a priority value used by the project, updating permissions for a project user, and limiting who can bulk edit project issues are all tasks that require Jira administrator access, and cannot be done by the project administrator.
Your team uses Story Points for estimation and tracking.
You performed several actions in the active sprint.
Which two actions are reflected as scope change? (Choose two.)
A. Added a fix version on a committed story.
B. Estimated a story in the backlog.
C. Dragged on estimated story from the backlog to the sprint.
D. Modified the estimate value on a committed story.
E. Added another 5ub-task to a committed story.
F. Logged work on several committed stories.
Explanation: The two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint.
Gen prioritizes and triages support requests as soon as they come in. She now wants to
use drag-and-drop to:
• quicklyassign and transition them to in Progress
• instantly associate them with Epics
Which board view will meet these requirements?
A. Scrum backlog
B. Kanban board
C. Kanban backlog
D. Active sprints
You want to remove some epics from your personal Scrum board, without impacting any other boards. Identify the correct solution.
A. Exclude them via a quick filter.
B. Mark them as Done via the Epics panel
C. Exclude them via the board filter
D. Exclude them via the board sub filter.
E. Transition them into an unmapped status.
You are reviewing the Velocity Chart for your team and notice that they completed more story points than they committed in their last sprint. You are definitely the only person who can add issues to sprints in your project. How did your learn complete more story points than they committed?
A. The sprint was completed early.
B. An epic with a story point estimate was completed during the sprint.
C. Someone increased the story point value on an issue mid-sprint.
D. A sub-task was in an unmapped status at the start of the sprint.
E. A new sub-task was created drying the sprint
Explanation: The reason why your team completed more story points than they committed in their last sprint is that someone increased the story point value on an issue mid-sprint. This will increase the total story points completed at the end of the sprint, but not affect the total story points committed at the start of the sprint. Therefore, it will result in a positive scope change. The other reasons mentioned in the question do not explain why your team completed more story points than they committed, as they either do not affect story points at all, or affect both committed and completed story points equally.
Your Scrum board has the following filter query:
project in (ENG. DEV) and type in (Bug. Task) ORDER BY Priority ASC
You have the necessary permissions but you are unable to drag an issue into a future
sprint in the backlog.
A. Identify the reason.
B. The filter should be in DESC order.
C. Stories are missing from the query.
D. Ranking is disabled.
E. The query should only have one project.
F. The active sprint has not yet been completed.
Explanation: The reason why you are unable to drag an issue into a future sprint in the backlog is that ranking is disabled. Ranking is a feature that allows you to order issues based on their relative priority or importance. Ranking is enabled by adding “ORDER BY Rank ASC” or “ORDER BY Rank DESC” to your board filter query. Ranking is required for Scrum boards, as it determines the order of issues in your backlog and sprints. If ranking is disabled, you cannot drag and drop issues in your backlog or plan future sprints.
Bethany knows the URL of an issue that she wants to restore in a particular project.
What are the minimum two permissions that she needs to restore the issue? (Choose two.}
A. Restore Issues
B. Browse Project Archive
C. Move Issues
D. Edit Issues
E. Browse Projects
Explanation: To restore an issue from the project archive, Bethany needs two permissions: Restore Issues and Browse Project Archive. The Restore Issues permission allows Bethany to restore issues that have been archived in a project. The Browse Project Archive permission allows Bethany to view the archived issues in a project. Without these permissions, Bethany will not be able to access or restore the archived issue, even if she knows the URL. The other permissions are not relevant for restoring an issue. The Move Issues permission allows Bethany to move issues from one project to another. The Edit Issues permission allows Bethany to modify the details of an issue. The Browse Projects permission allows Bethany to see the project and its issues, but not the archived ones. For more information on how to archive and restore issues, see Archive and restore issues and Manage project permissions.
The team requests that you update the name of your project. What impact will this have on Jira?
A. The URL for issues will change.
B. The project key will change.
C. Issue filters may need to be updated.
D. Issue search will not find issues from that project until Jira is re indexed.
Explanation: Updating the name of your project will not affect the URL for issues, as they are based on the project key, not the name. The project key will also remain unchanged unless you explicitly change it. Issue search will still find issues from that project regardless of the name change. However, issue filters may need to be updated if they use the project name as a criterion. Therefore, the correct answer is C.
A project was created with a shared configuration. Which two configurations were shared?
(Choose two.
A. component lead assignments
B. versions
C. transition screens
D. project role membership
E. project permissions
Explanation: When a project is created with a shared configuration, it inherits the configurations of an existing project. This includes the workflow, issue types, screens, fields, permissions, notifications, and schemes associated with them. However, the component lead assignments and versions are specific to each project and are not shared. Therefore, the correct answer is C and E.
| Page 2 out of 7 Pages |
| Previous |