Which of the following are suitable use-cases to use issue-level security? (Choose two.)
- A . Only managers can view certain projects.
- B . Only managers can view and edit high-priority issues.
- C . Only managers can view the development panel.
- D . Only managers can view issues created by the manager level.
- E . Only managers can move issues to other projects.
B,D
Explanation:
Users can create issue security levels within issue security schemes to let users and their team control who can see particular issues. When users associate an issue security scheme with a project, they can apply its security levels to issues in that project. Subtasks inherit the security level of their parent issue.
Note: Users need to be a Jira administrator to configure issue security levels.
If users need to move issues, they need Move Issues permission.
Browse Projects is the permission to control who can view the project.
Users need to use View Development Tools permission to control who can view the development panel.
__________ shows user how their team is progressing against the work for an epic.
Cumulative flow diagram
- A . Epic burndown report
- B . Burndown chart
- C . Velocity chart
- D . Control chart
A
Explanation:
The Epic Burndown report shows you how your team is progressing against the work for an epic. An epic is a large user story that can be broken down into a number of smaller stories. The report will show data based on the estimation statistic that your board is using.
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
A,C
Explanation:
To be able to rank the backlog in the Jira Software board, Nash needs to request the following permissions:
Which of the following is not the default team-managed project role?
Note:
– Company-managed projects are formerly known as classic projects.
– Team-managed projects are formerly known as next-gen projects
- A . User
- B . Viewer
- C . Member
- D . Administrator
A
Explanation:
Team-managed software projects come with three roles by default:
– Administrator
– Member
– Viewer
Administrator – Admins can do most things, such as: update settings, add other admins to the project, manage features, customize issue types, and add rules on the board. Admins need product access to Jira Software to get the full benefit of this role.
Member – Members are a part of the team. They can create issues, edit them, comment on them, move them into different statuses, and generally collaborate on the project’s work. Members need product access to Jira Software to get the full benefit of this role.
Viewer – Viewers can search through and view issues in the project, but not much else. You can give any registered user on your Jira site this role without extra product access.
Which of the following are true about epic? (Choose two.)
- A . An epic can have another epic. (Epic Link)
- B . An epic cannot have its own issue screen.
- C . An epic cannot convert to a sub-task.
- D . Users need to enable Kanban Backlog to use Epic in the Kanban Board.
- E . Users can customize Epic’s colour in both Kanban and Scrum projects.
- F . An epic can have issues that belong to more than one project.
C,F
Explanation:
Options C An epic cannot convert to a sub-task.
Sub-tasks are intended to be smaller parts of a standard issue, not a larger construct like an epic. While you can convert issues to epics and vice versa, it’s not possible to convert an epic directly into a sub-task, as they serve different functions and have different hierarchical levels.
Options F An epic can have issues that belong to more than one project.
In Jira, an epic is a large body of work that can be broken down into a number of smaller stories, or sometimes called "issues". It’s possible for these issues to belong to more than one project, which allows for cross-project tracking and management.
According to the components below, who will be the assignee if a user created a ticket with Java and Database components?
Project lead: Razi
Project default assignee: Unassigned
- A . Nick
- B . Nina
- C . Razi
- D . Unassigned
- E . Dom
C
Explanation:
A component default assignee will override the project’s overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that is first alphabetically.
Since there are no components with component lead, and the component ‘Java’ default assignee is Project default, which is Unassigned, Jira will use the Project Lead, Razi.
Nash’s team just completed their first sprint.
What can they learn from this chart? (Choose three.)
(Assume Remaining Estimate and Time Spent is enabled for this board.)
- A . Some of the issues are resolved during non-working days.
- B . Some of the issues are still unresolved.
- C . This sprint ends with 0 story points.
- D . This sprint starts with 20 story points.
- E . There are issues worth 5 story points resolved on July 13th.
- F . There are no scope changes in this sprint.
C,E,F
Explanation:
The grey area indicates non-working days. There were no issues resolved during non-working days since story points did not reduce in the grey area.
This chart starts drawing the Guideline and Remaining Values lines at the 18 story points on the y-axis.
On July 13th, story points were reduced from 15 to 10. This means that users have closed some issues that are worth 5 story points.
Users have closed all issues on July 20th. There are no story points remaining on this date.
Story points do not increase during this sprint. Since the Remaining Estimate and Time Spent is enabled for this board, scope change is indicated in the Burndown Chart for the subtask.
Which of the following exists in both team-managed and company-managed Kanban Projects sidebar? (Choose four.)
Note:
– Company-managed projects are formerly known as classic projects.
– Team-managed projects are formerly known as next-gen projects.
- A . Version releases.
- B . A link connected to Bitbucket or GitHub repositories.
- C . Integration with Opsgenie for on-call and incident management.
- D . An informative page integrated with Confluence.
- E . Project components.
- F . A website link shortcut.
B C D F
Explanation:
option B A link connected to Bitbucket or GitHub repositories.
This feature allows team members to view code changes related to the project directly in Jira.
option C Integration with Opsgenie for on-call and incident management.
Opsgenie is a modern incident management platform that ensures critical incidents are never missed, and actions are taken by the right people in the shortest possible time.
option D An informative page integrated with Confluence.
Confluence integration provides a convenient way to create, view, and manage relevant Confluence pages from within Jira.
option F A website link shortcut.
Website link shortcuts can be added to the project sidebar in both types of projects for quick access to important external resources.
An existing Jira project will be handed over to a new team. Users want to change the project details for an upcoming new project.
Which project details can users change from the Details page? (Choose four.)
- A . Key
- B . Title
- C . Avatar
- D . Project Lead
- E . Name
- F . Project Type
B C D E
Explanation:
B. Title – You can modify the title to reflect the new focus or direction of the project.
C. Avatar – You can change the avatar or icon that represents your project.
D. Project Lead – The project lead can be changed to the person who will now be responsible for the project.
E. Name – The name of the project can be updated to something more suitable for the new team or project goals.
A group of developers are working on multiple Jira projects. They can view all Jira projects and have the ‘Move Issues’ permission in all Jira projects. However, they cannot move issues to some of the Jira projects.
What is the possible root cause of this problem?
- A . They do not have the ‘View Issue’ permission in some projects.
- B . They do not have the ‘Transition Issue’ permission in some projects.
- C . They do not have the ‘Edit Issue’ permission in some projects.
- D . They do not have the ‘Create Issue’ permission in some projects.
D
Explanation:
If users are moving issues from project to project, they need to make sure they have the Create Issues permission in the Jira project they want to move it to.
In the current sprint, users have 10 issues but their team is only able to complete 5 issues.
What will happen to the other 5 issues if they wish to complete the current sprint? (Choose two.)
- A . Unresolved issues will be removed.
- B . Users can move them to the next sprint.
- C . Users can move them to the other active sprints.
- D . Unresolved issues will be archived.
- E . Users can move them to their backlog.
B E
Explanation:
When a team completes a sprint in Jira and there are issues that have not been completed, the software provides options for handling these unfinished issues. From the options you’ve provided:
B. Users can move them to the next sprint.
If another sprint is already planned, the incomplete issues can be moved to that sprint.
E. Users can move them to their backlog.
If there is not a sprint already planned, or if it’s uncertain when the team will work on these issues, they can be moved back to the backlog.
The other options (A. Unresolved issues will be removed, C. Users can move them to the other active sprints, D. Unresolved issues will be archived) do not typically occur in standard usage of Jira’s Scrum boards. Active sprints are typically unique to each Scrum board and not shared among multiple teams, and unresolved issues are not automatically removed or archived when a sprint is completed. The exact behavior may depend on your specific Jira configuration and workflows.
Which of the following are true about team-managed projects? (Choose three.)
Note:
– Company-managed projects are formerly known as classic projects.
– Team-managed projects are formerly known as next-gen projects.
- A . Team-managed projects only have standard board filters.
- B . By default, any licensed users can create and maintain team-managed projects.
- C . Users can create multiple team-managed projects and run a parallel sprint.
- D . Users can share team-managed projects’ settings with other Jira projects.
- E . Users can allow anonymous access to a team-managed project.
- F . Users can create a new project role.
B C E
Explanation:
In the context of team-managed (formerly known as next-gen) projects in Jira, the following statements are true:
B. By default, any licensed users can create and maintain team-managed projects.
Team-managed projects are designed to be easy to set up and manage, and by default, any licensed user can create one. The user who creates the project becomes the project’s administrator.
C. Users can create multiple team-managed projects and run parallel sprints.
Each team-managed project has its own independent configuration, including sprints. This allows multiple team-managed projects to operate in parallel, each with its own sprints.
E. Users can allow anonymous access to a team-managed project.
Project permissions in team-managed projects are simplified compared to company-managed projects, and include the ability to allow anyone on the internet (anonymous users) to view the project.
Please note, in team-managed projects, settings are unique to each project and can’t be shared with other projects (D). Similarly, there is no facility to create new project roles (F), and the board filters are not limited to standard ones (A). As always, check the most recent Atlassian documentation for the most accurate information.
As a project manager, Dom is responsible in monitoring all issues that have been assigned to his team are on track and the Time Estimation for each issue is correctly measured.
Which of the following is the best report that he can use to ensure Time Estimation and Time Spent by his team on issues are on track?
- A . Single Level Group By Report
- B . Pie Chart Report
- C . Resolution Time Report
- D . Time Tracking Report
- E . Average Age Report
- F . Time Since Issues Report
D
Explanation:
Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues.
– Identify which issues have exceeded the original estimation.
– Identify which issues are still on track.
– Identify which issues are correctly measured.
– Identify accuracy of the overall time estimation.
– Identify the current team’s progression on issues that they are currently working on.
Nash is working on a Finance Jira project. The next week, while still working on the Finance project, he also worked on HR projects. Both projects are using their own unique statuses in their project workflow.
Nash has updated the default board filter to the JQL below:
project in (HR, Finance) ORDER BY Rank ASC
A few issues are missing from the Jira board.
What are the best solutions for this issue? (Choose two.)
- A . Update the quick filter.
- B . Update the Jira workflow.
- C . Update the board column.
- D . Update the board filter.
C D
Explanation:
If some issues are missing from the Jira board even though Nash has updated the board filter to include both projects, it’s likely due to the board’s configuration. Here are the two best solutions:
C. Update the board column.
Jira boards are configured to map each column to one or more statuses. If a status used in either of the two projects’ workflows is not mapped to a column in this board, issues with that status will not appear. Nash can solve this problem by adjusting the column configuration to ensure all statuses used in these projects are mapped to a column.
D. Update the board filter.
While Nash has included both projects in his filter, there might be other criteria in the filter that are excluding the missing issues. Nash should review the filter query to ensure it includes all the necessary criteria to capture all relevant issues from both projects.
Please note, Updating the quick filter (A) would only affect the issues displayed temporarily, it wouldn’t solve the issue of missing tasks. Updating the Jira workflow (B) is a more substantial change that should not be necessary in this case, as the issue is likely with the board’s configuration rather than the workflows of the individual projects.
Which of the following are false about the roadmap? (Choose three.)
- A . Users can choose which epics they want to display on the dashboard. Either Complete or Incomplete.
- B . Users can change the view setting to customize their roadmap’s view. The changes will apply to all users that have access to that project.
- C . Schedule bars for child issues are currently available for scrum teams only.
- D . Users can customize epic’s color directly from the roadmap.
- E . Users can change the epic bar timeline to weeks, months, quarters, or yearly.
A,B,E
Explanation:
As of my last training cut-off in September 2021, in terms of Jira’s roadmap feature, the following statements are false:
B. Users can change the view setting to customize their roadmap’s view. The changes will apply to all users that have access to that project.
In fact, the roadmap view settings are user-specific. This means if one user changes their view setting, it will not apply to all users that have access to the project. Each user can customize their own view.
C. Schedule bars for child issues are currently available for scrum teams only.
This is false. Schedule bars for child issues (like stories or tasks under an epic) are not available in the roadmap, regardless of the team type (Scrum or Kanban). The roadmap generally focuses on the epic level.
E. Users can change the epic bar timeline to weeks, months, quarters, or yearly.
This statement is also false. As of my last update, the roadmap view in Jira does not provide options to change the time scale of the roadmap to weeks, months, quarters, or yearly.
Remember to always refer to the most recent Atlassian documentation to confirm whether these capabilities have been added or changed since my last update.
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.)
- 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.
C,F
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.
Which of the following is false about creating boards?
- A . Users can create a new board from existing Jira projects.
- B . Users can create a new board from the existing Saved Filter.
- C . Users cannot create a board with multiple projects, but they can add more projects once they create the board.
- D . Users can create a new board while creating a new Jira Software project.
C
Explanation:
This is not true. Users can definitely create a board that includes multiple projects. The filter for a board can include any valid JQL query, which can certainly involve multiple projects. For instance, you could set the filter query to project in (ProjectA, ProjectB, ProjectC) when you create the board, and it will include issues from all of those projects.
Which of the following are true about ranking parent issues and sub-tasks? (Choose two.)
- A . Sub-tasks will follow the parent issues’ ranking.
- B . Sub-tasks will have a different rank than the parent issues.
- C . Users need to rank all of the sub-tasks before ranking the parent issue.
- D . Sub-tasks can be ranked in relation to their sibling issues.
B,D
Explanation:
Ranking in Jira allows issues to be ordered by importance or priority. Regarding the ranking of parent issues and sub-tasks, the following statements are true:
B. Sub-tasks will have a different rank than the parent issues.
Sub-tasks can have their own independent ranking different from their parent issues. This allows sub-tasks to be ordered separately, and it’s not required to follow the ranking of the parent issue.
D. Sub-tasks can be ranked in relation to their sibling issues.
Sub-tasks can indeed be ranked in relation to their sibling issues. This means that sub-tasks within a parent issue can be ordered based on their own priority or importance.
Please note, while the ranking of a parent issue can influence the overall priority of the work, it doesn’t directly determine the ranking of the sub-tasks (A). Similarly, it’s not necessary to rank all of the sub-tasks before ranking the parent issue (C).
Which Jira user type is the most suitable for Nash for the following responsibilities?
– Manage project roles membership.
– Update project details and basic settings.
– Manage boards and field layout.
- A . Project administrator
- B . Jira Software users
- C . Site administrator
- D . Jira administrator
A
Explanation:
Site administrators:
– Usually someone that has the authority to manage the team’s finances.
– Manage new users.
– Manage billing and subscriptions.
– Manage site settings.
Jira administrators:
– Usually someone that has good technical knowledge in Jira.
– Manage Jira plugins.
– Manage Jira global configurations (Global permissions, global settings, etc).
– Manage Jira schemes (Workflow, permissions, screens, notifications, etc).
Project administrators:
– Usually someone that is managing a specific Jira project.
– Manage project configurations (Roles, project details, etc).
Jira Software users:
– Users that are working on issues in the Jira Software project.
– Users’ permissions are being managed by other administrators.
Nash is creating a new Scrum board with multiple Jira projects. Each project has a different status in its workflow.
Which of the following are true? (Choose two.)
- A . Some issues will be hidden from the board.
- B . The user cannot create a new board with multiple Jira projects.
- C . All statuses will be mapped to 3 default columns: To Do, In Progress, and Done
- D . All issues will be hidden from thewwwboard.dumpspanda..com
- E . The status will be mapped to the first selected project when creating the new board.
A C
Explanation:
Razi is the Jira administrator for the WINDOWS Jira project. He received a new request to create a new Jira project called LINUX, and both projects need to have the same configurations.
Razi created the LINUX Jira project using the shared configuration option to ensure both projects have the same configurations.
Assuming the WINDOWS project is already configured with all of the below configurations, which configurations does Razi have to update in the LINUX project manually? (Choose three.)
- A . Status
- B . Project Avatar
- C . Version
- D . Priority
- E . Notification
- F . Components
B C F
Explanation:
When a Jira administrator creates a new project and chooses the "Share configurations" option with another project, most settings are duplicated in the new project. However, certain project-specific details are not copied over. In this case, Razi would have to manually update the following configurations in the LINUX project:
B. Project Avatar
Project avatars are unique to each project and are not copied over when sharing configurations. Therefore, Razi would have to manually set an avatar for the LINUX project.
C. Version
Versions are unique identifiers used for releases within a project. These are project-specific and are not copied over when configurations are shared. Razi will need to manually create versions for the LINUX project.
F. Components
Components are also project-specific and are used to group issues within a project. These are not shared between projects, even when using the shared configuration option. Thus, Razi will have to manually create any needed components in the LINUX project.
Statuses (A), priorities (D), and notifications (E) are part of the shared configurations and would be the same in both the WINDOWS and LINUX projects, assuming the shared configuration option was used when the LINUX project was created.
Which JQL query can users use to get a list of issues in the current sprint for the "Udemy" project?
- A . project = "Udemy" AND Sprint in openSprints()
- B . project = "Udemy" AND Sprint in activeSprint()
- C . project = "Udemy" AND Sprint = activeSprint()
- D . project = "Udemy" AND Sprint = openSprints()
A
Explanation:
The answer is project = "Udemy" AND Sprint in openSprints(). activeSprint() does not exist.
These are the only valid query for the sprint:
– openSprints()
– closedSprints()
– futureSprints()
You cannot use equal sign ‘=’ with openStrings().
You need to use ‘in openSprint()’.
Which of the following are part of the Jira Automation rules? (Choose three.)
- A . Listeners
- B . Conditions
- C . Triggers
- D . Actions
- E . Requirements
- F . Steps
B,C,D
Explanation:
Automation rules are made up of three parts:
Triggers (When):
Every rule starts with a trigger. They kick off the execution of your rules. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed.
Conditions (If/Else-if/Else):
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.
Actions (Then):
Actions are the doers of your rule. They allow you to automate tasks and make changes within your site and can perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks.
Users created a new custom field called Environment that has two values:
– Production
– Non-Production.
They need a table report to group issues from Production and Non-Production, and the overall status of those issues. The report should return a table containing three groups; issues with Production value, issues with Non-production value, and issues with a null value.
Which report is suitable for this use case?
- A . Time Since Issues Report
- B . Average Age Report
- C . Single Level Group By Report
- D . Resolution Time Report
- E . Pie Chart Report
- F . Time Tracking Report
C
Explanation:
Single Level Group By Report shows a table of issues grouped by a particular field (including custom fields) for a filter. This helps users group search results by a field and see the overall status of each group.
Which of the following indicates that the productivity of the team is increasing in Control Chart report? (Choose two.)
- A . Rolling average line showing a downtrend.
- B . More issues or a group of issues are below the average line.
- C . Rolling average line showing an uptrend.
- D . Rolling average line is consistently close to the average line.
- E . More issues or a group of issues are above the average line.
A,B
Explanation:
More issues or a group of issues below the average line shows that the team takes a shorter time to transition an issue from one status to another status.
If the rolling average is showing a downtrend, that means the team’s productivity is increasing because the time they took to close issues are getting shorter.
Dom created an issue in Project A. Now he wants to move the issue to Project B.
According to the information below, which of the following fields will retain their values after moving the issue to Project B? (Choose two.)
Project A custom fields:
– Custom Field A – Text Field (single line)
– Custom Field B – Text Field (single line)
– Custom Field C – Version picker
Project B custom fields:
– Custom Field A – Text Field (single line)
– Custom Field C – Version picker
- A . Custom Field A
- B . Components
- C . Fix Versions
- D . Labels
- E . Custom Field C
- F . Custom Field B
A,D
Explanation:
Component and version fields are project fields; not global fields. Therefore, those data will be permanently lost if users move issues between projects. This includes the Version Picker custom field. Other incompatible fields will also appear empty, even if users choose to retain their values.
In this example, only Labels and Custom Field A will retain their values:
– Labels’ values are shared globally.
– Custom Field A is compatible with Project B. Thus, Jira will retain its value.
– Project B does not have Custom Field B. Thus, Jira will not retain its value.
– Custom Field C is a version picker. Jira will not retain the version’s value.
Sarah created a new custom field called ‘Project Cost’. She cannot view the field in some of the issues.
Which of the following is true?
- A . ‘Project Cost’ value is empty.
- B . ‘Project Cost’ is one of the ‘Hidden fields’.
- C . She needs ‘Browse Projects’ permission.
- D . Some issues have ‘Issue Level Security’ applied.
B
Explanation:
Since Sarah can view the issue, she has the ‘Browse Projects’ permission and no ‘Issue Level Security’ has been applied.
‘Project Cost’ field is not one of the ‘Hidden fields’ because Sarah can view the ‘Project Cost’ field in other issues. If it was, the field will be hidden in all issues.
The correct answer is because the ‘Project Cost’ value is empty. If users place the field under the ‘HIDE WHEN EMPTY’ section, the field will not appear on the issue screen if their value is empty.
__________ listen to any events selected by users to start their automation rules.
- A . Conditions
- B . Listeners
- C . Triggers
- D . Steps
- E . Requirements
- F . Actions
C
Explanation:
Every rule starts with a trigger. They kick off the execution of your rules. Triggers will listen for events in Jira, such as when an issue is created or when a field value is changed.
Automation rules are made up of three parts:
– Triggers (When)
– Conditions (If/Else-if/Else)
– Actions (Then)
Razi accidentally deleted a column from the board. Assuming he has full access to manage the board, which of the following is true?
- A . The user cannot delete a column that contains at least one status.
- B . Statuses associated with that column will be deleted.
- C . Some issues will be deleted.
- D . All answers are incorrect.
- E . The number of issues in the report will change.
A
Explanation:
Razi’s team just completed their first sprint.
What can they learn from this chart? (Choose three.)
(Assume Remaining Estimate and Time Spent is disabled for this board.) This sprint ends with 0 story points.
- A . There are 2 issues resolved on July 8th.
- B . Some of the issues are still unresolved.
- C . This sprint starts with 20 story points.
- D . Some of the issues are resolved during non-working days.
- E . There are no scope changes in this sprint.
C,D,E
Explanation:
The grey area indicates days that are non-working days. Some issues were resolved during non-working days since story points were reduced in the grey area.
This chart starts drawing the ‘guideline’ and ‘remaining values’ lines at the 20 story points on the y-axis.
Meaning, this sprint starts with 20 story points.
The ‘remaining values’ line ends with 2.5 story points. Therefore, some issues are still unresolved in this sprint.
Story points do not increase during this sprint. Since the remaining estimate and time spent is disabled for this board, scope change is not indicated in the Burndown Chart for the subtask. We cannot confirm if there are no scope changes in this sprint.
According to the components below, who will be the assignee if a user created a ticket with all these components?
Project lead: Razi
Project default assignee: Project Lead
- A . Nina
- B . Razi
- C . Nick
- D . Dom
- E . Unassigned
C
Explanation:
A component default assignee will override the project’s overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that is first alphabetically.
A Jira workflow contains 3 statuses; To Do, In Progress, and Done.
Which of the following JQL will return issues that have never been in ‘Done’ status?
- A . resolution != null
- B . status was not Done
- C . resolution is EMPTY
- D . status != Done
- E . status was in ("To Do", "In Progress")
B
Explanation:
status was not Done will return issues that have never been in ‘Done’ status before.
resolution != null will return resolved issues.
resolution is EMPTY will return unresolved issues.
status != Done will return issues that are not currently in ‘Done’ status, which are issues in ‘To Do’ and ‘In Progress’.
status was in ("To Do", "In Progress") will return issues that have been in ‘To Do’ or ‘In Progress’ status.
Nina recently joined as a finance manager. Her team already has a few Jira projects running that is related to finance projects. She needs to create a new project using the same configurations as the other finance projects.
Below is the configuration she used to create the project.
What will happen to Nina’s Jira project (RMC) if the team that is managing the USC project changed their Jira configuration?
- A . Any changes with the other team’s Jira project will automatically apply to Nina’s Jira project.
- B . Nina has permission to accept the configuration changes if she needs them.
- C . All answers are incorrect.
- D . Nothing will happen. Jira will only apply the configuration changes at the initial Jira project creation.
D
Explanation:
In Jira, when you create a project by sharing configurations with another project, only the configurations at the time of creation are shared. Any subsequent changes to the original project’s configurations won’t affect the project that was created with shared configurations. This allows project configurations to evolve independently over time, even if they started from a common point.
Which of the following are suitable scenarios to use Jira group? (Choose four.)
- A . Members of the group are responsible for making bulk changes on multiple issues.
- B . The project administrator will manage group membership.
- C . Same users will be working on multiple projects.
- D . Permission can be managed at the global level.
- E . The site administrator will manage group membership.
- F . Team members require ‘Work On Issues’ permission to log work done.
A C D E
Explanation:
Jira groups are often used to manage permissions at a broader level. They are useful when you have a set of users who will be working on multiple projects (C) or when certain users need the ability to make bulk changes on multiple issues (A).
Jira group memberships are managed by the site administrator (E), not project administrators. This is because groups exist across the entire site and can be used to control access and permissions across multiple projects.
Using Jira groups also allows permissions to be managed at the global level (D), so you can quickly and easily assign the same permissions to multiple users.
However, the ‘Work On Issues’ permission is typically managed at the project level, not through groups, so option F is not a suitable scenario for using a Jira group.
Nash recently joined the team as a scrum master.
Which permission will allow Nash to perform the below actions? (Choose four.)
– Manage version
– Manage component
– Manage sprint
– Edit an issue’s due date
- A . Administer Projects
- B . Manage Sprints
- C . Schedule Issues
- D . Edit Issues
- E . Manage Versions
- F . Manage Components
B C E F
Explanation:
The actions Nash needs to perform map to the following permissions:
Manage version: This requires the "Manage Versions" permission (E).
Manage component: This requires the "Manage Components" permission (F).
Manage sprint: This requires the "Manage Sprints" permission (B).
Edit an issue’s due date: This requires the "Schedule Issues" permission (C).
Please note that granting the "Administer Projects" permission (A) would also enable Nash to perform all of these actions, but this permission provides access to many additional actions as well, which may be beyond what is needed in this scenario. It’s generally best practice to grant the least permissions necessary for a user to perform their job to minimize risk.
Which of the following can be explained from the chart below?
- A . Users have not started the sprint yet.
- B . Users deleted the sprint.
- C . Users closed some issues the moment the sprint started.
- D . There are no issues in the sprint.
C
Explanation:
If the grey ‘guideline’ line does not show, the sprint may have been started before any issues were assigned to it.
In this case, since the grey ‘guideline’ line does show up in the chart, the sprint already started. The ‘remaining values’ line indicates that someone closed some issues that are worth 5 story points as soon as they started their sprint.
Which of the following are true about card layout customization? (Choose three.)
- A . Only board administrators can customize the cards.
- B . Users can enable the ‘days in column’ to show a series of dots on the card, representing how long the card has been in a particular column.
- C . Jira will apply the customization to the current board only.
- D . Users can have a separate card layout for backlog and active sprints for the Scrum board.
- E . Users can add extra custom fields – up to 5 fields.
A C E
Explanation:
The following statements are true about card layout customization:
Razi’s team and Dom’s team are working on the same backlog, but they have their own active sprint.
Which of the following are true about parallel sprints? (Choose three.)
- A . If users want to complete active sprint A with unresolved issues, they cannot move it to active sprint B.
- B . Project administrators can disable the parallel sprint feature for their projects.
- C . Users cannot complete multiple active sprints at once.
- D . Users can run up to 2 parallel sprints only.
- E . Users cannot have a separate velocity chart for each team.
A,C,E
Explanation:
The parallel sprints feature lets users enable multiple active sprints that are running parallel to each other. For example, if they have two teams working on the same backlog, each team can now work on their own active sprint simultaneously.
Users can only complete one sprint at a time.
Atlassian does not mention whether there are limits on how many sprints users can run in parallel, however it is possible for users to run more than two parallel sprints.
Users cannot have a separate velocity chart for each team.
Sprint feature can be enabled/disabled from the global settings. Only Jira administrators have access to control it.
If there are unresolved issues in the current active sprint and users want to complete the sprint, users can only move them to inactive sprint or backlog. They cannot move them to other active sprints.
Nina found that the roadmap no longer appears on her board.
Which of the following is the possible cause for this problem?
Note:
– Company-managed projects are formerly known as classic projects.
– Team-managed projects are formerly known as next-gen projects.
- A . Roadmap is disabled by the site administrator.
- B . There is no Epic created in the project.
- C . Nina does not have ‘View Read-Only Workflow’ permission.
- D . Board Filters contains multiple projects.
- E . Nina is using a team-managed project. Roadmap only exists in company-managed Jira projects.
A D E
Explanation:
The possible cause for the problem that Nina is facing could be:
Nick’s Team is responsible for developing a new mobile application for their client. Each module will be delivered continuously to the client until they complete the project.
Which of the following Jira Software template is suitable for Nick’s Team?
- A . Project management
- B . Kanban
- C . Scrum
- D . IT service management
- E . Bug Tracking
B
Explanation:
Kanban is designed for teams who are focused on continuous delivery and who wish to visualize the entire workflow to monitor progress and bottlenecks. This methodology allows work to be pulled into the workflow as capacity allows, rather than being planned for and pushed in, as in the Scrum methodology.
Note that the best methodology always depends on the specific team and project dynamics. For some teams, a Scrum or hybrid approach might also work well.
Which field is suitable for the requirements below? (Choose two.)
– Can be shared globally
– Users can select only a single value
– Must have a default value
– Can have different options for different projects.
- A . Radio Button
- B . Components
- C . Text Field (single line)
- D . Checkboxes
- E . Labels
- F . Select List (single choice)
A,F
Explanation:
Both these fields allow users to select a single value and can have a default value. These field types can also be used across different projects. Additionally, the options available in the select list or radio buttons can vary depending on the configuration of the field context, allowing different options for different projects.
According to the components below, who will be the assignee if a user created a ticket with all these components?
Project lead: Razi
Project default assignee: Unassigned
- A . Dom
- B . Nina
- C . Razi
- D . Unassigned
- E . Nick
A
Explanation:
A component default assignee will override the project’s overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that is first alphabetically.
Based on the component configuration, the default assignee will be the component lead. Since the user selected all 3 components, Jira will choose the component lead that comes first alphabetically.
Which of the following are true about labels? (Choose four.)
- A . Labels are unreliable for searching issues.
- B . Labels can only be accessed at the project level.
- C . Users cannot use labels in the report.
- D . Users can use the ‘Bulk Change’ tool to change labels’ values.
- E . Only project administrators can create new labels.
- F . Labels might contain inconsistent values.
Given the scenarios below, which project type is suitable for this project?
– Project should be maintained by the project team.
– Users are working on a smaller-scale project.
– Each project should have its own unique configuration.
– Users do not require complex Jira workflow.
– Users’ permissions require minimum maintenance.
Note:
– Company-managed projects are formerly known as classic projects.
– Team-managed projects are formerly known as next-gen projects.
- A . Company-managed project
- B . Team-managed project
B
Explanation:
Reasoning: Team-managed projects in Jira were designed for teams that want to work autonomously and have their project management practices independent of other teams in the organization. These projects have simplified workflows and configurations which can be easily maintained by the project team itself. They are ideal for smaller-scale projects and require less maintenance in terms of permissions.
According to the components below, who will be the assignee if a user created a ticket with all components?
Project lead: Razi
Project default assignee: Unassigned
- A . Nina
- B . Razi
- C . Nick
- D . Unassigned
- E . Dom
C
Explanation:
A component default assignee will override the project’s overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that is first alphabetically.
Since component ‘Java’ default assignee is ‘Project default’, Jira will skip this and look for the next component lead alphabetically, which is Nick.
Note: The ‘Create component’ button is only available to the Jira and Project Administrator.
Reference: Select a default assignee
If the image below is not visible, right-click it then select ‘Open image in new tab’.
Nash is using Kanban boards for his development projects. There are too many issues in the ‘Done’ column in one of the boards. He only wants to see completed issues for the current week.
Which of the following is the best feature that he should use to achieve this?
- A . Board Filter
- B . Swimlanes
- C . Hide completed issues
- D . Quick Filters
- E . Issue Detail View
- F . Board Sub-Filter
F
Explanation:
Reasoning: The sub-filter is a JQL (Jira Query Language) query used in configuring boards, particularly Kanban boards, that controls which issues are displayed on the board after applying the main board filter. In this scenario, Nash can use the sub-filter to only show issues in the ‘Done’ column that were completed in the current week.
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
C
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.
Razi works as a technical lead for the Cloud Team. He wants to customize his board to show cloud-related issues at the top row, followed by other issues.
Which feature can he use to achieve this?
- A . Quick Filters
- B . Issue Detail View
- C . Board Filter
- D . Hide Completed Issues
- E . Board Sub-Filter
- F . Swimlanes
F
Explanation:
Razi should use the Swimlanes feature to group issues in the board row. Grouped issues can also be sorted by the user. There are a few types of Swimlanes; Queries, Stories, Assignees, Epics, Projects, or None. If you choose None, no swimlanes will be displayed.
JQL search results from the Board Filter will apply to Jira boards and reports.
JQL search results from the Board Sub-Filter will apply to Jira boards only. (exists in Kanban boards only)
Quick Filters can be used to further filter issues in the board based on the additional JQL. Quick Filters JQL
will not overwrite JQL in your Board Filterwww.Jira.dumpspandaplywill the JQL.comntop of your existing JQL Board Filter.
Hide Completed Issues allow users to hide completed issues older than 1 week, 2 weeks, or 4 weeks. (exists in Kanban boards only)
Issue Detail View allows users to choose which field appears on the issues.
Sarah’s Team is responsible for developing a web application for their client. The modules will be delivered to the client batch by batch every two weeks.
Which of the following Jira Software template is suitable for Sarah’s Team?
- A . Kanban
- B . IT service management
- C . Project management
- D . Scrum
- E . Bug Tracking
D
Explanation:
The Scrum framework is commonly used for product development by teams who work iteratively in sprints, usually 1-4 weeks long. This would allow Sarah’s team to plan, develop, test, and deliver the modules batch by batch every two weeks as per the client’s requirements.
Which of the following are true about the Jira board? (Choose two.)
- A . Only the Scrum board can use ‘Hide completed issues’
- B . Only the Kanban board can use ‘Quick Filters’
- C . Only the Scrum board can use ‘Quick Filters’
- D . Both Kanban and Scrum boards can use ‘Hide completed issues’
- E . Both Kanban and Scrum board can use ‘Quick Filters’
- F . Only the Kanban board can use ‘Hide completed issues’
D E
Explanation:
Quick Filters are a feature of both Scrum and Kanban boards that allow users to filter the view of the board to see only the issues they want. The ‘Hide completed issues’ feature is also available on both types of boards, allowing users to hide issues that are marked as done to reduce clutter.