How to pass the ACP-120 Jira Administration in the Cloud certification exam

As a scrum master at Orbit Agile, Lara needs a JQL expression to retrieve all Jira issues that do not have any labels. Which JQL will return those issues? (Choose 4)

• ❏ A. labels = ”

• ❏ B. labels = null

• ❏ C. labels is EMPTY

• ❏ D. labels = “”

• ❏ E. labels in (null)

• ❏ F. labels = EMPTY

Which methods can be used to create swimlanes on an organization-managed board in Jira when configuring the board layout? (Choose 5)

• ❏ A. Queries

• ❏ B. Components

• ❏ C. Epics

• ❏ D. Issue types

• ❏ E. Projects

• ❏ F. Assignees

• ❏ G. Stories

A midsize development team is assessing Advanced Roadmaps in Jira which of the following capabilities does it offer?

• ❏ A. Pivot or persevere guidance

• ❏ B. Custom hierarchy levels enabling parent items above epics

• ❏ C. Epic balancing report

• ❏ D. Program increment planning support

Which project attributes can a project administrator modify from the project details page of an organization managed project? (Choose 3)

• ❏ A. Project identifier

• ❏ B. Project description

• ❏ C. Project title

• ❏ D. Workflow scheme

• ❏ E. Assigned project lead

• ❏ F. Project grouping

At Nimbus Labs a team is auditing project permissions in their issue tracker and they want to confirm which statements about those permissions are accurate. Which of the following statements about project permissions are correct? (Choose 3)

• ❏ A. The ‘Move Issues’ permission allows changing an issue’s status from one state to another

• ❏ B. The ‘Resolve Issues’ permission allows a user to reopen an issue that was previously resolved

• ❏ C. The ‘View Development Tools’ permission is required to see the sprint board for a project

• ❏ D. The ‘Resolve Issues’ permission is required to set the Release version field on an issue

• ❏ E. The ‘Transition Issues’ permission is needed to populate the Release version field when changing an issue’s status

• ❏ F. The ‘Manage Sprints’ permission is required to complete a sprint from the sprint board

Which board estimation settings ensure that when issues are completed their full story point estimates are deducted from the sprint total? (Choose 2)

• ❏ A. Create a numeric custom field and use it as the estimation metric

• ❏ B. Set Estimation statistic to Story Points

• ❏ C. Enable time tracking for the board

• ❏ D. Set Estimation Time tracking to No time tracking

Ravi must create a JQL filter that returns every issue in the team managed project “ORION” while excluding any issues that reference the archived fix version “1.2.3” What JQL expression fulfills this requirement?

• ❏ A. project = ORION AND fixVersion not in (“1.2.3”)

• ❏ B. project = ORION AND (fixVersion is EMPTY OR fixVersion != “1.2.3”)

• ❏ C. project = ORION AND fixVersion != “1.2.3”

• ❏ D. project = ORION AND fixVersion is not “1.2.3”

Sophia cannot open agile reports on the company managed Scrum board for project “CORE” in her team. What are two possible reasons she cannot view those reports? (Choose 2)

• ❏ A. Sophia is missing the “Manage sprints” project permission

• ❏ B. The saved filter that the board relies on is not shared with Sophia

• ❏ C. There is no “View reports” project permission configured

• ❏ D. An issue security scheme is restricting Sophia from seeing the issues on the board

• ❏ E. Sophia lacks the “Browse projects” permission on the project

• ❏ F. Sophia is not listed as a board administrator

Maya and Omar lead two squads that share a single backlog and they want to run their sprints at the same time. Which statements about parallel sprints are accurate? (Choose 3)

• ❏ A. When finishing an active sprint you can move unresolved issues into another active sprint

• ❏ B. It is not possible for each squad to have its own separate velocity report when they use parallel sprints

• ❏ C. Board level settings determine whether parallel sprints are available

• ❏ D. Both company-managed projects and team-managed projects allow parallel sprints

• ❏ E. A project administrator can enable or disable parallel sprints for a company-managed project

• ❏ F. Users cannot finish more than one active sprint at the same time

A release manager at SolaceWorks wants to assess how close the time estimates were for tasks assigned to release “2.0”. Which report should she run?

• ❏ A. Average age report

• ❏ B. Time tracking report

• ❏ C. Resolution time report

• ❏ D. Version workload report

The company managed Scrum project “ORION” has these project roles and permissions. Browse projects is granted to Project Role Team Leads. Edit issues is granted to Project Role Engineers. Create attachments is granted to Project Role Legal. Delete all attachments is granted to Project Role Auditors. Delete own attachments is granted to Project Role Contributors. Delete issues is granted to Project Role Administrators. Ashley must be able to add and remove PDF files on issues in the “ORION” project. How many project roles must be assigned to Ashley at a minimum?

• ❏ A. Four roles

• ❏ B. Two roles

• ❏ C. Three roles

• ❏ D. Five roles

On a board that uses the simplified workflow and already has a column named “In Progress” what happens if you add a new column named “In Progress” immediately after Backlog?

• ❏ A. The board prevents adding a column with the same name

• ❏ B. The new column can be added and it will have no status mapped to it

• ❏ C. The existing status will automatically map to the new column

Jordan is building a mobile client for BrightLearn Inc and he wants everyone at BrightLearn to be able to comment on the project issues while only developers he adds can create new issues. He plans to set up a team managed project. Which access level should Jordan select to meet these requirements?

• ❏ A. Restricted

• ❏ B. Public

• ❏ C. Limited

• ❏ D. Individual

• ❏ E. Open

• ❏ F. Private

The project settings for the company project “NOVA” are as follows. The project lead is Claire and the default assignee is Project Lead. Component settings list Serverless with lead Rina and default assignee Component Lead. Database has lead Marcus and default assignee Project Lead. Insights has lead Elena and default assignee Project Default. Ledger has lead Javier and default assignee Unassigned. You create a new issue while selecting the components “Ledger” and “Insights” and you leave the assignee set to “Automatic”. Who will be assigned the new issue?

• ❏ A. Claire

• ❏ B. Elena

• ❏ C. Unassigned

• ❏ D. Javier

Which statements accurately describe company-controlled Jira boards used by teams within an organization? (Choose 3)

• ❏ A. Users cannot create a Kanban board in a project that uses Scrum workflows

• ❏ B. Users can add a Scrum board inside a project that is configured for Kanban

• ❏ C. Boards are hard linked to project templates and cannot be modified without recreating the project

• ❏ D. Users can create a Kanban board in a project that uses Scrum practices

• ❏ E. A board is only a view of issues and teams can create multiple Scrum or Kanban boards in any company-managed project

• ❏ F. Users are prevented from having both Kanban and Scrum boards in the same project

In a Jira Cloud project at BlueVertex which elements make up an automation rule and determine when it runs and what it does? (Choose 3)

• ❏ A. Cloud Pub/Sub

• ❏ B. Rule conditions

• ❏ C. Event triggers

• ❏ D. Workflow validators

• ❏ E. Action steps

• ❏ F. Event listeners

Marisol at Cedarwood Analytics has noticed a steady pileup of unresolved tickets every month and she is forming a small task team to tackle the backlog. She requires a dashboard visualization that shows how many tickets are created each month and how many of those created tickets remain unresolved. Which dashboard gadget provides this view?

• ❏ A. Average Age Chart

• ❏ B. Filter Results

• ❏ C. Recently Created Chart

• ❏ D. Resolution Time

Which of the following statements about team managed projects are true? (Choose 3)

• ❏ A. Users can apply custom filters on a team managed board to narrow issue lists

• ❏ B. A team managed project can export its configuration to other projects

• ❏ C. Any user with a product license can create and manage a team managed project

• ❏ D. Project members can define custom roles in a team managed project

Maya wants clearer visibility of the component field due date and the created date on her Kanban board. Which setting should she change?

• ❏ A. Columns configuration

• ❏ B. Card colours

• ❏ C. Issue detail view

• ❏ D. Card layout settings

Mina was given requirements for new custom fields at VerdantTech. The fields must be available across all projects, allow only a single selection by a user, include a predefined default value, and support different option sets per project. Which custom field types satisfy these criteria? (Choose 2)

• ❏ A. Components

• ❏ B. Labels

• ❏ C. Select List (single choice)

• ❏ D. Checkbox

• ❏ E. Radio Button

A delivery team at Meridian Studios has created a company managed Kanban project named Artifacts that uses a shared configuration. Which project configuration elements are part of the shared configuration? (Choose 4)

• ❏ A. Workflow scheme

• ❏ B. Project board

• ❏ C. Notification scheme

• ❏ D. Components

• ❏ E. Issue security scheme

• ❏ F. Project navigation

• ❏ G. Issue types

• ❏ H. Project roles membership

Which roles can manage a Jira board for a development group in a Scrumwise Cloud instance at scrumtuous.com? (Choose 4)

• ❏ A. Project administrator role

• ❏ B. Site administrator role

• ❏ C. Original board creator

• ❏ D. Jira administrator role

• ❏ E. Board administrator role

A product team at SprintLab uses the Sequence view which was previously called the roadmap in SprintBoard Cloud. Which of the following statements about the Sequence view are accurate? (Choose 4)

• ❏ A. The Sequence view allows filtering epics and issues by priority

• ❏ B. Users can create new issues directly from the Sequence view

• ❏ C. The Sequence view supports filtering epics and issues by sprint

• ❏ D. Users can add comments from within the Sequence view

• ❏ E. The Sequence view lets users filter epics and issues by status

• ❏ F. Users can filter epics and issues by assignee in the Sequence view

Which Jira dashboard gadgets display issues for the currently logged in user without requiring a saved filter or a project selection? (Choose 3)

• ❏ A. Filter Results gadget

• ❏ B. Issues in progress

• ❏ C. Watched issues

• ❏ D. Assigned to me

You administer a company controlled Kanban board for Marigold Solutions and you recently promoted Maya to be a board administrator. She adjusted most board settings however she is unable to modify the saved filter that the board uses. What is preventing her from changing the filter query?

• ❏ A. The saved filter is owned by another user and not shared with Maya

• ❏ B. Maya needs to be added as an Editor of the saved filter

• ❏ C. Maya lacks a project permission that would let her edit the filter

• ❏ D. Maya lacks a global permission related to filters

While building an automation workflow for a project at Bluewater Labs you wonder if there is a cap on how many “IF/ELSE” blocks you can include and whether there is a separate cap on the total number of components permitted in a single rule?

• ❏ A. There is a cap on the number of “IF/ELSE” blocks and there is also a cap on the total components in one rule

• ❏ B. There is no cap on “IF/ELSE” blocks and there is also no cap on the total components in one rule

• ❏ C. There is no cap on the number of “IF/ELSE” blocks but there is an overall cap of 48 components per rule

• ❏ D. There is a cap on the number of “IF/ELSE” blocks but there is no cap on the total components in a single rule

When a team member has the Resolve Issues project permission which system field are they allowed to modify?

• ❏ A. Alter the system field Due Date

• ❏ B. Modify the system field Fix Versions

• ❏ C. Edit the system field Resolution

• ❏ D. Update the custom field Resolution Reason

Rosa oversees a company managed project at Horizonix and she needs three distinct functional teams to work inside the same project without heavy configuration. Each team must only see and work on its own issues and each team needs a burnup chart that reflects only its issues. As the project administrator what project configuration best satisfies these requirements?

• ❏ A. Use labels to mark each functional team and create three separate boards each filtered by its team label

• ❏ B. Use versions to indicate functional areas and create a single board with swimlanes arranged by version

• ❏ C. Assign components to represent each functional team and build three boards each filtered by its component

• ❏ D. Create a new custom field for functional area and use a single board with three quick filters driven by that field

A product group at NovaTech has asked you to create a project that offers a backlog and an Agile board for daily prioritization, supports seven day sprint iterations, and allows the project administrator to rename workflow status labels. The project must provide these capabilities immediately after creation without enabling extra features. Which project type and template should you create?

• ❏ A. Company-managed project with Scrum template

• ❏ B. Company-managed project with Kanban template

• ❏ C. Team-managed project with Kanban template

• ❏ D. No Jira project type can satisfy all requirements

• ❏ E. Team-managed project using Scrum template

Which of the following statements about parallel sprints is incorrect?

• ❏ A. Each squad requires a separate backlog for parallel sprints

• ❏ B. The tool lets you complete all active sprints in one operation

• ❏ C. Teams must use the same estimation scale for their work

• ❏ D. The Velocity Chart will not display velocity broken down by squad

A product team at Meridian Labs added a custom field called “Role” with the values Lead and Staff. They want a visual chart that groups issues into Lead and Staff and then applies a saved filter. Which report will produce that visualization?

• ❏ A. Time Since Issues Report

• ❏ B. Average Age Report

• ❏ C. Time Tracking Report

• ❏ D. Single Level Group By Report

• ❏ E. Resolution Time Report

• ❏ F. Pie Chart Report

During the current sprint at Meridian Apps the team committed to 12 issues but they were only able to finish 6 of them. What will happen to the six incomplete issues when the team completes the sprint? (Choose 2)

• ❏ A. Unresolved issues are archived

• ❏ B. Move them into the upcoming sprint

• ❏ C. They are removed from the board

• ❏ D. Move them to the backlog

• ❏ E. Move them directly to another active sprint

Priya can open every issue in the Agile project but she cannot reorder items in the backlog on the Scrum board. Which project permissions should she request to gain that capability? (Choose 2)

• ❏ A. Manage sprints

• ❏ B. Schedule issues

• ❏ C. Administer projects

• ❏ D. Edit issues

• ❏ E. View development tools

• ❏ F. Browse projects

Lara is a Test Lead at an engineering firm and she manages automation work on a Scrum board, but the board contains many issues that belong to other squads. Which board feature will allow her to show only the issues assigned to her team? (Choose 2)

• ❏ A. Issue Detail View

• ❏ B. Quick Filters

• ❏ C. Saved Filters

• ❏ D. Board Sub Filter

• ❏ E. Swimlanes

• ❏ F. Board Filter

Diego created an automation that notifies his team every week about issues that remain unresolved, and the notification runs on a schedule. Which component must this automation include?

• ❏ A. Smart values

• ❏ B. Condition

• ❏ C. Trigger

• ❏ D. Send Slack message

Which permissions are required to bulk update the “Component/s” field on closed issues in a company managed Kanban board? (Choose 2)

• ❏ A. “Browse projects” project permission

• ❏ B. “Edit issues” project permission

• ❏ C. “Manage project roles” project permission

• ❏ D. “Make bulk changes” global permission

Brightline Solutions completed a migration from Jira Software Server to Jira Software Cloud Premium and teams want to learn which Advanced Roadmaps for Jira capability helps them implement agile at scale. Which statement is true?

• ❏ A. Import issues from external systems and other Jira sites to build a plan

• ❏ B. Save personalized plan views for different audiences

• ❏ C. Link budget and financial figures directly to plans

• ❏ D. Consolidate data from multiple Jira Cloud instances into a single plan

Sofia created a new Scrum board for her squad and configured it to match their process. She updated the board filter, added new tasks, uploaded attachments, set due dates, and assigned tasks to herself. When she tried to reorder stories in the Backlog by dragging them during planning she could not change their order. What is causing this problem?

• ❏ A. The board filter does not include the ranking field

• ❏ B. Sofia needs Schedule Issues project permission

• ❏ C. Sofia lacks Jira Software product access

• ❏ D. Sofia requires project administrator privileges

Maya created a new company-managed board from the “Create board” menu and selected the option “Board from an existing project” where she picked the company-managed Kanban project “ORION” which her team already has access to, yet when she shared the board URL her teammates could not open it, why did this happen?

• ❏ A. The team does not have the project permission Browse projects

• ❏ B. The board filter is private to Maya and not shared

• ❏ C. Maya does not have the global permission “Create Shared Objects”

• ❏ D. Maya is missing the project permission Administer projects

A delivery manager at HarborTech must set up a new Jira project for work that needs to be visible across multiple projects and that will receive ongoing bug fix releases. The team will not operate in fixed sprint cycles and they need a board that can include issues from other projects. Which project type should they choose?

• ❏ A. Team-managed Scrum project

• ❏ B. Company-managed Kanban project

• ❏ C. Team-managed Kanban project

• ❏ D. Company-managed Scrum project

Which statements correctly describe how a TaskBoard is managed in TrackerPro for a software delivery team? (Choose 3)

• ❏ A. The board filter hides issues from the TaskBoard while leaving report totals unchanged

• ❏ B. Releases listed in the backlog display only issues that satisfy the board filter

• ❏ C. Board managers can alter the board filter even if they are not the owner of the saved filter

• ❏ D. The board sub filter hides issues on the TaskBoard without affecting counts shown in external reports

• ❏ E. The count of Epics shown in the backlog is unaffected by the board filter

• ❏ F. A TrackerPro system administrator can create a new workflow status by adding a column on the board

Which of the following statements about sub tasks in Jira are accurate? (Choose 3)

• ❏ A. Sub tasks can contain their own sub tasks

• ❏ B. Administrators can disable the sub task feature

• ❏ C. The name and description for sub tasks can be localized for installed languages

• ❏ D. Users can convert a sub task into a standard issue type and convert standard issues into sub tasks

Priya oversees releases at Meridian Labs and she needs to confirm that her developers are meeting their original time estimates and that logged work matches expectations for ongoing tasks. Which report should she use to validate both original time estimates and time spent on tasks are progressing as planned?

• ❏ A. Pie Chart Report

• ❏ B. Time Since Issues Report

• ❏ C. Resolution Time Report

• ❏ D. Average Age Report

• ❏ E. Single Level Group By Report

• ❏ F. Time Tracking Report

A product team at NovaTask uses the timeline feature which was previously called Roadmap in Sprintly Cloud and they need to confirm its behaviors. Which of the following statements about the project timeline are untrue? (Choose 3)

• ❏ A. Altering the timeline view settings will change the perspective for everyone on the project

• ❏ B. Users can change an epic’s color directly on the timeline

• ❏ C. Completed epics are automatically removed from the timeline

• ❏ D. Child issue schedule bars are available for both Scrum and Kanban teams

• ❏ E. Users can switch the epic bar display to weeks months quarters or an annual view

Which JQL query will return the issues that are part of the current sprint for the “BrightLearn” project?

• ❏ A. project = “BrightLearn” AND Sprint = activeSprint()

• ❏ B. project = “BrightLearn” AND Sprint in openSprints()

• ❏ C. project = “BrightLearn” AND Sprint = openSprints()

• ❏ D. project = “BrightLearn” AND Sprint in futureSprints()

A release coordinator at Cedar Labs needs to configure an automation that adds a comment to every issue within a given Epic. Which automation branch should they use?

• ❏ A. Linked Issues

• ❏ B. Parent

• ❏ C. Children

• ❏ D. Epic (Parent)

• ❏ E. Sub-tasks

Maya must create a new project with the following constraints. Three separate squads will run sprints concurrently and the project must reuse the same custom fields that other projects already use in the company. Which project type should Maya select?

• ❏ A. Team-managed Kanban project

• ❏ B. Company-managed Kanban project

• ❏ C. Team-managed Scrum project

• ❏ D. Company-managed Scrum project

If you are a project administrator who does not have the global permission “Create shared objects” can you duplicate a project board and will the team retain view and edit access to the duplicate?

• ❏ A. You can duplicate the board but the copy will be private to you

• ❏ B. You can duplicate the board and the team will retain viewing and editing access to the copy

• ❏ C. You cannot duplicate the board without the global permission “Create shared objects”

In a Jira Cloud instance used by Meridian Labs which statement about project categories is accurate?

• ❏ A. A project category can be associated with only one project

• ❏ B. Both team-managed and company-managed projects can be assigned a project category

• ❏ C. Issue types can be linked to project categories

• ❏ D. Project administrators can create project categories

A delivery group at Orion Agile uses a hosted scrum instance and wants to identify which of the following names are not valid JQL functions for finding sprint related issues? (Choose 2)

• ❏ A. futureSprints()

• ❏ B. currentSprints()

• ❏ C. openSprints()

• ❏ D. closedSprints()

• ❏ E. nextSprints()

Who can update the configuration of a board that was built from an existing saved filter?

• ❏ A. Users who have been granted the Product Administrator role

• ❏ B. The Project Administrator for the project that contains the board

• ❏ C. The owner who created the saved filter

• ❏ D. Any account with Jira Software product access

A product team at HelixSoft is deciding whether to implement a custom field or a project component in their issue tracker. Which circumstances make a custom field the preferable choice? (Choose 3)

• ❏ A. The assignee must be automatically set based on the chosen value

• ❏ B. A site administrator will maintain and configure the field for use across projects

• ❏ C. The field should accept only a single selectable value

• ❏ D. A project administrator will be responsible for managing the field within their project

• ❏ E. Every project needs the ability to add this field to their issue screens

Marisol’s product group must set up a new Jira board. The team needs stories and tasks to follow independent workflows and they must be able to publish a release directly from the board when required. Which type of project fulfills all of these conditions?

• ❏ A. Team-managed Scrum board

• ❏ B. Team-managed Kanban board

• ❏ C. Company-managed Kanban board

• ❏ D. Company-managed Scrum board

Which changes cannot be made in a team-managed project? (Choose 2)

• ❏ A. Create a bespoke issue type for the project

• ❏ B. Introduce a screen transition into the project workflow

• ❏ C. Change project permissions scheme

• ❏ D. Add an “Affects versions” field to an issue type’s field list

Priya is the project lead for a team-managed project named “BRICK” where project access is set to “Restricted”. Priya added Maya to the project and gave her the “Member” role. Priya confirmed that Maya can create issues add comments attach files set due dates change the reporter and assign and edit issues yet Maya cannot rank issues. What should Priya do to allow Maya to rank issues?

• ❏ A. Grant Maya the “Administrator” role for the “BRICK” project

• ❏ B. Request that Maya be granted Jira Software product access

• ❏ C. Change the “BRICK” project type to a company managed project

• ❏ D. Assign Maya the “Work on BRICK issues” project permission

The correct answers are: labels = null, labels is EMPTY, labels in (null) and labels = EMPTY.

Jira Query Language treats missing or absent values as null or EMPTY and all four of the highlighted forms return issues that have no labels. Using labels = null directly checks for a null value. Using labels is EMPTY or labels = EMPTY uses the EMPTY keyword to find fields with no values. Using labels in (null) checks membership against null which is useful when combining the condition with other values in an IN clause.

labels = ” is incorrect because an empty quoted string is not the same as a null or EMPTY value in JQL and it will not reliably match issues that simply have no labels.

labels = “” is incorrect for the same reason and it is not a standard way in JQL to express a missing or empty field.

When you need to find issues with no value in a field use EMPTY or null in JQL rather than trying to match an empty quoted string.

Queries, Epics, Projects, Assignees, and Stories are correct methods to create swimlanes on an organization-managed board in Jira.

Queries lets you define swimlanes using JQL or saved filters so that each lane contains issues that match a specific query. This is useful when you need custom grouping that does not map to a single built in field.

Epics creates lanes for each epic so you can see all issues grouped under their parent epic on the board. This is commonly used to visualize progress by epic across the team.

Projects allows lanes to represent different projects when a board aggregates work from multiple projects. This makes cross project boards easier to scan by project scope.

Assignees groups issues by the person assigned so each lane corresponds to an owner. This helps with workload visibility and handoff tracking.

Stories creates lanes based on parent stories so subtasks or related issues are visually grouped under their story. This is helpful for teams that track work primarily at the story level.

Components is incorrect because component is not offered as a swimlane option in the board layout for organization-managed boards. Components can be used in filters and reports but not as a built in swimlane type.

Issue types is incorrect because grouping by issue type is not a swimlane choice in the board layout for organization-managed boards. You can filter or quick filter by issue type instead of creating lanes for them.

When the question specifies organization-managed boards remember the standard swimlane choices such as Queries, Epics, Projects, Assignees, and Stories and rule out fields like Components or Issue types that are not listed as swimlane options.

The correct option is Custom hierarchy levels enabling parent items above epics.

Custom hierarchy levels enabling parent items above epics is supported by Advanced Roadmaps because the product allows you to add and configure additional hierarchy levels above epics so that initiatives or other parent items can roll up work across multiple teams and projects. This hierarchy capability improves visibility for cross team planning and lets you aggregate estimates and view dependencies at higher portfolio levels.

Pivot or persevere guidance is incorrect because Advanced Roadmaps does not provide decision framework advice of that type. That phrase refers to product discovery or Lean Startup guidance rather than a built in planning or hierarchy feature in Jira.

Epic balancing report is incorrect because there is no specific feature named an epic balancing report. Advanced Roadmaps does offer capacity planning and scenario comparisons to help distribute work, but it does not provide a distinct report by that exact name.

Program increment planning support is incorrect as stated because Advanced Roadmaps does not advertise a dedicated program increment workflow. You can model multi sprint planning that resembles PI planning, but formal PI support and full SAFe tooling is generally handled by products like Jira Align or specialized PI planning tools.

When a question asks about Advanced Roadmaps focus on hierarchy and roll up capabilities and look for answers that match Atlassian documentation wording rather than generic management phrases.

The correct options are Project description, Project title, and Assigned project lead.

You can edit the Project title and the Project description from the project details page because these fields are basic project metadata that project administrators can update to reflect the project purpose and display name.

The Assigned project lead can also be changed on the project details page so that ownership and primary contact for the project are kept up to date without needing higher level administration.

Project identifier is not correct because the identifier or project key is typically set at creation and it is not a field you change on the project details page for an organization managed project. Changing identifiers usually requires additional administrative steps or site admin privileges.

Workflow scheme is not correct because workflows and their schemes are managed through the workflow or scheme administration areas and they are not edited from the basic project details page. Altering a workflow scheme often requires careful migration and higher permissions.

Project grouping is not correct because grouping or categorization is handled in other project management or administration screens and is not a detail editable from the project details page for organization managed projects.

When answering these questions look for whether the item is basic project metadata or an administrative scheme. Basic metadata like title, description, and project lead are usually editable by project admins while schemes and identifiers often need higher permissions.

The correct options are The ‘Resolve Issues’ permission allows a user to reopen an issue that was previously resolved, The ‘Resolve Issues’ permission is required to set the Release version field on an issue, and The ‘Manage Sprints’ permission is required to complete a sprint from the sprint board.

The Resolve Issues permission governs actions around resolving and reopening issues according to the workflow. Users who have that permission can perform resolution related transitions and reopen issues when the workflow and screens allow it.

The Resolve Issues permission is also relevant when the Release version field is populated as part of a resolution transition. If a workflow transition applies the release or fix version during resolution the ability to perform that resolution is controlled by the Resolve Issues permission rather than only a generic edit permission.

The Manage Sprints permission grants administrative sprint actions on a board such as starting, completing, and adjusting sprints. Completing a sprint from the sprint board requires this management level permission so it is correctly marked as required.

The ‘Move Issues’ permission allows changing an issue’s status from one state to another is incorrect. The Move Issues permission is used to move an issue between projects or change its issue type. Changing status is performed via workflow transitions and not by the move action.

The ‘View Development Tools’ permission is required to see the sprint board for a project is incorrect. The View Development Tools permission controls the visibility of linked development information and code artifacts. Access to boards and sprints is governed by board and project permissions such as browsing the project and board-specific permissions.

The ‘Transition Issues’ permission is needed to populate the Release version field when changing an issue’s status is incorrect. The Transition Issues permission lets a user execute workflow transitions, but whether a field like Release version is set during a transition can depend on the specific transition configuration and on the Resolve Issues permission or other field edit conditions.

When a question ties a permission to an action ask whether the action is a workflow transition or a board administration task. Look for words like resolve and manage to map actions to the appropriate permission.

The correct answers are Set Estimation statistic to Story Points and Set Estimation Time tracking to No time tracking.

When you choose Set Estimation statistic to Story Points the board calculates sprint totals and remaining work using story point values rather than time estimates. When you also choose Set Estimation Time tracking to No time tracking the board stops combining time based remaining estimates with story point totals so completed issues remove their story point value from the sprint remaining total as expected.

Create a numeric custom field and use it as the estimation metric is incorrect because boards expect the configured estimation statistic or the built in story points field for sprint calculations and a generic numeric custom field does not become the board estimation metric in the same way.

Enable time tracking for the board is incorrect because enabling time based tracking makes the board rely on time estimates rather than story points and that can prevent completed issues from deducting their full story point value from the sprint total.

On exam questions about sprint totals focus on whether the board uses story points as the estimation statistic and whether time based estimation is disabled since those two settings determine how completed issues affect the sprint remaining total.

The correct answer is: project = ORION AND (fixVersion is EMPTY OR fixVersion != “1.2.3”).

This JQL returns every issue in the ORION project while excluding any issue that references the archived fix version 1.2.3 and still includes issues that have no fixVersion set.

In JQL the operators that compare values do not match empty fields by default. You must explicitly include fixVersion is EMPTY or else issues without a fixVersion will be omitted, so the combined form shown above is required to get all issues except those that reference “1.2.3”.

project = ORION AND fixVersion not in (“1.2.3”) is incorrect because using not in will exclude the specified version but it does not match issues where fixVersion is empty, so those issues would be left out.

project = ORION AND fixVersion != “1.2.3” is incorrect for the same reason. The != operator does not return issues with an empty fixVersion, so you must add an explicit empty check to include them.

project = ORION AND fixVersion is not “1.2.3” is incorrect because is not is not valid JQL syntax for comparing to a literal value. The is and is not operators are used with keywords like EMPTY rather than with a quoted version name.

Remember that != and not in do not match empty fields in JQL. Add an explicit is EMPTY check when you need to include issues that have no value set.

The correct options are The saved filter that the board relies on is not shared with Sophia and Sophia lacks the “Browse projects” permission on the project.

A board only shows and produces reports from the issues returned by its saved filter. If The saved filter that the board relies on is not shared with Sophia she cannot see the board issues or any of the agile reports because the filter results are restricted to the users or groups the filter is shared with.

Sophia also needs project level visibility to open boards and reports. If Sophia lacks the “Browse projects” permission on the project she will be unable to view the board or its reports even if the filter is shared because Browse projects controls basic access to the project and its issues.

Sophia is missing the “Manage sprints” project permission is incorrect because that permission only allows creating and modifying sprints and it is not required to view reports or boards.

There is no “View reports” project permission configured is incorrect because Jira does not provide a dedicated project permission named View reports. Report visibility is governed by filter sharing and project access.

An issue security scheme is restricting Sophia from seeing the issues on the board is not one of the two best answers. Issue security can hide individual issues but it would not by itself prevent opening the board or all reports if the user has Browse projects and the filter is shared.

Sophia is not listed as a board administrator is incorrect because board administrator rights are not required to view reports. Admin rights only allow changing board settings and filters.

When a user cannot see a board or its reports check the board’s saved filter sharing and the user’s Browse projects permission first before looking at other settings.

It is not possible for each squad to have its own separate velocity report when they use parallel sprints, Both company-managed projects and team-managed projects allow parallel sprints, and Users cannot finish more than one active sprint at the same time are correct.

It is not possible for each squad to have its own separate velocity report when they use parallel sprints is correct because velocity is calculated at the board level and it aggregates completed work across the active sprints on that board. When multiple squads run sprints in parallel against the same backlog the reporting context is shared so you will not get separate velocity charts per squad.

Both company-managed projects and team-managed projects allow parallel sprints is correct because the parallel sprints feature is supported for boards used by both project types in Jira Software Cloud. Both kinds of projects can host boards that run simultaneous sprints provided the feature is available for the site.

Users cannot finish more than one active sprint at the same time is correct because the product requires sprint completion to be done one sprint at a time. This prevents conflicting state changes and ensures unresolved issues are handled in a controlled manner when you complete each sprint.

When finishing an active sprint you can move unresolved issues into another active sprint is incorrect. When you complete a sprint the UI asks where unresolved issues should go and the common targets are the backlog or a future sprint, but moving them directly into another currently active sprint is not the standard completion flow.

Board level settings determine whether parallel sprints are available is incorrect. The availability of parallel sprints is governed at the product or site level and is not solely a per-board toggle, so boards may need the feature enabled globally before they can use it.

A project administrator can enable or disable parallel sprints for a company-managed project is incorrect. Enabling or disabling the feature is typically a Jira administration or site level action rather than something a project administrator can change for a single company-managed project.

Focus on whether the question is asking about reporting scope or feature enablement. Remember that sprint reports are tied to the board and that turning features on or off is often a site administrator responsibility.

The correct answer is Time tracking report.

The Time tracking report shows original time estimates alongside time logged and remaining estimates so you can compare planned effort against actual work for a release. Running that report for release 2.0 lets the release manager see, by issue and in aggregate, how close the task estimates were to the time actually spent.

Average age report shows the average age of unresolved issues and helps highlight aging work. It does not show estimated time versus time logged so it will not measure estimate accuracy.

Resolution time report reports how long issues take to be resolved and helps evaluate throughput and response, but it focuses on resolution durations rather than comparing original estimates to actual work.

Version workload report shows how work or issues are distributed across a version and can help with capacity planning, but it does not directly compare original time estimates to logged time so it is not the best report for assessing estimate accuracy.

When a question asks you to compare estimates with actual work look for reports that reference time tracking or worklogs rather than reports that focus on age, resolution, or assignment.

The correct option is Three roles.

Ashley must be able to view and open issues and then add and remove the PDF files she uploads. Viewing issues requires the Browse projects permission which is granted to Project Role Team Leads. Adding files requires the Create attachments permission which is granted to Project Role Legal. Removing files she created requires the Delete own attachments permission which is granted to Project Role Contributors. Membership in those three roles is therefore the minimum required.

Four roles is incorrect because you do not need the Delete all attachments permission or an extra role to remove attachments you created. The Auditors role that grants Delete all attachments is not required if Ashley only needs to remove files she uploaded.

Two roles is incorrect because Create attachments and Delete own attachments alone do not let her access issues. She also needs Browse projects to view and open issues in the ORION project so two roles are not sufficient.

Five roles is incorrect because assigning additional roles such as Engineers or Administrators is unnecessary for adding and removing attachments. The three roles already cover the required permissions and any extra roles are not needed for this task.

When solving permission questions first list the exact actions required and then map each action to the project role that grants it. Remember to include the view or Browse projects permission because it is often required to reach the resource.

The new column can be added and it will have no status mapped to it is the correct option.

When using the simplified workflow the board allows you to add another column even if a column with the same name already exists. The new column is created as a separate column and it does not inherit or duplicate the existing status mapping automatically.

The board prevents adding a column with the same name is incorrect because the board does not block duplicate display names in this scenario. The system permits creating a second column with the same label instead of enforcing a unique column name.

The existing status will automatically map to the new column is incorrect because mappings are explicit. The original status remains mapped only to the original column and you must assign or map a status to the new column manually if you want it linked.

When a question asks about board behavior think about whether names and mappings are separate concepts and remember that mappings often require explicit configuration rather than occurring automatically.

The correct option is Limited.

Limited is correct because it lets the whole BrightLearn organization participate in discussions while keeping issue creation restricted to project members. Jordan can add only the developers who should create issues to the project membership and everyone else at the company can still comment on existing issues.

Restricted is incorrect because restricted access typically limits viewing and commenting to a small set of people and would not allow everyone at BrightLearn to comment.

Public is incorrect because a public project would expose creation and editing capabilities too broadly and would not enforce the developer-only creation requirement.

Individual is incorrect because that level implies access tied to specific single users and it does not match the scenario of letting the entire company comment while limiting creators.

Open is incorrect because an open project normally allows broad creation and participation and would not prevent non-developers from creating issues.

Private is incorrect because a private project restricts visibility and commenting to only invited members which would stop everyone at BrightLearn from commenting.

When a question separates who can comment from who can create think about access levels that allow broad participation but restrict write actions to project members. For team managed projects match the access level to the role that needs creation rights.

The correct option is Unassigned.

When you create an issue with the assignee set to Automatic and multiple components are selected the system evaluates each component’s default assignee. The Ledger component explicitly has its default assignee set to Unassigned while Insights uses the project default. Because one of the selected components explicitly sets the assignee to Unassigned the new issue will be created as Unassigned.

Claire is the project lead but the project default assignee only applies when a component’s default is Project Default. Since Ledger explicitly sets Unassigned the project lead is not selected.

Elena is the lead for Insights but the Insights component is configured to use the project default rather than the component lead. That means she will not be automatically assigned.

Javier is the component lead for Ledger but Ledger’s default assignee is set to Unassigned rather than Component Lead. That prevents him from being automatically assigned.

When several components are chosen check each component’s default assignee because an explicit Unassigned setting will override project defaults and stop automatic assignment to a person.

The correct options are Users can add a Scrum board inside a project that is configured for Kanban, Users can create a Kanban board in a project that uses Scrum practices and A board is only a view of issues and teams can create multiple Scrum or Kanban boards in any company-managed project.

Jira boards are essentially saved views or filters over issues, so A board is only a view of issues and teams can create multiple Scrum or Kanban boards in any company-managed project is accurate. Teams often create multiple boards to represent different workflows or team views and each board can use either the Scrum or Kanban board type.

Because boards are views rather than tightly coupled project artifacts, Users can add a Scrum board inside a project that is configured for Kanban and Users can create a Kanban board in a project that uses Scrum practices are both correct. You can create a board of one type that surfaces the project issues even if the project practices or workflows are oriented toward the other board type.

Users cannot create a Kanban board in a project that uses Scrum workflows is incorrect because Jira does not block creating a Kanban board simply because the project uses Scrum workflows. Boards are views and can be created independently of the underlying workflow scheme.

Boards are hard linked to project templates and cannot be modified without recreating the project is incorrect because boards and their configurations can be edited and boards are not irrevocably tied to the project template in a way that requires project recreation to change them.

Users are prevented from having both Kanban and Scrum boards in the same project is incorrect because a single company-managed project can host multiple boards of different types at the same time and teams commonly run both kinds of boards against the same set of issues.

When you see statements about what is “not” allowed or that something is “hard linked” think about whether the feature is a view or a project configuration. Remember that Jira boards are primarily views of issues and that word often indicates flexibility rather than a hard restriction. Use that clue to eliminate overly absolute answers.

The correct answer is Rule conditions, Event triggers, and Action steps.

Event triggers determine when an automation rule starts by detecting the occurrence of a specific event or schedule. Triggers are the entry point for a rule and they tell the system to evaluate the rule whenever the defined event happens.

Rule conditions are used after a trigger to decide whether the rule should continue. Conditions filter the incoming events so that actions only run when the issue or event meets the required criteria.

Action steps are the tasks the rule performs when its conditions pass. Actions make changes such as editing an issue field, transitioning the issue, sending notifications, or calling external services.

Cloud Pub/Sub is a Google Cloud messaging service and it is not an element that composes Jira Cloud automation rules.

Workflow validators are part of Jira workflow transitions and they enforce constraints at transition time. They are not the same as automation rule conditions and they do not define triggers or action steps in automation rules.

Event listeners are a different mechanism that can respond to events at the application level. Jira Cloud automation uses triggers rather than low level listeners, so listeners are not listed as the core elements of an automation rule.

When you read questions about automation rules think in sequence. Identify the trigger that starts the rule then the conditions that filter events and finally the actions that run.

Recently Created Chart is the correct option.

The Recently Created Chart gadget is designed to show the number of tickets created over time and it can be configured to highlight how many of those created issues remain unresolved in each period which matches the requirement to visualize monthly backlog and unresolved counts.

Average Age Chart is not correct because it reports the average age of unresolved issues rather than showing counts of tickets created each month and how many remain open.

Filter Results is not correct because it provides a list or basic count of issues that match a saved filter and it does not produce a month by month chart showing created versus unresolved items.

Resolution Time is not correct because it focuses on how long it takes issues to be resolved and not on the number of tickets created each month or how many of those remain unresolved.

When a question asks for counts over time and how many remain open look for gadgets that mention created or recently created and avoid gadgets that emphasize age or resolution duration.

Users can apply custom filters on a team managed board to narrow issue lists, Any user with a product license can create and manage a team managed project, and Project members can define custom roles in a team managed project are correct.

Users can apply custom filters on a team managed board to narrow issue lists is correct because team managed boards support quick filters and other board filtering features that let project members narrow the visible issues for their workflow and focus.

Any user with a product license can create and manage a team managed project is correct because team managed projects are designed to be created and administered by users who have product access and they do not require global administration rights, although site or organization admins can impose creation limits.

Project members can define custom roles in a team managed project is correct because roles and permissions in team managed projects are project scoped and configurable by project admins so members can create and adjust roles that apply only to that project.

A team managed project can export its configuration to other projects is incorrect because team managed projects keep configuration local and do not provide the shared scheme or export capabilities that company managed projects offer for reusing configuration across projects.

When the question contrasts team managed and company managed projects look for key phrases about shared schemes or global reuse. Team managed keeps configuration local so answers mentioning export or reuse across projects are usually incorrect.

Card layout settings is correct. Changing the Card layout settings lets Maya choose which issue fields appear on Kanban cards so she can show the component field and the created and due dates for clearer visibility.

The board’s card layout controls the fields that display on the face of each card and how many extra fields are visible. By editing the Card layout settings Maya can add the component field and surface date fields so the team sees them without opening each issue.

Columns configuration is incorrect because columns map statuses and represent workflow stages and they do not control which fields are shown on cards.

Card colours is incorrect because card colours only change visual highlighting and do not add or expose fields like component or created date on the card.

Issue detail view is incorrect because that view affects the layout when an issue is opened and not the fields that appear on the Kanban board cards.

If you need extra fields visible on cards go to the board settings and edit the Card layout settings then use the board preview to confirm the fields appear as expected.

The correct options are Select List (single choice) and Radio Button.

Select List (single choice) meets the requirements because it is a single choice field that supports a predefined default value and it can use field contexts to provide different option sets per project while remaining a global custom field available across projects.

Radio Button also meets the requirements because it enforces a single selection, supports default values, and supports project specific option sets through field contexts so you can vary the options by project while keeping the field available across projects.

Components are tied to a specific project and cannot be defined as a global custom field across all projects, so they do not satisfy the requirement that the field be available across all projects.

Labels allow multiple freeform values and do not enforce a single choice or a predefined option set, so they fail the single selection and predefined default requirements.

Checkbox custom fields allow multiple selections rather than a single choice, so they do not meet the requirement that only one option can be chosen.

When you see questions about field availability and option sets focus on whether the field supports single versus multiple selection and whether it supports field contexts and default values.

Workflow scheme, Notification scheme, Issue security scheme, and Issue types are correct.

Workflow scheme is part of shared configuration because company managed projects use workflow schemes to map workflows to issue types and those schemes are applied across projects so a single scheme can control workflow behavior for many projects.

Notification scheme belongs to shared configuration because notification schemes define who gets notified for events and they are reusable schemes that can be associated with multiple projects to standardize notifications.

Issue security scheme is included because it is a scheme that controls issue visibility and it can be shared across projects so access rules apply consistently when the same scheme is used.

Issue types are part of the shared configuration through the issue type scheme so the set of issue types available to a project is controlled by a shared scheme rather than being an individual project attribute.

Project board is incorrect because boards are not shared schemes and they are tied to filters and board configuration rather than being part of the project shared configuration.

Components is incorrect because components are project level entities that are managed per project and are not part of the reusable scheme system that defines shared configuration.

Project navigation is incorrect because navigation and UI layout are project specific settings and are not represented as shared schemes for company managed projects.

Project roles membership is incorrect because the membership is a per project assignment of users and groups and it is not a shared scheme even though the role definitions themselves are global.

When a question mentions shared configuration look for items that are defined as schemes such as workflow, notification, issue security and issue type schemes and filter out items that are clearly project specific like boards, components or membership.

The correct options are Project administrator role, Original board creator, Jira administrator role, and Board administrator role.

The Board administrator role is explicitly created to manage a board and its settings so that person can change board configuration, columns, and quick filters and perform other board level administration tasks.

The Project administrator role can manage boards that are based on or owned by their project because project administrators have rights to alter project settings and boards that rely on project filters.

The Original board creator typically becomes a board administrator by virtue of creating the board and therefore retains the ability to manage that board unless their permissions are changed.

The Jira administrator role is a system level role with broad product permissions so Jira administrators can manage boards across the instance and change filters and permissions as needed.

The Site administrator role is not a correct choice because site administrators focus on the overall Atlassian site and user or billing management and they do not automatically gain board management rights inside Jira projects in the same way that board, project, or Jira administrators do.

When you see questions about who can manage boards look for roles with board or project administration privileges and remember that site administration is a separate, higher level concern and does not automatically imply board control.

The correct options are Users can create new issues directly from the Sequence view, Users can add comments from within the Sequence view, The Sequence view lets users filter epics and issues by status, and Users can filter epics and issues by assignee in the Sequence view.

The Sequence view is intended for planning and sequencing work and it includes inline controls so teams can add new work items without leaving the view. Creating issues directly in the view helps keep backlog grooming and planning fast and reduces context switching.

The view also supports adding comments on items so teams can capture discussion and decisions in place and keep the conversation linked to the work being planned.

Filtering by status and by assignee is available so users can narrow what they see to particular states or to work owned by specific people. Those filters are common for planning workflows and they are supported in the Sequence view.

The Sequence view allows filtering epics and issues by priority is incorrect. Priority based filtering is not offered in this view and priority is not listed as an available filter.

The Sequence view supports filtering epics and issues by sprint is incorrect. Sprint based filtering is not available in the Sequence view and you must use other views or reporting tools to filter by sprint.

When answering UI feature questions look for keywords that indicate actions such as create or comment and not just filters. Verify which exact filter types are supported in the product documentation before selecting answers.

The correct answers are Issues in progress, Watched issues, and Assigned to me.

The Issues in progress gadget shows work that is currently active for the person viewing the dashboard because it uses the viewer context to present items in progress rather than requiring a saved filter or a specific project to be chosen.

The Watched issues gadget lists issues that the logged in user has added to their watch list so it inherently shows the current user’s items without needing a saved filter or project selection.

The Assigned to me gadget displays issues where the assignee is the viewer and it relies on the current user context to show that person’s assigned work without a saved filter or project being specified.

Filter Results gadget is incorrect because it requires a selected saved filter or explicit JQL to determine which issues to display and it does not by itself default to the currently logged in user unless the saved filter explicitly uses the currentUser() function.

When a question asks about the “currently logged in user” look for gadgets that use currentUser() or that are described as showing “my” or “assigned to me” items without selecting a saved filter.

Maya needs to be added as an Editor of the saved filter is correct.

Maya needs to be added as an Editor of the saved filter is the precise issue because saved filter queries are owned and editable only by the filter owner or by users who have been granted edit rights. Being a board administrator does not automatically grant the ability to change the saved filter query, and the simplest resolution is to add Maya to the filter’s editor list or have the owner transfer ownership.

The saved filter is owned by another user and not shared with Maya is incorrect because ownership and basic sharing determine visibility and use. If Maya could not see or use the board at all then sharing would be the problem, but the scenario indicates she can administer the board and the missing capability is the specific edit permission.

Maya lacks a project permission that would let her edit the filter is incorrect because project permissions control actions on issues within a project and not who can edit a saved filter. Editing a saved filter is governed by the filter owner and the filter’s editor or sharing settings.

Maya lacks a global permission related to filters is incorrect because the immediate restriction is the per‑filter editor setting. Changing global permissions is not required when the filter owner can simply add Maya as an editor to allow her to modify the query.

Remember that board administrator does not automatically equal filter editor. When a user cannot change a saved filter check the filter’s editors or the filter owner first.

There is no cap on the number of “IF/ELSE” blocks but there is an overall cap of 48 components per rule. This choice is correct because the platform does not limit the count of IF and ELSE constructs independently and instead enforces a total component ceiling for a rule.

The platform counts all building blocks in a rule as components and that total must not exceed 48. That means you can nest or chain many IF/ELSE constructs as long as the combined number of components including conditions, actions, and branching elements stays within the 48 component limit.

There is a cap on the number of “IF/ELSE” blocks and there is also a cap on the total components in one rule is incorrect because it states there is a separate limit on IF/ELSE blocks. The actual constraint is only on the total component count rather than on IF/ELSE blocks by themselves.

There is no cap on “IF/ELSE” blocks and there is also no cap on the total components in one rule is incorrect because there is indeed a cap on the total components per rule. Saying there is no cap on components contradicts the documented 48 component limit.

There is a cap on the number of “IF/ELSE” blocks but there is no cap on the total components in a single rule is incorrect because it reverses the actual limits. The system does not impose a separate IF/ELSE limit and it does impose an overall components limit.

When a question contrasts limits on a specific construct versus total components, trust the rule that platforms often enforce a single overall component count rather than many small per-construct caps. Check the wording for overall or per rule to choose the right answer.

Modify the system field Fix Versions is correct because the Resolve Issues project permission allows users to change the fix version assignments when they perform resolve transitions or update an issue as part of closing work.

The Fix Versions field is a system field that records the target release or releases for an issue and changing it is commonly part of resolving an issue. Granting Resolve Issues permits users to perform the resolve action and to modify that field on the transition screens or via the workflow as configured.

Alter the system field Due Date is incorrect because editing the due date is not specifically granted by the Resolve Issues permission. Changing due dates is typically controlled by edit permissions and by which fields appear on the screens used for a transition.

Edit the system field Resolution is incorrect because although resolution values are applied when issues are resolved the Resolution field is normally managed by workflow transitions and post functions rather than being an explicit grant of the Resolve Issues permission alone in many configurations.

Update the custom field Resolution Reason is incorrect because custom fields are governed by screen and field configuration and by general edit permissions. Updating a custom field depends on those configurations rather than being uniquely enabled by the Resolve Issues permission.

When answering permissions questions check what the permission explicitly grants and whether a field is managed by workflow screens or by a separate custom field configuration.

Assign components to represent each functional team and build three boards each filtered by its component is the correct option for this requirement.

Components are a built in issue attribute that can represent each functional team and they can be used directly in board filters so each team gets its own board that only shows its issues. A board scoped to a single component will produce reports and a burnup chart that reflect only the issues included on that board so each team sees a burnup for its work without heavy project reconfiguration.

Use labels to mark each functional team and create three separate boards each filtered by its team label is not ideal because labels are freeform and prone to typos and inconsistency. Labels can be used to filter boards but they are harder to govern and do not provide the same structured ownership and visibility as components.

Use versions to indicate functional areas and create a single board with swimlanes arranged by version is incorrect because versions represent releases or milestones rather than teams. Using versions for functional areas will confuse release tracking and a single board with swimlanes will not give each team its own board level reports and burnup chart.

Create a new custom field for functional area and use a single board with three quick filters driven by that field is not the best choice because quick filters do not change the board scope for built in reports and they are a transient view. A custom field adds administrative overhead and still would not provide three separate boards each with its own burnup chart unless you created separate boards filtered by that field instead of relying on quick filters.

When the exam describes separate team views and separate reports inside the same project think about using built in issue attributes like components that can drive distinct boards and their reports rather than ad hoc labels or only quick filters.

Team-managed project using Scrum template is correct because it provides a backlog and an Agile board on creation supports sprint iterations such as seven day sprints and lets the project administrator rename workflow status labels without enabling extra features.

Team-managed projects give project administrators direct control over boards workflows and issue types so an admin can rename status labels inside the project settings without needing Jira administrator rights. The Scrum template includes a backlog and built in sprint support so you can create seven day iterations immediately and run the agile board from day one.

Company-managed project with Scrum template is incorrect because company managed projects use shared workflows that normally require a Jira administrator to edit. That means a project administrator cannot rename workflow status labels immediately without extra admin changes.

Company-managed project with Kanban template is incorrect because Kanban templates do not provide sprint iterations by default. The requirement calls for seven day sprint iterations and Kanban does not meet that need.

Team-managed project with Kanban template is incorrect because the Kanban template does not include Scrum sprints even though team managed projects let admins edit statuses. It therefore fails the sprint iteration requirement.

No Jira project type can satisfy all requirements is incorrect because a Team-managed project using Scrum template does satisfy the backlog board sprint and admin rename requirements.

When a question asks who can edit workflows or statuses remember that team-managed projects give project admins more control while company-managed projects often require Jira administrator involvement.

The tool lets you complete all active sprints in one operation is the correct choice for the statement that is incorrect about parallel sprints.

This statement is incorrect because parallel sprints are closed or completed at the sprint level or by board and they require deciding where to move unfinished work for each sprint. There is no single global action that reliably completes every active sprint across multiple teams and boards in one operation.

Each squad requires a separate backlog for parallel sprints is not the incorrect statement because many parallel sprint setups use separate team backlogs or filtered boards so squads can plan and prioritize independently. That makes the option a valid description of common parallel sprint practices rather than a false claim.

Teams must use the same estimation scale for their work is not the incorrect statement because using a common estimation scale is often required when teams want comparable velocity and combined reporting. Requiring a shared estimation approach is therefore a reasonable and frequently applied constraint rather than an incorrect description.

The Velocity Chart will not display velocity broken down by squad is not the incorrect statement because velocity charts are tied to a board or a specific sprint scope and you can view velocity per board or per sprint to obtain team level metrics. The chart behavior does not universally prevent viewing velocity by squad, so the option is not the false statement asked for here.

When a question asks which statement is incorrect focus on whether the described action applies globally or only per sprint or board. Check whether the feature requires per-sprint decisions or supports a one click global change and use that to eliminate answers.

The correct answer is Pie Chart Report.

The Pie Chart Report produces a visual chart that groups issues by a chosen field and it can be run against a saved filter so you can restrict which issues are included. This makes it the right choice when you need a simple visual breakdown for a custom field such as Role with values Lead and Staff.

Time Since Issues Report is not correct because it focuses on how long issues have been in a particular state rather than producing a grouped visual chart by a custom field.

Average Age Report is not correct because it shows age metrics for issues and does not create a categorical pie chart grouped by a custom field.

Time Tracking Report is not correct because it summarizes logged work and estimates rather than visualizing issue counts grouped by a custom field.

Single Level Group By Report is not correct because it produces grouped lists or tables and not the pie chart visualization that was requested.

Resolution Time Report is not correct because it analyzes time to resolution metrics and does not create a pie chart grouped by the Role field.

Focus on the verbs in the question to decide whether the exam wants a visualization or a metric report. If the question asks for a grouped visual chart and a saved filter then choose a chart type such as the Pie Chart Report.

The correct answers are Move them into the upcoming sprint and Move them to the backlog.

When the team completes a sprint the project management tool prompts for where to place incomplete issues. If you choose Move them into the upcoming sprint the unfinished issues are carried forward into the next planned iteration so the team can address them without recreating work. If you choose Move them to the backlog the issues return to the backlog so they can be reprioritized refined or estimated before being planned into a future sprint.

Unresolved issues are archived is incorrect because incomplete issues are not archived automatically at sprint completion. The system requires you to move them to the backlog or into another sprint.

They are removed from the board is incorrect because removing would hide or delete work which does not happen when a sprint is completed. Issues remain tracked and must be assigned to the backlog or a sprint.

Move them directly to another active sprint is incorrect because the typical completion dialog offers the backlog or an upcoming sprint as targets and it does not place issues into an already active sprint without manual reassignment.

When you see questions about incomplete sprint work look for choices that match the completion dialog and focus on options that send work back to the backlog or into an upcoming sprint.

Edit issues and Schedule issues are correct.

Schedule issues grants the ability to change scheduling fields and to move and reorder issues on the backlog and board so this permission is required to reorder backlog items on the Scrum board.

Edit issues allows a user to modify issue fields and details which is often required when repositioning or updating work items because reordering can involve changing sprint or ranking fields and the user needs edit rights to persist those changes.

Manage sprints is focused on creating, starting, and closing sprints and it alone does not allow reordering backlog items if the user lacks scheduling or edit rights.

Administer projects is a high level permission for changing project settings and roles and it is not required just to reorder backlog items and it is usually overprivileged for this task.

View development tools only controls visibility of development information such as commits and pull requests and it does not grant the ability to change backlog order.

Browse projects only allows viewing project issues and does not include rights to edit or schedule issues so it cannot be used to reorder the backlog.

When questions ask about changing backlog order look for permissions that let you modify issues or schedule them. Grant the least privilege needed and match the action to the specific permission name.

The correct answers are Quick Filters and Board Filter.

The Quick Filters feature lets Lara add board-level buttons that apply simple queries or JQL so she can click to show only issues assigned to her team or to specific assignees. Quick filters are intended for quick, temporary views without changing the board configuration.

The Board Filter defines the overall scope of the board with a JQL query and it controls which issues appear on the board for everyone. Editing the board filter to include only the squad or a team field will make the board show only that team’s issues.

Issue Detail View displays the contents and fields of a single selected issue and it does not filter or hide other issues on the board.

Saved Filters are general JQL queries that users can reuse across the site and they are not the board-specific control for interactive board views. A saved filter can be the basis of a board filter but it is not the on-board toggle Lara needs for quick team views.

Board Sub Filter is not the primary mechanism to show only a specific squad on the board and it is not commonly used for the interactive, per-view filtering that Quick Filters provide.

Swimlanes organize issues into horizontal lanes based on queries or stories and they help with layout and grouping rather than hiding all non-team issues as a filter would.

Use Board Filter to set the permanent scope for the board and create a few Quick Filters for fast, repeatable views such as showing only your squad or current assignees.

The correct option is Trigger.

A Trigger is the component that starts an automation and a scheduled notification requires a schedule to kick off the rule. For a weekly notification you must configure a Trigger that runs on the desired cadence so the automation can check for unresolved issues and then perform actions.

Smart values are used to read or format issue data inside actions and conditions and they do not start or schedule the automation, so they are not the required component here.

Condition is used to limit or filter which issues the rule acts on and it does not initiate the rule, so it is not the mandatory piece for a scheduled notification.

Send Slack message is an action that performs the actual notification and it is optional depending on how you want to notify the team, but the action by itself does not cause the automation to run on a schedule.

When you see automation questions ask which part starts the rule. The trigger is the required element for any rule that must run on a schedule or in response to an event.

“Edit issues” project permission and “Make bulk changes” global permission are correct.

The “Edit issues” project permission is required because updating the Component/s field modifies the issue itself and the project permission controls who can make those edits within the project. Without that project permission a user cannot change issue fields even if they can view the issue.

The “Make bulk changes” global permission is required because initiating and executing bulk operations is controlled at the site level and only users granted that global right can perform bulk edits across multiple issues or projects.

“Browse projects” project permission is incorrect because that permission only allows a user to view the project and its issues and it does not grant the ability to edit issues or run bulk operations.

“Manage project roles” project permission is incorrect because that permission lets a user change role membership and role assignments within a project and it does not provide edit rights on issues or the ability to perform bulk changes.

When answering permission questions check whether the task changes issue data or starts a site wide action. Remember that project permissions control editing and global permissions control bulk operations.

The correct answer is Save personalized plan views for different audiences.

This capability lets teams create and preserve tailored perspectives of the same plan so stakeholders and delivery teams can each see the information they need without changing the underlying plan. Saved views support filters and layout choices which makes it easier to scale agile work by presenting the right level of detail to different audiences.

Import issues from external systems and other Jira sites to build a plan is incorrect because Advanced Roadmaps consumes issue sources from within a Jira site such as projects, boards, and filters and it is not designed to act as a universal importer of external systems or of other separate Jira instances without additional migration or integration tools.

Link budget and financial figures directly to plans is incorrect because Advanced Roadmaps focuses on scheduling, dependencies, and capacity planning rather than financial accounting. Budget and financial tracking are not native features and require third party apps or integrations.

Consolidate data from multiple Jira Cloud instances into a single plan is incorrect because Advanced Roadmaps reads issue data from a single Jira site and does not natively aggregate across separate Jira Cloud instances. Cross instance consolidation requires separate centralization or reporting solutions.

When evaluating Advanced Roadmaps features focus on what the product natively manages such as views, hierarchies, and capacity. Favor answers that describe saved views and plan configuration over options that imply cross instance imports or built in financial linking.

The correct answer is The board filter does not include the ranking field.

The Scrum board stores the backlog and board order in a special field called the Rank or ranking field. If the board’s filter or JQL omits that field or otherwise restricts the issues used for ranking then the UI cannot persist a new order and dragging items in the Backlog will not work. To restore ordering you must adjust the board filter so the ranking field is available for the board.

Sofia needs Schedule Issues project permission is incorrect because the Schedule Issues permission controls editing of scheduling fields like due date and does not prevent reordering issues on the board.

Sofia lacks Jira Software product access is incorrect because lacking product access would prevent her from seeing or interacting with the Scrum board at all and would not manifest only as an inability to drag to reorder.

Sofia requires project administrator privileges is incorrect because project administrator rights are not required to rank issues. Users only need normal issue interaction permissions and a board filter that includes the ranking field to change the backlog order.

When a board will not let you rearrange issues first check the board filter and JQL for anything that hides the Rank or ranking field before troubleshooting permissions.

Maya does not have the global permission “Create Shared Objects” is correct.

The reason is that creating a company managed board from an existing project still requires the ability to create and share the board and its filter at the global level. Because Maya lacks the “Create Shared Objects” global permission she cannot successfully share the new board URL with her teammates even though they already have access to the ORION project.

The team does not have the project permission Browse projects is incorrect because the scenario states the team already has access to the company managed Kanban project. If they could access the project then lacking Browse projects would not be the cause of the board link being inaccessible.

The board filter is private to Maya and not shared is incorrect because the inability to share or make the board visible is governed by the global sharing permission. The filter would only remain private if Maya could not share objects due to missing the global permission rather than a per filter setting alone.

Maya is missing the project permission Administer projects is incorrect because administering the project is not required to create or share a company managed board. The blocker in this case is the global “Create Shared Objects” permission rather than the project level Administer projects right.

When a shared board link does not open for teammates check both project access and the global Create Shared Objects permission because sharing of company managed boards is controlled at the global level.

The correct option is Company-managed Kanban project.

Company-managed Kanban project is the right choice because company managed projects support shared boards and advanced configuration so a board can include issues from multiple projects. Kanban supports a continuous flow and does not rely on fixed sprint cycles which fits a team that will not operate in sprints and that will deliver ongoing bug fix releases.

Company-managed Kanban project also provides release and version management and permissions that make it easier for a delivery manager to expose work across the organization and to track recurring fixes centrally.

Team-managed Scrum project is incorrect because team managed projects are scoped to a single project and cannot easily host issues from other projects and Scrum enforces sprint based work which does not match a non sprint workflow.

Team-managed Kanban project is incorrect because although Kanban matches the continuous workflow requirement, team managed projects remain confined to their own project and they lack the cross project board sharing and release management needed for ongoing bug fix releases across multiple projects.

Company-managed Scrum project is incorrect because even though company managed projects allow cross project boards, Scrum is built around sprint cycles and that contradicts the requirement to avoid fixed sprints.

Watch for keywords like cross project and no sprints and then select a company-managed Kanban option because company managed projects support shared boards and Kanban supports continuous delivery.

The correct answers are Releases listed in the backlog display only issues that satisfy the board filter, The board sub filter hides issues on the TaskBoard without affecting counts shown in external reports, and A TrackerPro system administrator can create a new workflow status by adding a column on the board.

Releases listed in the backlog display only issues that satisfy the board filter is correct because the board filter defines which issues are visible in backlog release groups and the backlog view applies that filter when it enumerates release contents.

The board sub filter hides issues on the TaskBoard without affecting counts shown in external reports is correct because the sub filter operates as a view layer on the board only and it does not change the underlying issue set that external reports and totals use.

A TrackerPro system administrator can create a new workflow status by adding a column on the board is correct because administrators have the permission to extend the workflow and adding a column on the board creates the corresponding status in the system workflow.

The board filter hides issues from the TaskBoard while leaving report totals unchanged is incorrect because the board filter affects which issues are considered in backlog and reporting contexts and therefore can change report totals.

Board managers can alter the board filter even if they are not the owner of the saved filter is incorrect because saved filter ownership and permissions control who can modify the saved filter and board manager rights do not automatically override saved filter ownership.

The count of Epics shown in the backlog is unaffected by the board filter is incorrect because the board filter restricts which issues are visible in the backlog and that restriction changes the counts of Epics that are shown.

When a question contrasts a board filter with a sub filter focus on whether the statement says it changes report totals or only the board view. Permissions and saved filter ownership are often decisive in questions about who can edit filters.

The correct answers are Administrators can disable the sub task feature, The name and description for sub tasks can be localized for installed languages and Users can convert a sub task into a standard issue type and convert standard issues into sub tasks.

Administrators can disable the sub task feature is correct because Jira system administrators have a global setting to enable or disable sub-tasks from the administration interface. When that setting is turned off the sub-task issue type is not available for creating new sub-tasks until an administrator turns the feature back on.

The name and description for sub tasks can be localized for installed languages is correct because issue type metadata supports localization when multiple languages are installed in the instance, and you can provide translated names and descriptions so users see them in their chosen language.

Users can convert a sub task into a standard issue type and convert standard issues into sub tasks is correct because Jira provides issue type conversion operations that let you change a sub-task into a standard issue and vice versa, subject to workflow and field compatibility rules and to the permissions required to perform conversions.

Sub tasks can contain their own sub tasks is incorrect. Jira does not support nested sub-tasks beyond a single parent level so a sub-task cannot have its own sub-tasks. If deeper hierarchies are needed you must use linked issues or different issue type schemes rather than nested sub-tasks.

When answering, watch for statements that imply more than one level of nesting. Remember that sub-tasks are a single level under a parent issue and that administrators can enable or disable sub-task functionality globally.

The correct report is Time Tracking Report.

The Time Tracking Report displays each issue’s original estimate, the time logged against the issue, and the remaining estimate so Priya can compare planned effort to actual work and validate that tasks are progressing as expected.

Pie Chart Report shows the distribution of issues by a selected field and it does not include original estimates or time logged so it cannot validate estimates versus actual work.

Time Since Issues Report reports how long it has been since issues changed state and it is intended for aging analysis rather than checking original estimates against time spent.

Resolution Time Report summarizes how long issues take to reach resolution and it measures time to close rather than providing original estimate and logged time comparisons.

Average Age Report shows the average age of unresolved issues and it does not provide original estimate or time spent details needed to validate progress against estimates.

Single Level Group By Report groups and counts issues by a specified field and it focuses on counts and grouping rather than on time tracking or estimates.

When you must compare planned effort with actual work look for reports that explicitly mention original estimate or time spent because those reports contain the time tracking fields you need.

Altering the timeline view settings will change the perspective for everyone on the project, Completed epics are automatically removed from the timeline, and Users can switch the epic bar display to weeks months quarters or an annual view are the correct statements.

Altering the timeline view settings will change the perspective for everyone on the project is correct because the timeline view is a project level display option and changes to filters or time scale affect what all project members see rather than creating a separate personal view.

Completed epics are automatically removed from the timeline is correct because the timeline focuses on active planning and completed work is typically hidden or archived from the active timeline to reduce clutter and keep the schedule focused on in progress and upcoming items.

Users can switch the epic bar display to weeks months quarters or an annual view is correct because the timeline supports multiple time scales so teams can zoom in and out to a weekly, monthly, quarterly, or yearly perspective to match their planning horizon.

Users can change an epic’s color directly on the timeline is incorrect because color and styling are set in the epic properties or through labels and not by clicking the epic bar on the timeline to change its color in most implementations of the feature.

Child issue schedule bars are available for both Scrum and Kanban teams is incorrect because child issue schedule bars are not universally available to both team types and their visibility depends on the board configuration and the product edition rather than being automatically provided for every Scrum and Kanban team.

Note that this feature was previously called Roadmap in Sprintly Cloud so older documentation or study materials may use that name and you should be aware that naming can change over time.

Read each statement carefully and watch for words that indicate scope such as project wide or automatically when deciding which options are true or false.

project = “BrightLearn” AND Sprint in openSprints() is correct.

The project = “BrightLearn” AND Sprint in openSprints() query limits results to the BrightLearn project and uses the openSprints() function to target sprints that are currently open. The openSprints() function returns a set of sprint values so the query uses the in operator to match issues assigned to any open sprint on the board.

The project = “BrightLearn” AND Sprint = activeSprint() option is incorrect because activeSprint() is not a standard JQL sprint function and the equals operator expects a single sprint value rather than a function result, which makes the expression invalid for selecting the current sprint.

The project = “BrightLearn” AND Sprint = openSprints() option is incorrect because openSprints() returns multiple sprint values and you must use the in operator to compare the Sprint field to that set. Using the equals operator will not correctly match the open sprints.

The project = “BrightLearn” AND Sprint in futureSprints() option is incorrect because futureSprints() returns sprints that are planned to start in the future and it will not include the currently active open sprint.

When a JQL function returns multiple sprints use the in operator rather than = and check whether the function returns open or future sprints to match the question.

The correct option is Children.

The Children branch iterates over the issues that are directly contained within an Epic so the automation can add a comment to each story or task inside that Epic. Using this branch runs the comment action once per child issue which meets the requirement to touch every issue in the Epic.

Linked Issues is incorrect because it targets issues connected by issue links such as relates to or blocks and not specifically the child issues of an Epic.

Parent is incorrect because that branch moves from a child issue to its parent and does not iterate through the issues inside an Epic.

Epic (Parent) is incorrect because it is used when you start from a child and want to operate on its Epic rather than when you need to act on all issues within an Epic.

Sub-tasks is incorrect because it targets sub-tasks of an individual issue and will not reach the standard stories or tasks that are children of an Epic.

When a rule must act on every issue inside an Epic look for branches that iterate the Epic’s child issues. Use Children to target those stories and tasks and avoid Sub-tasks which only covers lower level sub-issues.

Company-managed Scrum project is correct because it supports Scrum sprints for multiple squads and it allows reuse of shared custom fields and schemes that are managed at the company level.

A Company-managed Scrum project provides centralized configuration for workflows, screens, and custom field schemes so different projects can share the same custom fields and settings. It also provides Scrum-specific features such as sprint planning and boards that let multiple squads run sprints concurrently while using the same project-level configuration.

Team-managed Kanban project is wrong because team-managed projects keep their own independent configurations and cannot reuse company-wide custom field schemes. Also Kanban is focused on continuous flow and does not include sprint management.

Company-managed Kanban project is wrong because although company-managed projects can share custom fields it uses the Kanban template which does not provide built-in sprint support. That makes it unsuitable when multiple squads must run sprints concurrently.

Team-managed Scrum project is wrong because team-managed projects do include Scrum boards but they maintain separate, per-project configurations and cannot reuse the shared custom field schemes that other company projects rely on.

When the question mentions shared configuration or reuse of custom fields choose a company managed project. When it mentions concurrent sprints choose a Scrum template rather than Kanban.

The correct answer is You can duplicate the board and the team will retain viewing and editing access to the copy.

When a project administrator duplicates a board the duplicate keeps the original board’s sharing configuration and permissions. If the original board was shared with the team the copy remains shared and team members retain their view and edit access. Duplicating the board copies the board settings and does not by itself require changing global sharing permissions.

You can duplicate the board but the copy will be private to you is incorrect because the copy does not automatically become private when the original was already shared. The duplicate inherits the sharing settings so it will remain accessible to the same team unless those settings are changed after duplication.

You cannot duplicate the board without the global permission “Create shared objects” is incorrect because duplication of an existing shared board does not require that global permission to preserve the sharing. The global permission controls creating new shared objects from scratch or changing share scopes in some systems but it does not prevent copying a board that already has shared settings.

When you see questions about permissions focus on whether the action copies existing sharing settings or whether it creates a new shared object. Pay attention to the words duplicate and share in the question to decide which permission matters.

Both team-managed and company-managed projects can be assigned a project category is correct.

The reason is that project categories are site level labels used to group projects and they are not limited to one project type. Administrators apply project categories across the Jira site so both team-managed projects and company-managed projects can be assigned the same category for reporting and navigation.

A project category can be associated with only one project is incorrect because categories are intended to group multiple projects and you may assign the same category to many projects.

Issue types can be linked to project categories is incorrect because issue types are part of project configuration and schemes while categories are only for grouping projects. There is no feature that ties issue types to project categories.

Project administrators can create project categories is incorrect because creating and managing categories requires site administration permissions. Project admins do not have the global rights needed to create or delete project categories.

When answering similar questions decide first if the feature is managed at the site or project level and then pick the role that matches that scope.

The correct answers are currentSprints() and nextSprints().

Both currentSprints() and nextSprints() are not defined JQL functions in Jira Software, so they are the names that are not valid for sprint-related queries. The sprint-related JQL features use specific functions to target sprint states and these two names do not appear in the documented set of sprint functions.

futureSprints() is a valid JQL function that finds issues in sprints that have not yet started, so it is not one of the invalid names.

openSprints() is a valid JQL function that returns sprints that are currently in progress, so it is not one of the invalid names.

closedSprints() is a valid JQL function that returns completed sprints, so it is not one of the invalid names.

When a question asks for invalid function names, quickly recall the documented sprint JQL functions such as openSprints(), closedSprints(), and futureSprints() and then pick the names that do not match those exact functions.

The correct answer is The owner who created the saved filter.

The owner who created the saved filter can update the configuration because the board built from that filter relies on the saved filter for its issue scope and permissions. The filter owner can change the filter’s JQL and sharing settings and those changes directly affect the board configuration and results.

The option Users who have been granted the Product Administrator role is incorrect because being a product administrator does not automatically grant ownership of a specific saved filter or the right to edit a board that depends on someone else s filter. Product administration is broader and separate from filter ownership and board administration.

The option The Project Administrator for the project that contains the board is incorrect because a board can span multiple projects and project administrator rights do not give control over a saved filter owned by another user. Project admins do not automatically become board or filter owners unless they were given those specific permissions.

The option Any account with Jira Software product access is incorrect because general product access alone does not permit changing a board s configuration. Only the saved filter owner or users who have been explicitly made board administrators or given access to edit the filter can update the configuration.

Focus on the concept of ownership when a question mentions a saved filter. Ownership and explicit board admin rights usually determine who can change board configuration.

The correct options are A site administrator will maintain and configure the field for use across projects, The field should accept only a single selectable value, and Every project needs the ability to add this field to their issue screens.

A site administrator will maintain and configure the field for use across projects is correct because custom fields are typically created and configured at the global or site level so that they can be standardized, managed centrally, and made available to many projects. Central administration ensures consistent behavior and permissions across the instance.

The field should accept only a single selectable value is correct because a custom field can be defined as a single-select field when you need one value chosen from a predefined list. That data shape is a common reason to use a custom field rather than a free text field or a multi select option.

Every project needs the ability to add this field to their issue screens is correct because custom fields that are created globally can be added to multiple projects and screens. If the intent is to let projects opt in and place the field on their own issue types and screens then a globally managed custom field is appropriate.

The assignee must be automatically set based on the chosen value is incorrect because automatic assignment is achieved with workflow post functions or automation rules rather than by the custom field itself. A custom field can carry the value but it does not by itself perform automatic assignee changes.

A project administrator will be responsible for managing the field within their project is incorrect because creation and configuration of custom fields is normally a site or system administration task. Project administrators can add existing fields to screens and schemes when permissions allow but they do not typically create global custom fields for the whole instance.

When a question contrasts global and project scoped settings remember that global configuration implies a site administrator role and availability across projects while per project features are managed by project administrators.

Company-managed Kanban board is correct.

Company-managed Kanban board allows administrators to define separate workflows per issue type so stories and tasks can follow independent workflows. Company-managed projects also provide centralized version and release management which lets teams publish a release from the project and from board views. A Kanban board is designed for continuous flow and it maps to publishing releases directly from the board when required.

Team-managed Scrum board is incorrect. Team-managed projects use simplified, project level settings and they do not support independent workflows per issue type, so stories and tasks would share the same workflow and the release controls are more limited.

Team-managed Kanban board is incorrect. Although Kanban supports continuous delivery, the team-managed variant lacks the advanced project administration needed to set separate workflows for stories and tasks and to manage releases centrally from the board.

Company-managed Scrum board is incorrect. Company-managed projects supply the workflow flexibility but Scrum boards are sprint oriented and focus on sprint planning and cadence rather than a continuous board based release flow, so they do not match the requirement to publish a release directly from the board as naturally as a Kanban board.

When a question asks for independent workflows and the ability to publish releases from the board focus on company-managed projects for workflow flexibility and choose Kanban when the team needs a continuous release flow.

The correct answers are Introduce a screen transition into the project workflow and Add an “Affects versions” field to an issue type’s field list.

Introduce a screen transition into the project workflow is not possible because team-managed projects use a simplified, project-scoped workflow editor that does not support adding transition screens or the same screen-transition configuration that company-managed projects offer. The workflow and screen customization options are intentionally limited in team-managed projects to keep configuration simple.

Add an “Affects versions” field to an issue type’s field list is not possible because certain system fields are not exposed for per-issue-type field list customization in team-managed projects. Version fields are managed differently in team-managed projects and you cannot add the Affects versions field to an issue type form in the same way you would in a company-managed project.

Create a bespoke issue type for the project is incorrect because team-managed projects allow you to create and manage custom issue types directly within the project.

Change project permissions scheme is incorrect because team-managed projects provide project-specific permission and access controls that you can change from the project settings, even though they are handled differently than shared permission schemes in company-managed projects.

Remember that team-managed projects use simplified, project-level configuration. If a question asks about advanced workflow or system field changes think about whether that feature exists only in company-managed projects.

Request that Maya be granted Jira Software product access.

This is required because ranking issues is a Jira Software capability and a user must have Jira Software product access at the site level to use backlog ranking or drag and drop ordering in team managed projects. Giving Maya the Member role in the project does not by itself provide Jira Software product access, so granting product access is the correct fix.

Grant Maya the “Administrator” role for the “BRICK” project is incorrect because becoming a project administrator is not necessary to rank issues and the administrator role does not grant site level product access that enables Jira Software features.

Change the “BRICK” project type to a company managed project is incorrect because changing the project type is not required to enable ranking. Team managed projects support ranking when the user has Jira Software product access, so converting the project is unnecessary.

Assign Maya the “Work on BRICK issues” project permission is incorrect because that project permission controls working on or editing issues and does not grant the Jira Software product access needed to use the ranking features.

Before changing roles or permissions check a user�s Jira product access in site administration as product access is often the root cause when users cannot use Jira Software features.