Jira ACP-620 Exam Dumps and Braindumps

At NovaTech Solutions you must create an automation rule in a company managed project so that when a new issue is created and it is linked to a parent epic the new issue inherits the epic’s due date. How should you implement this behavior?

• ❏ A. Use the Issue Created trigger then run a branch for the parent epic and then edit the parent epic’s “Due date”

• ❏ B. Use the Issue Created trigger then apply a condition that checks if an associated epic exists and then edit the issue fields to set the “Due date”

• ❏ C. Use the Issue Created trigger then apply a condition that the issue type equals Epic and then edit the issue fields to set the “Due date”

• ❏ D. Use the Issue Created trigger then run a branch for linked issues and then copy the parent epic’s “Due date” into the new issue

Mateo’s squad needs a new board for managing their backlog. Their criteria are that the team works in one week iterations, that issues can be organized by assignee on the board, and that the board shows the due date for every issue. Which board type satisfies these requirements?

• ❏ A. Team managed Scrum board

• ❏ B. Kanban board

• ❏ C. Company managed Scrum board

• ❏ D. Team managed Kanban board

The company run Kanban board “NEPTUNE” shows these project roles and their permissions. Browse Projects is assigned to Project Role “Reviewers” and Project Role “Dev team”. Application access is Jira Software. Edit issue is assigned to Project Role “Audit team” and Project Role “Reviewers”. Create issues is assigned to Project Role “Audit team” and Project Role “Reviewers” and Project Role “Dev team”. Create attachments is assigned to Project Role “Reviewers” and Project Role “Dev team”. Ashley needs the ability to only create issues. Which role or roles should be granted to Ashley to meet that requirement?

• ❏ A. The “Dev team” role

• ❏ B. The “Audit team” and the “Dev team” roles

• ❏ C. The “Reviewers” role

• ❏ D. The “Audit team” role

Every issue that Maia files is linked to an Epic in her team backlog and Maia wants to estimate how many more sprints will be required to finish an Epic that has been active for several months. Which chart can she use to forecast the remaining sprint count?

• ❏ A. Cumulative flow diagram

• ❏ B. Burndown chart

• ❏ C. Control chart

• ❏ D. Epic burndown report

• ❏ E. Velocity chart

Which statements about quick filters used on Scrum and Kanban boards are accurate? (Choose 2)

• ❏ A. Quick filters are limited to a single project

• ❏ B. Quick filters exist only on company managed boards

• ❏ C. Any person who can view the board may apply its quick filters

A consultancy manages a company driven Kanban board for Meridian Labs and the project follows this permission mapping. Administrators have the Administer project permission. Administrators and the Product Crew have Browse projects. Any logged in user has Modify reporter. Developers Administrators and the Squad have Assignable user. Developers Administrators the Product Crew and the Squad have Edit issues. Administrators and the Squad have Assign issues. Maria must be able to change the assignee and modify the reporter and she must be granted the minimal permissions required. Which role or roles does Maria need to meet these requirements while observing the least privilege principle?

• ❏ A. The Developers role and the Product Crew role

• ❏ B. The Administrators role

• ❏ C. The Developers role and the Squad role

• ❏ D. The Squad role and the Product Crew role

Priya needs her squad to continuously complete work and avoid piling up too many tasks in the “In Progress” column on their board. Which Jira project type should she select?

• ❏ A. Team-managed Scrum project

• ❏ B. Team-managed Kanban project

• ❏ C. Company-managed Kanban project

• ❏ D. Company-managed Scrum project

Priya manages a Kanban board for Nimbus Solutions and she needs issues that have been resolved for longer than six weeks to be removed from the board automatically while leaving the board agile reports unchanged. What is the most operationally efficient way to achieve this?

• ❏ A. Quick filters

• ❏ B. Hide completed issues older than setting

• ❏ C. Board sub-filter

• ❏ D. Automation rule to transition or archive issues

Maya created a saved filter to monitor critical incidents and subscribed her operations team to it. She scheduled the subscription to send email alerts each morning at 07:30 AM. The subscription worked as expected and messages arrived on schedule for several weeks. When she attempted to add an additional group to the subscription she found she could not modify the group list even though she continued to receive the subscription emails. Which permission was revoked for Maya?

• ❏ A. Application access

• ❏ B. Project permission

• ❏ C. Manage shared objects permission

• ❏ D. Global permission

Which JQL returns issues from the APOLLO and OCEANA projects while excluding any issues that have the label “CHK”?

• ❏ A. project in (APOLLO, OCEANA) AND labels != “CHK”

• ❏ B. project = APOLLO OR project = OCEANA OR labels != “CHK”

• ❏ C. project in (APOLLO, OCEANA) AND (labels is EMPTY OR labels not in (“CHK”))

A support group uses automation rules limited to specific project boundaries. Which of the following scopes are not permitted for automation rules? (Choose 2)

• ❏ A. Multiple selected projects

• ❏ B. Project grouping category

• ❏ C. All projects in the site

• ❏ D. Project type

• ❏ E. Cross instance projects

• ❏ F. Single project

A development group at NovaSoft adds a subtask to an issue that is already in an active sprint and the Scrum board is configured to burn down estimates when work is completed. How will the added subtask affect the sprint scope and the burndown chart?

• ❏ A. The subtask will not change the sprint scope and it will be shown on the burndown chart

• ❏ B. The subtask will not alter the sprint scope and it will not appear on the burndown chart

• ❏ C. The subtask will count as a change to sprint scope yet it will not be represented on the burndown chart

• ❏ D. The subtask will update the sprint scope and it will appear on the burndown if the board uses remaining estimate or time tracking fields

Daniel manages a company-managed project that uses the simplified workflow and his board shows four columns from left to right as follows “Backlog” “Selected for development” “In Progress” and “Done”. In the Board settings Daniel changed the “Backlog” column label to “To Do” and removed the “Selected for development” column. Which statement is true?

• ❏ A. The status that was linked to “Selected for development” appears in the Unmapped statuses area of the Columns settings

• ❏ B. Renaming the “Backlog” column renames the corresponding project status to “To Do”

• ❏ C. Removing the “Selected for development” column deletes that status from the project workflow

• ❏ D. The board backlog capability becomes disabled after the column is deleted

In what situations is it preferable to use project components instead of a shared custom field in IssueFlow? (Choose 2)

• ❏ A. Only the system administrator will control the new field globally

• ❏ B. The component selection should automatically set the issue assignee

• ❏ C. Every project across the instance can reuse this field on their screens

• ❏ D. Users must be limited to choosing only a single value from the new field

• ❏ E. The project administrator will be responsible for maintaining the new field

Which board configuration settings can cause a board to display fewer issues than a project search that returns issues in the “Backlog” and “In Progress” statuses? (Choose 4)

• ❏ A. Issue security levels

• ❏ B. Board filter

• ❏ C. Quick filters

• ❏ D. Column mapping

• ❏ E. Board sub-filter

Maya is the scrum master and project lead for the company project “NEBULA” and she needs a JQL query that lists all standard issue types in the active sprint that are not yet resolved?

• ❏ A. issuetype in standardIssueTypes() and sprint in openSprints() and project = “NEBULA” and statusCategory != “Done”

• ❏ B. issuetype != sub-task and sprint in openSprints() and project = “NEBULA” and status not in (“Done”)

• ❏ C. issuetype in standardIssueTypes() and sprint = openSprints() and project = “NEBULA” and resolution is EMPTY

• ❏ D. issuetype != sub-task and sprint = currentSprint() and project = “NEBULA” and status != “Done”

A delivery team at scrumtuous.com is examining the default role set assigned to a team managed project and wants to know which role from the list does not come preconfigured in that type of project?

• ❏ A. Viewer

• ❏ B. User

• ❏ C. Administrator

• ❏ D. Member

Lina has just been hired as the technical lead for SkillForge. Her responsibilities include installing and managing Jira plugins keeping project schemes updated and configuring global Jira settings. Which Jira user type is most appropriate for these responsibilities?

• ❏ A. Site administrators

• ❏ B. Jira administrators

• ❏ C. Project administrators

• ❏ D. Jira Software users

Your lead asked you to automatically hide cards from a Kanban board that have been resolved for more than 10 days without altering the board reports. Which board configuration would you use to accomplish this? (Choose 2)

• ❏ A. Quick filters

• ❏ B. “Hide completed issues older than” setting

• ❏ C. Board filter

• ❏ D. Board sub-filter

• ❏ E. Create an automation rule to archive resolved issues older than 10 days

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

Which Jira configuration can copy the Reviewer custom field from a parent issue to a subtask’s Assignee when the subtask is transitioned to Pending Review? (Choose 2)

• ❏ A. Listener

• ❏ B. Workflow post-functions

• ❏ C. Project default assignee

• ❏ D. Automation rule

As the project administrator for an organization-managed project at a small finance startup named NovaLedger which changes to the issue view layout can you make within that project? (Choose 2)

• ❏ A. Change tabs in the issue layout

• ❏ B. Place the Resolution field into the description fields area

• ❏ C. Set a field to be hidden when it contains no value

• ❏ D. Make a field mandatory using the project settings

• ❏ E. Reorder fields within the issue layout

Priya must set up a new Jira board for her delivery group. What options can she choose when creating the board? (Choose 3)

• ❏ A. Create a board using a saved filter she can view

• ❏ B. Create a board for a brand new Jira project

• ❏ C. Create a board from an unshared saved filter

• ❏ D. Google Cloud Storage

• ❏ E. Build a board that aggregates issues from several existing projects

When reviewing a control chart for a development team at Skylark Solutions which pattern indicates that the team has steady productivity?

• ❏ A. Several data points fall well outside the control limits

• ❏ B. The rolling average trends downward across multiple iterations

• ❏ C. The rolling average remains close to the mean line

• ❏ D. A histogram shows a narrow spread of cycle times

A group of engineers at Meridian Software work across multiple Jira projects and they can view every project and they also have the ‘Move Issues’ permission in each project. They are unable to relocate issues into a few specific projects. What could be the root cause?

• ❏ A. They do not have the Browse Projects permission in the destination projects

• ❏ B. They are missing the Create Issues permission in the destination projects

• ❏ C. They lack the Transition Issues permission in the target projects

• ❏ D. They do not have the Edit Issues permission in the affected projects

How can a board administrator restore drag and drop ranking on a Jira Scrum board that no longer allows issues to be reordered?

• ❏ A. Remove any ORDER BY clause from the board filter

• ❏ B. Add “ORDER BY Rank ASC” to the board filter

• ❏ C. Add “ORDER BY Rank DESC” to the board filter

A development group at Nimbus Systems is comparing features between organization-managed projects and team-managed projects in their issue tracker. Which capabilities are not available in team-managed projects but are present in organization-managed projects? (Choose 2)

• ❏ A. Roadmaps

• ❏ B. Versions

• ❏ C. Issue security levels

• ❏ D. Releases

• ❏ E. Sub-filter configurations

A newly hired scrum master has joined Meridian Insights and they need the ability to create reorder and complete sprints on your company managed Scrum board. Which permissions must be granted to allow those sprint management operations? (Choose 2)

• ❏ A. Board administrator role

• ❏ B. Project permission to manage sprints

• ❏ C. Manage boards site permission

• ❏ D. Jira Software product access

• ❏ E. Global permissions

Which statements accurately describe the board capabilities in Sprintwise when using Scrum and Kanban boards? (Choose 4)

• ❏ A. Quick filters are available on both Scrum and Kanban boards

• ❏ B. Both Scrum and Kanban boards can apply sub filters to the board query

• ❏ C. Estimations can only be recorded while issues are in the backlog and only on Scrum boards

• ❏ D. Kanban boards are the only board type that can hide completed issues from the active board view

• ❏ E. Both Scrum and Kanban boards are ordered by rank by default

Maya is a release coordinator and wants a consolidated view of all versions scheduled for release within the next 45 days and a graphical summary of progress toward completing the issues in those versions. Which gadget should she add to her dashboard?

• ❏ A. Projects

• ❏ B. Sprint Burndown gadget

• ❏ C. Release Roadmap gadget

• ❏ D. Activity Stream

Which requirement can be satisfied only by the Components field in an enterprise managed project? (Choose 2)

• ❏ A. Allow selecting multiple values

• ❏ B. Project interface that lists issues per component

• ❏ C. Required field that sets assignee from selected component

At Nimbus Solutions there is an unresolved high priority issue and Alex needs to send a scheduled email every Monday morning to three separate teams to report on its status. Which Jira feature must Alex configure to accomplish this?

• ❏ A. Notification scheme

• ❏ B. Saved filter subscription

• ❏ C. Workflow post function

• ❏ D. Automation rules

A development team at Solstice Software is setting up a sprint board and they want to be clear about how estimation and time logging operate on the board. Which statement about board estimations and time tracking is accurate?

• ❏ A. Velocity Chart can only show values when story points are used as the estimation metric

• ❏ B. Estimates may use any numeric custom field as the board estimation statistic

• ❏ C. Every board built on a project must use the same estimation statistic

• ❏ D. Estimations can only be entered for Epic and Story issue types while time can be logged on every issue type

Which fields are the standard Jira time tracking fields that capture the original plan the actual time recorded and the remaining effort? (Choose 3)

• ❏ A. Planned hours

• ❏ B. Time spent

• ❏ C. Story points

• ❏ D. Remaining estimate

• ❏ E. Time consumed

• ❏ F. Original estimate

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

In a hosted Jira Cloud instance for HarborTech which categories of users are allowed to create a team-managed project? (Choose 4)

• ❏ A. Users with a Jira Service Management agent license

• ❏ B. Anonymous visitors

• ❏ C. Any user with an account on the site

• ❏ D. Users with Jira Software licenses

• ❏ E. Customers of a service desk project

• ❏ F. Project administrators

Which board feature ensures that a component filter affects both the board and its Cumulative Flow Diagram?

• ❏ A. Quick Filters

• ❏ B. Board Sub Filter

• ❏ C. Swimlanes

• ❏ D. Board Filter

Which patterns on a control chart for the engineering group at MapleTech indicate the team is becoming less productive? (Choose 2)

• ❏ A. The rolling average line remains very close to the mean line

• ❏ B. Multiple issues plotted below the average line

• ❏ C. Several consecutive data points located above the mean line

• ❏ D. A sustained upward trend in the rolling average line

• ❏ E. A declining spread in individual cycle times

Orion Kanban company managed project uses the following permission assignments. Administer project is granted to project role Administrators. Browse projects is granted to project roles Administrators Users Managers Auditors. Assignable user is granted to project roles Auditors Administrators. Edit issues is granted to project roles Administrators Managers. Resolve issues is granted to project roles Auditors Managers Users. Close issues is granted to project roles Administrators Auditors Managers. Manage sprints is granted to project roles Administrators Auditors. Schedule issues is granted to project roles Auditors Administrators. Set issue security is granted to project roles Administrators Managers. Diane needs to be able to set the “Fix version” field on issues and change the issue security level while receiving the minimum permissions necessary. Which project role or roles should Diane be assigned to accomplish these requirements?

• ❏ A. Users and Auditors roles

• ❏ B. Administrators role

• ❏ C. Managers and Auditors roles

• ❏ D. Managers role

Which of the following statements about creating boards in Jira Software is not true?

• ❏ A. A new board can be created from an existing saved filter

• ❏ B. Boards can aggregate issues from multiple existing projects

• ❏ C. Boards can only be created from a single existing company managed project

• ❏ D. A user can create a board during the setup of a new Software project

Which statements are accurate regarding the JQL expression labels != TASK-342? (Choose 3)

• ❏ A. Issues that have no labels will be returned by labels != TASK-342

• ❏ B. Issues with other labels and without the TASK-342 label will appear in the results

• ❏ C. labels is not TASK-342 will behave the same as labels != TASK-342

• ❏ D. Issues that include the TASK-342 label will be excluded from the results

• ❏ E. labels not in (TASK-342) returns an identical set of issues as labels != TASK-342

Which Jira user roles can create automation rules at the project level and which can create them at the global level? (Choose 2)

• ❏ A. Site administrators

• ❏ B. Project administrators

• ❏ C. Project lead

• ❏ D. Jira administrators

You and your team at Aurora Labs are building a decentralized application and you track work on an organization managed scrum board. The workflow maps statuses to columns named To Do In Development QA Done with resolution set to Done and Archived with resolution set to Closed. After you complete a sprint you notice issues that are in Done still show up in the backlog. Why does this occur?

• ❏ A. The person who completed the sprint does not have the “Manage sprints” project permission

• ❏ B. The person who finished the sprint is not the board administrator

• ❏ C. The resolution field must be cleared for those issues

• ❏ D. The Done column is not the right most column

Amira added a custom field named Deployment Environment with values Production and Non Production and she needs a table that groups issues by those values and displays the overall status for each group. Which report should she use?

• ❏ A. Time Tracking Report

• ❏ B. Two Dimensional Filter Statistics Report

• ❏ C. Average Age Report

• ❏ D. Single Level Group By Report

• ❏ E. Pie Chart Report

• ❏ F. Resolution Time Report

A product team at Orion Labs is setting up custom fields for their issue tracker. They require field types that permit only a single selectable value, allow a default value to be set, and support different available values depending on the project. Which field types satisfy these requirements? (Choose 2)

• ❏ A. Radio button field

• ❏ B. Components field

• ❏ C. Single user picker field

• ❏ D. Labels field

• ❏ E. Single version picker field

• ❏ F. Project selector field

• ❏ G. Single line text field

A product team at HarborSoft uses a team managed project in their issue tracker. From the project details page which project attributes can the project administrator edit? (Choose 4)

• ❏ A. Project template

• ❏ B. Project lead

• ❏ C. Project key

• ❏ D. Description

• ❏ E. Project name

• ❏ F. Project category

In the project tracker, which capabilities are available on both team boards and enterprise managed boards? (Choose 4)

• ❏ A. Show the Versions panel

• ❏ B. Configure automation rules for transitions

• ❏ C. Enable the Backlog view

• ❏ D. Access the Cycle Time report

• ❏ E. Show the Epics panel

A development group at Meridian Labs uses TaskBoard Cloud and needs to reorder work items in the backlog. Which permissions must a person have to move issues within the backlog? (Choose 4)

• ❏ A. Create issues project permission

• ❏ B. TaskBoard application access

• ❏ C. Manage sprints project permission

• ❏ D. Browse projects project permission

• ❏ E. Manage boards project permission

• ❏ F. Schedule issues project permission

• ❏ G. Edit issues project permission

• ❏ H. Rank issues global permission

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

Maya is working in a company managed project at Meridian Systems and she can view all issues with Advanced issue search yet several issues are missing from her Scrum board. What could explain why those issues do not appear on the board? (Choose 3)

• ❏ A. The board configuration’s saved filter or its JQL was modified

• ❏ B. The user lacks Issue Security Level access

• ❏ C. The viewer has enabled a Quick Filter on the board

• ❏ D. The board has a sub filter JQL that excludes some issues

• ❏ E. Some statuses are placed in the Unmapped Statuses column

• ❏ F. The user lacks Browse Projects permission

A project lead at NovaApps needs a built in report that shows the results of a saved filter and groups the issues by priority while displaying a progress bar for each priority that indicates the percent and the number of issues resolved out of the total for that priority. Which report should they use?

• ❏ A. Average age report

• ❏ B. Single level group by report

• ❏ C. Resolution time report

• ❏ D. Time tracking report

Which Jira role should Marta be granted if she needs to manage project role membership update project settings and maintain boards and field configurations?

• ❏ A. Jira administrators

• ❏ B. Jira Software users

• ❏ C. Project administrators

• ❏ D. Site administrators

Which scope options can be selected when configuring automation rules? (Choose 4)

• ❏ A. Single project

• ❏ B. User group

• ❏ C. Global

• ❏ D. Multiple projects

• ❏ E. Project type

NovaWorks uses a Kanban board with columns labeled “Backlog” “Development” “Peer Review” and “Done”. You move a ticket into “Development” and it stays there for 3 days. You then transition the ticket into “Peer Review” for 2 days. After receiving feedback you move the ticket back into “Development” and it remains there for 2 more days. At the end of that final day what will the days in columns indicator display for this ticket?

• ❏ A. 2 days

• ❏ B. 5 days

• ❏ C. 3 days

• ❏ D. 7 days

A newly onboarded team at HorizonApps has provisioned a Cloud site and enabled Jira Software Cloud and Jira Work Management Cloud with all defaults in place. Which statement about team managed projects and default roles is accurate?

• ❏ A. All Jira Work Management users can create issues in team managed projects when the project visibility is Public

• ❏ B. Users assigned the default project role Developer can create issues in a team managed project where that role is applied

• ❏ C. All Jira Work Management users can set issue due dates in team managed projects whose access level is set to Limited

• ❏ D. Every user with Jira Software product access can create team managed projects by default

As the project administrator for a team-managed project at AuroraApps you need to update the issue layout for a specific issue type to enforce or prefill certain fields What actions are permitted on the issue layout? (Choose 3)

• ❏ A. Define a default tag for the “Labels” field

• ❏ B. Move the “Description” field even though the description area only contains “Summary” and “Description”

• ❏ C. Mark custom fields as required

• ❏ D. Remove the “Summary” field from the issue form

• ❏ E. Edit the default helper text of the “Description” field

Which fields are always present in the issue details panel for a company-managed project board and cannot be changed in the default layout? (Choose 2)

• ❏ A. Status

• ❏ B. Linked issues

• ❏ C. Description

• ❏ D. Assignee

• ❏ E. Summary

What types of visibility restrictions can be enforced by Jira issue level security? (Choose 2)

• ❏ A. Only the team lead can view all issues

• ❏ B. Only the team lead can move tickets between projects

• ❏ C. External customers can only see the tickets they reported

• ❏ D. Issue security controls who can edit issues

Use the Issue Created trigger then apply a condition that checks if an associated epic exists and then edit the issue fields to set the “Due date” is correct.

The rule should fire on issue creation and then verify whether the newly created issue is linked to an epic. If an associated epic exists then the rule can read the epic’s due date and edit the new issue so it inherits that due date.

Use the Issue Created trigger then run a branch for the parent epic and then edit the parent epic’s “Due date” is incorrect because it updates the epic instead of setting the created issue to inherit the epic due date.

Use the Issue Created trigger then apply a condition that the issue type equals Epic and then edit the issue fields to set the “Due date” is incorrect because that only applies when the created issue itself is an epic and it will not handle child issues that are linked to an existing epic.

Use the Issue Created trigger then run a branch for linked issues and then copy the parent epic’s “Due date” into the new issue is incorrect because branching on generic linked issues may not reliably detect the epic relationship in company managed projects and it adds unnecessary complexity compared with a condition that checks for an associated epic followed by an edit action.

When you need to copy data from a parent epic prefer a rule that checks for an associated epic and then edits the created issue rather than branching to update the parent.

The correct option is Company managed Scrum board.

A Company managed Scrum board supports fixed length sprints so the team can run one week iterations. It lets you organize and view issues by assignee on the board and it provides board configuration options to display the due date field on cards for every issue. These configuration capabilities make it the best fit for all three requirements.

Team managed Scrum board is incorrect because team managed projects are simpler and offer fewer board configuration options. They can support sprints but they give less control over card fields and board level customizations so they may not reliably show due dates for every issue.

Kanban board is incorrect because Kanban is designed for continuous flow and does not use fixed length iterations. That means it cannot satisfy the one week iteration requirement even though it can show assignees and due dates.

Team managed Kanban board is incorrect because it also lacks sprint support and has limited card customization compared to company managed projects. It therefore cannot meet the one week iteration requirement and may not display due dates as needed.

When a question requires fixed length sprints and full card customization prefer company managed Scrum boards. Focus on whether the board supports sprint configuration and card field visibility when choosing an option.

The correct option is The “Audit team” role.

The “Audit team” role is the minimal project role that provides the Create issues permission while avoiding the roles that grant Browse Projects or Create attachments. Granting this role allows Ashley to be given the ability to create issues without also giving the broader access that the other roles confer.

The “Dev team” role is incorrect because that role also grants Browse Projects and Create attachments in addition to Create issues. Those extra permissions give more access than the requirement of only creating issues.

The “Audit team” and the “Dev team” roles is incorrect because combining roles would grant the extra privileges from the Dev team role such as Browse Projects and Create attachments. The combination therefore exceeds the requirement.

The “Reviewers” role is incorrect because that role includes Browse Projects and Create attachments and it also shares Edit issue with the Audit team. The Reviewers role therefore grants additional capabilities beyond just creating issues.

When an exam asks for a role that grants only one capability look for the least privileged role that contains that specific permission. Use the project permissions table and compare which roles add extra permissions before selecting the answer.

The correct answer is Epic burndown report.

The Epic burndown report is built to show remaining work for an epic over time and it displays scope changes and completed work across multiple sprints so it is the report you would use to forecast how many more sprints are required to finish an epic that has been active for several months.

Cumulative flow diagram shows the amount of work in each workflow state over time to help identify bottlenecks and stability issues and it does not directly present remaining epic scope or a sprint based forecast.

Burndown chart typically tracks remaining work for a single sprint or a fixed release window and it is not focused on the multi sprint progress and scope changes of an epic that spans many sprints.

Control chart displays cycle time and the distribution of issue lead times to help assess process predictability and it is not intended to forecast the number of sprints left for an epic.

Velocity chart reports the average completed work per sprint and it can support rough forecasting but it does not show remaining epic scope or scope changes over time in the way the epic burndown report does so it is not the best single chart for this question.

When you need to forecast remaining sprints for an epic look for a report that tracks remaining epic work and scope changes over time. Epic burndown is the most direct tool for that task.

The correct answers are Quick filters exist only on company managed boards and Any person who can view the board may apply its quick filters.

Quick filters exist only on company managed boards is correct because quick filters are created and managed in the board settings that are available on company managed boards. Team managed projects do not provide the same quick filter configuration so quick filters are typically a feature of company managed boards and they are saved with the board.

Any person who can view the board may apply its quick filters is correct because quick filters act as client side controls that apply the board’s filter or JQL for any viewer. Users do not need additional board permissions just to toggle quick filters and the results still respect issue and project permissions so users only see issues they are allowed to view.

Quick filters are limited to a single project is incorrect because quick filters are defined at the board level and a board can be backed by a filter that spans multiple projects. Quick filters run against the board’s underlying query so they are not constrained to one project.

When you encounter questions about board features focus on whether the feature lives in board settings or in the project itself. Remember that visibility of results still depends on users’ issue and project permissions.

The Squad role and the Product Crew role are correct.

To change the assignee you need the Squad role because it grants the Assign issues permission while the Modify reporter permission is already available to any logged in user. You also need the Product Crew role because it grants Browse projects which is required to access the project and make changes. Together the two roles give exactly the permissions required and follow least privilege principles.

The Developers role and the Product Crew role is wrong because the Developers role does not grant the Assign issues permission needed to change the assignee even though the Product Crew role provides Browse projects.

The Administrators role is wrong because it would work for the actions but it grants Administer project and other high level permissions and so it violates least privilege by giving far more access than required.

The Developers role and the Squad role is wrong because the combination still does not provide Browse projects. The Developers role does not include Browse projects so Maria would not have project access with just those two roles.

When a question asks for minimal permissions map the required actions to concrete permissions such as Assign issues, Browse projects, and Modify reporter. Remember that Modify reporter is often granted to any logged in user so focus on the missing project level permissions and pick the smallest role set that fills those gaps.

The correct answer is Company-managed Kanban project.

A Company-managed Kanban project is designed for continuous flow and it supports configurable work in progress controls and classic board features that help prevent too many issues from piling up in the In Progress column. The company managed option provides the richer workflow and board configuration needed to enforce WIP limits and automation that keep work moving steadily.

Team-managed Scrum project is incorrect because Scrum is based on fixed length sprints and sprint planning rather than continuous flow and column WIP enforcement.

Team-managed Kanban project is incorrect because team managed projects use simplified configuration and historically lack some of the classic board controls and enterprise level settings that let you enforce WIP limits across a team.

Company-managed Scrum project is incorrect because even though it is company managed it follows the Scrum framework with iterations and sprint boundaries instead of the continuous pull system that Kanban provides.

When a question mentions continuous flow or limit tasks in progress prefer a Kanban board and choose the company-managed option when the need is for enforceable WIP limits and advanced board controls.

The correct option is Board sub-filter.

Using Board sub-filter allows Priya to add a JQL clause that excludes issues resolved more than six weeks ago from the board display while leaving the board’s main filter and agile reports unchanged. This approach applies automatically to the board view and does not modify issue data or reporting filters.

Quick filters are incorrect because they require users to turn them on manually and they do not automatically remove issues from the board in the background.

Hide completed issues older than setting is incorrect because that setting is not as flexible as a JQL sub-filter and it can affect broader board behavior rather than providing a precise, board-only exclusion based on resolution date.

Automation rule to transition or archive issues is incorrect because automations would change issue state or archive items and that alters reporting and increases operational overhead compared with a simple board-level filter.

When a question asks to change only what appears on a board but not reports think about a board-level control such as a sub-filter rather than automations or user-only quick filters.

Global permission is correct.

Global permission governs actions that span across projects and shared configurations so revoking it can stop a user from changing who is subscribed to a saved filter while leaving the scheduled emails intact. Maya continued to receive the subscription emails because the subscription job and delivery remained active, but the revoked Global permission removed her ability to modify the subscription membership.

Application access is incorrect because application level access would typically block using an integration or API and would not selectively prevent editing a subscription list while still allowing emails to be sent. The fact that Maya still received messages shows application access was not the issue.

Project permission is incorrect because project scoped permissions apply only to resources within a single project. The scenario describes a change to a shared subscription and recipient list that is governed at a broader scope than a single project.

Manage shared objects permission is incorrect because that permission would specifically cover sharing objects but it does not necessarily control the global ability to edit subscription membership across the system. The symptom points to a global scope restriction rather than that specific sharing right.

When a question mentions changing shared settings or subscriber lists pay attention to the scope implied by the action. Look for words like global or project and match the permission scope to the action required.

The correct option is project in (APOLLO, OCEANA) AND (labels is EMPTY OR labels not in (“CHK”)).

project in (APOLLO, OCEANA) AND (labels is EMPTY OR labels not in (“CHK”)) works because it limits results to the two named projects and then explicitly includes issues that have no labels while also excluding issues that carry the CHK label. The labels is EMPTY portion ensures unlabeled issues are returned and the labels not in (“CHK”) portion filters out any issue that contains the CHK label.

project in (APOLLO, OCEANA) AND labels != “CHK” is incorrect because the != operator does not match empty fields in JQL. That query will omit issues that have no labels and so it will miss unlabeled issues from the two projects.

project = APOLLO OR project = OCEANA OR labels != “CHK” is incorrect because the OR makes the label condition apply globally. That query can return issues from other projects as long as their labels are not CHK, so it does not properly restrict results to APOLLO and OCEANA.

Remember that != does not match empty fields in JQL so include is EMPTY when you want to capture issues with no value.

The correct options are Project grouping category and Cross instance projects.

Project grouping category is not permitted because automation rules that are limited to specific project boundaries must target explicit projects or defined multi project selections and not broader categories that group projects for reporting or administration. The automation engine requires concrete project targets so a category cannot be used as a rule scope.

Cross instance projects is not permitted because automation rules run within a single instance and cannot operate across separate instances. Rules cannot reach into another instance to read or modify projects so cross instance targeting is not supported.

Multiple selected projects is incorrect because automation commonly supports selecting several projects as the rule scope and multi project rules allow you to include multiple specific projects.

All projects in the site is incorrect because site level or global rules can apply to all projects within the same instance when that scope is allowed by the automation configuration.

Project type is incorrect because rules can be applied based on project characteristics and you can often target projects by type or use other selectors to include projects that share attributes.

Single project is incorrect because limiting a rule to a single project is a standard and supported scope for automation rules.

When you see scope related words in the question focus on whether the rule must operate within the same instance and whether the scope requires explicit project targets. Pay attention to the phrase cross instance as a clear indicator of an unsupported scope.

The subtask will count as a change to sprint scope yet it will not be represented on the burndown chart.

Adding a subtask to an issue that is already in an active sprint increases the sprint scope because there is now an additional work item assigned to that sprint. The burndown chart in a board that burns down estimates when work is completed only reflects estimate changes when work is finished, so creating a new subtask does not immediately change the burndown until the subtask s estimate is completed or consumed.

The subtask will not change the sprint scope and it will be shown on the burndown chart is incorrect because adding a new subtask does change sprint scope. The statement also wrongly assumes the burndown will immediately reflect the new work item when the board is configured to burn down completed estimates.

The subtask will not alter the sprint scope and it will not appear on the burndown chart is incorrect because it denies the scope change that occurs when a new work item is added to an active sprint. The part about not appearing on the burndown is only half true for this board configuration.

The subtask will update the sprint scope and it will appear on the burndown if the board uses remaining estimate or time tracking fields is incorrect in this scenario because the board is configured to burn down estimates when work is completed. That configuration does not show the new subtask on the burndown until the estimate is completed or the completed-estimate metric is affected.

When a subtask or issue is added mid sprint check whether the board burns down completed estimates or uses remaining estimates. That setting determines whether the burndown chart immediately reflects the change.

The status that was linked to “Selected for development” appears in the Unmapped statuses area of the Columns settings is correct.

The status that was linked to “Selected for development” moves to the Unmapped statuses area when you remove its column on a simplified workflow board because removing a column only removes the column-to-status mapping on the board and does not delete the underlying status in the project. The board retains the project status but it is no longer mapped to any column so it appears in the Unmapped statuses area until you map it to another column.

Renaming the “Backlog” column renames the corresponding project status to “To Do” is incorrect because renaming a column in board settings changes only the column label that users see on the board. The underlying project status name is not renamed by changing a board column label in a simplified workflow.

Removing the “Selected for development” column deletes that status from the project workflow is incorrect because deleting a column on a board does not delete the project status itself. The status remains in the project workflow and will appear in the Unmapped statuses area rather than being removed from the workflow.

The board backlog capability becomes disabled after the column is deleted is incorrect because removing a column does not automatically disable the backlog feature. The backlog capability depends on board configuration and the presence of a backlog column, but deleting a column simply changes mappings and does not globally turn the backlog feature off.

When a question mentions board column changes think about mapping versus deletion. Mapping changes affect the board view and labels while the underlying project statuses remain unless you explicitly edit the workflow or status itself. Remember to look for terms like “unmapped” or “mapping” on the exam.

The correct options are The component selection should automatically set the issue assignee and The project administrator will be responsible for maintaining the new field.

Choosing The component selection should automatically set the issue assignee indicates that the selection must trigger per-project automation such as assigning the issue to a specific person. Project components are designed to carry that kind of project-level metadata and to drive automatic assignee behavior when a component is chosen.

Choosing The project administrator will be responsible for maintaining the new field signals that the field should be owned and edited at the project level rather than by a system administrator. Project components are maintained by project administrators so they fit scenarios where local ownership and upkeep are required.

Only the system administrator will control the new field globally is incorrect because that describes a globally shared custom field that is managed by the system administrator, which is the opposite of choosing a project-level component.

Every project across the instance can reuse this field on their screens is incorrect because reusable global fields are a feature of shared custom fields, not project components which are scoped and managed per project.

Users must be limited to choosing only a single value from the new field is incorrect because the choice of single versus multiple values is a configuration detail that does not by itself determine whether to use a project component or a shared custom field.

When the question mentions local ownership or manual maintenance by project admins favor project components. When it mentions global reuse or system administrator control favor a shared custom field.

The correct answers are Quick filters, Board filter, Column mapping, and Board sub-filter.

Board filter defines the base JQL that determines which issues belong to the board. If the board filter is narrower than a project search then some issues that appear in the project will not be part of the board and so they will not show in Backlog or In Progress on that board.

Quick filters are additional, user selectable filters applied on top of the board. When a quick filter is active the board shows only the issues that match that quick filter. That can make the board display fewer issues than a plain project search which does not apply those quick filters.

Column mapping controls which issue statuses are mapped to the board columns and to the backlog. If a status is not mapped into the columns that the board shows then issues in that status can be hidden from the expected Backlog or In Progress views, which makes the board list differ from a project search.

Board sub-filter is an additional JQL that can exclude issues from the board view even though they are returned by the main board filter. A sub-filter is commonly used to hide certain issue types or issues in a particular state and that exclusion can make the board show fewer issues than a project search.

Issue security levels are not a board configuration setting. Issue security levels restrict which users can see specific issues across the application and they would also affect project search results for those users. That means they do not explain a difference caused by board settings alone.

When issues appear in a project search but not on a board first turn off all quick filters and then compare the board filter and sub-filter with your project JQL. Also check column mappings to ensure the statuses you expect are mapped to visible columns.

The correct answer is issuetype in standardIssueTypes() and sprint in openSprints() and project = “NEBULA” and statusCategory != “Done”.

The query uses issuetype in standardIssueTypes() to include only standard issue types and to exclude subtasks. It uses sprint in openSprints() to target issues in active sprints. The project clause limits results to “NEBULA” and statusCategory != “Done” excludes any issue whose status belongs to the Done category which is more reliable across different workflows than checking a single status name or only resolution.

issuetype != sub-task and sprint in openSprints() and project = “NEBULA” and status not in (“Done”) is incorrect because excluding a type by name can miss other subtask type names and because using specific status names is less robust than using statusCategory. The syntax also risks mistakes if the issue type name is not exact.

issuetype in standardIssueTypes() and sprint = openSprints() and project = “NEBULA” and resolution is EMPTY is incorrect because sprint = openSprints() uses the equality operator with a function that must be used with IN. Also filtering by resolution is EMPTY can miss issues that are marked done without a resolution value, so it is not as reliable as using statusCategory.

issuetype != sub-task and sprint = currentSprint() and project = “NEBULA” and status != “Done” is incorrect because currentSprint() is not a standard JQL function and the equality form for sprint is invalid. The issuetype exclusion and status != “Done” have the same robustness problems as the other incorrect options.

When you see JQL functions check whether they require the IN operator and prefer statusCategory != “Done” to catch all done statuses across workflows.

The correct option is User. The other roles that appear by default in a team managed project are Administrator, Member, and Viewer so they are not the correct choice.

Team managed projects use a simplified set of built in roles and the defaults are the Administrator, the Member, and the Viewer. There is no separate default User role in that project type, so User is the role that does not come preconfigured.

Viewer is an incorrect option because it is provided by default to grant read only access in team managed projects.

Administrator is an incorrect option because it is the built in role for project administration in team managed projects.

Member is an incorrect option because it is the default role used for normal project contributors in team managed projects.

When answering role questions confirm whether the question refers to a team-managed project or a company-managed project. The default role names differ and that difference lets you eliminate answers quickly.

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

The correct option is Jira administrators.

Jira administrators are responsible for product level administration in Jira. They can install and manage apps and plugins configure global Jira settings and manage schemes that affect multiple projects. Lina’s tasks of installing and managing Jira plugins keeping project schemes updated and configuring global settings align directly with the responsibilities of a Jira administrator.

Site administrators manage the Atlassian site itself including user access product subscriptions and billing and they do not necessarily perform product specific tasks such as installing Jira plugins or updating Jira project schemes.

Project administrators control settings only within individual projects and they can manage project level configurations and permissions but they cannot install global plugins or change global Jira settings that affect the whole product.

Jira Software users are regular users who work on issues and boards and they do not have administrative privileges to install apps or alter global or product level configurations.

Match the scope of the duties in the question to the scope of the role. Global or product level tasks point to Jira administrators while project level tasks point to project administrators.

“Hide completed issues older than” setting and Board sub-filter are correct.

“Hide completed issues older than” setting is a built in board option that automatically removes completed or resolved cards from the Kanban board view after the specified number of days. This setting changes only how issues are displayed on the board and does not modify the board filter or the underlying issue data, so reports that rely on the board filter remain unchanged.

Board sub-filter lets you apply an additional JQL clause to the board display without altering the main board filter that reports use. You can add a sub-filter that excludes resolved issues older than 10 days and the board will hide those cards while the saved board filter used for reports stays the same.

Quick filters are incorrect because they are user toggles that must be applied manually and they do not automatically hide issues on a schedule.

Board filter is incorrect because changing the main board filter alters the filter that reports use and therefore would affect board reports.

Create an automation rule to archive resolved issues older than 10 days is incorrect because an automation that archives or changes issues will modify issue data and therefore affect reports, and it is unnecessary when the built in hide setting or a board sub-filter can hide the cards from the board view without changing historical data.

When the question requires hiding items from a board without affecting reports look for options that only change the board display such as the hide completed UI setting or a board sub-filter rather than changing the main board filter or altering issue data.

The correct options are Workflow post-functions and Automation rule.

Workflow post-functions run as part of the issue transition and can update fields on the issue that is being transitioned. This makes them a natural fit for copying a parent issue custom field into a subtask assignee at the moment the subtask moves to Pending Review because the change happens as part of the transition logic.

Automation rule can trigger on an issue transition and then use smart values to read the parent issue’s custom field and set the subtask’s assignee. Automation is flexible and works well when you want a no-code, configurable rule that reacts to the Pending Review transition across projects or issue types.

Listener is not the best answer because event listeners are usually a development level solution that require custom code or add-ons and they are not the typical UI configuration an admin would use for a simple transition copy.

Project default assignee is incorrect because that setting applies to newly created issues when no assignee is specified and it does not perform dynamic copying of a parent field to a subtask when a transition occurs.

When a change must happen exactly during a transition think post-function. When you need broader or reusable logic that reads related issues use automation.

The correct options are Set a field to be hidden when it contains no value and Reorder fields within the issue layout.

Set a field to be hidden when it contains no value is supported because the issue view layout lets project administrators control field visibility and they can choose to hide fields that have no value to keep the issue view concise.

Reorder fields within the issue layout is supported because the issue layout editor provides the ability to move fields around within the layout for the project without changing global field configurations.

Change tabs in the issue layout is incorrect because tab configuration is handled by screens and screen schemes or by global settings rather than by the per project issue layout editor.

Place the Resolution field into the description fields area is incorrect because the Resolution field is a system field with special behavior and its placement and behavior are governed by screens and workflows rather than by moving it into arbitrary description sections in the issue layout.

Make a field mandatory using the project settings is incorrect because making a field required normally requires changes to the workflow or the field configuration which are global or require higher level administration rather than being a simple toggle in the project issue layout.

Focus on whether the change affects only the visual layout and visibility or whether it changes field behavior and validation. Visual edits like ordering and hiding are often allowed at the project level while making a field required usually needs workflow or global field configuration changes so look for that difference in exam questions.

The correct options are Create a board using a saved filter she can view, Create a board for a brand new Jira project, and Build a board that aggregates issues from several existing projects.

Create a board using a saved filter she can view is correct because Jira boards can be created from saved filters and the creator must be able to view the filter so the board can use its JQL to populate issues.

Create a board for a brand new Jira project is correct because boards can be tied to a single project and you can create a board when you set up or target a newly created project so it will surface the issues for that project.

Build a board that aggregates issues from several existing projects is correct because a board can be scoped using a filter or project selection that spans multiple projects and this is a common way to track cross project work.

Create a board from an unshared saved filter is incorrect because an unshared filter that is not visible to the user cannot be used as the basis for a board. The filter must be accessible to the board owner.

Google Cloud Storage is incorrect because it is unrelated to creating Jira boards and is not an option when configuring boards in Jira.

When you see options about Jira boards think about whether the board is based on a project or a saved filter. Remember that the filter must be viewable or shared to be used and that boards can span multiple projects.

The correct answer is The rolling average remains close to the mean line.

A rolling average that stays near the mean line indicates the process is stable and that variation is common cause rather than special cause. This pattern shows the team is delivering at a consistent rate across iterations and there are no persistent trends or sudden shifts in performance.

Several data points fall well outside the control limits is incorrect because points outside control limits indicate special cause variation and instability. Those signals suggest the process is not steady and that an investigation is needed to identify and correct unusual events.

The rolling average trends downward across multiple iterations is incorrect because a downward trend shows declining productivity rather than steady performance. A steady team would show no long directional trends in the rolling average.

A histogram shows a narrow spread of cycle times is incorrect because a histogram captures the distribution of past data but it does not show stability over time. A narrow spread can indicate low variability but it does not prove the process is stable unless the time series shows no trends or special cause signals.

When a question asks about steady productivity look for measures that show stability over time and no trends or outliers. Focus on time-ordered charts like control charts rather than distribution-only views.

The correct option is They are missing the Create Issues permission in the destination projects.

This is correct because moving an issue into another project requires the ability to create an issue in the destination project. A move operation effectively creates the issue in the target project and then removes it from the source project, so the user must have the Create Issues permission in the destination even if they already have Move Issues in the source.

They do not have the Browse Projects permission in the destination projects is not the root cause because the engineers can view every project which indicates they already have the browse permission for those destinations.

They lack the Transition Issues permission in the target projects is incorrect because the Transition Issues permission controls workflow state changes and is unrelated to moving issues between projects.

They do not have the Edit Issues permission in the affected projects is incorrect because Edit Issues governs modification of issue fields after creation and is not required to perform a move into a project.

When troubleshooting moves check both the source and destination project permissions and pay particular attention to Create Issues in the destination and Move Issues in the source.

Add “ORDER BY Rank ASC” to the board filter is correct because explicitly ordering the board by the Rank field in ascending order is what enables Jira to maintain and update the rank when you drag issues on a Scrum board.

Jira uses the Rank field to represent the manual order of issues and the board query must sort by that field for reordering to work. Including ORDER BY Rank ASC in the board filter tells Jira to present issues in Rank order so the system can update the Rank when you drag and drop issues.

Remove any ORDER BY clause from the board filter is incorrect because omitting an explicit ORDER BY can allow the board to use a different or unpredictable sort and that prevents reliable manual ranking.

Add “ORDER BY Rank DESC” to the board filter is incorrect because using descending order reverses the expected Rank sequence and Jira requires the board to be ordered by Rank in ascending order for drag and drop ranking to function properly.

When a board will not allow reordering check the board filter in Board settings and make sure it explicitly uses ORDER BY Rank ASC.

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

The correct options are Issue security levels and Sub-filter configurations.

Team-managed projects do not support Issue security levels. Issue security relies on global security schemes that restrict visibility at the issue level and those schemes can only be applied in organization managed projects. Team-managed projects use simplified, project scoped permissions and cannot attach an issue security scheme to the project.

Team-managed projects also do not provide configurable board Sub-filter configurations. Sub-filters are board level JQL settings that let you hide or exclude issues from board and sprint views and those advanced board configurations are available only in organization managed projects. Team-managed boards use simplified filtering and do not expose a separate sub-filter setting.

Roadmaps is incorrect because team-managed projects include a built in roadmap feature. The roadmap in team-managed projects is simpler than the company managed roadmap but it is available to teams.

Versions is incorrect because team-managed projects support versions and a releases area where you can create and manage project versions.

Releases is incorrect because team-managed projects provide a releases page to track and manage versions and releases for the project.

When comparing project types focus on whether a feature requires a global scheme or advanced board JQL. Features that need global schemes or detailed board configuration are usually only available in organization managed projects.

The correct answers are Project permission to manage sprints and Jira Software product access.

You must grant the Project permission to manage sprints at the project level because that specific permission controls creation, reordering, and completing of sprints on a Scrum board. This permission is configured in the project permissions and is required for the user to perform sprint lifecycle actions within that project.

You also must grant Jira Software product access because sprint functionality is provided by Jira Software and the user needs a Jira Software license to access boards and sprint features. Product access enables the UI and feature set that make sprint management possible.

The Board administrator role is incorrect because being a board admin allows configuration of the board and filters but does not inherently grant the project permission to create or manage sprints.

The Manage boards site permission is incorrect because it is a higher level site capability for administering boards across the site and it does not replace the project level sprint management permission or the need for Jira Software access.

The Global permissions entry is incorrect because global permissions control broad administrative abilities and do not by themselves grant the specific project level ability to manage sprints or provide product access.

When answering permissions questions, check for both a required product license and the specific project permission because many features need both to work correctly.

The correct options are Quick filters are available on both Scrum and Kanban boards, Estimations can only be recorded while issues are in the backlog and only on Scrum boards, Kanban boards are the only board type that can hide completed issues from the active board view and Both Scrum and Kanban boards are ordered by rank by default.

Quick filters are available on both Scrum and Kanban boards because quick filters act at the board view level and let users temporarily narrow which issues are visible without changing the underlying board query. That makes them useful on either board type for focusing on specific issue attributes or workflow states.

Estimations can only be recorded while issues are in the backlog and only on Scrum boards means that estimate values are entered during backlog refinement or sprint planning and are not captured on the active Kanban board. Scrum workflows rely on backlog estimates for sprint planning while Kanban emphasizes flow and work in progress rather than backlog-based estimation.

Kanban boards are the only board type that can hide completed issues from the active board view because Kanban focuses on continuous flow and keeping the active board uncluttered. Hiding completed issues helps teams maintain visibility on work in progress while completed work is not shown on the active Kanban board. Scrum boards typically retain completed items within the sprint until the sprint is completed.

Both Scrum and Kanban boards are ordered by rank by default since rank determines the relative ordering of issues on the backlog or within columns and is the default sorting method on both board types. Users can reorder items manually which updates the rank used by the board.

Both Scrum and Kanban boards can apply sub filters to the board query is incorrect because sub filters are not available on both board types. Sub filter capabilities are limited to specific board configurations and are not applied to Scrum boards in the same way they are on Kanban boards in Sprintwise.

When answering board capability questions check whether the feature applies to the backlog or the board view and pay attention to qualifiers like only and both as they often determine the correct choice.

The correct option is Release Roadmap gadget.

The Release Roadmap gadget is built to show a consolidated timeline of versions that are scheduled for release in a configurable time window and it provides graphical progress indicators for each version so you can quickly see how close each release is to completion. This makes it the right choice when you need a view of all versions due in the next 45 days and a summary of progress toward completing the issues in those versions.

Projects is not correct because it focuses on listing or linking to projects and basic project information and it does not provide a timeline view of upcoming release versions with progress bars.

Sprint Burndown gadget is not correct because it tracks progress within a single sprint and shows burndown information for that sprint rather than showing release versions across a release window or a graphical summary of version completion.

Activity Stream is not correct because it provides a feed of recent activity and changes and it does not present a consolidated roadmap or graphical progress for scheduled releases.

When a question asks for a consolidated timeline of releases and progress look for keywords like roadmap or release and match those to gadgets that show version timelines rather than gadgets that show activity or sprint level charts.

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

Project interface that lists issues per component and Required field that sets assignee from selected component are correct.

The Project interface that lists issues per component is a direct capability of the Components feature because components are project level entities that provide built in filtering and views so you can open a component and see the issues that belong to it. That project level listing and quick navigation is something components provide as part of the project interface.

The Required field that sets assignee from selected component is also provided by components because each component can have a designated lead or default assignee and the Components field can be made required so that selecting a component drives who gets assigned either directly or through simple project automation. That integration between component selection and assignee behavior is not something generic fields provide by default.

The Allow selecting multiple values option is incorrect because allowing multiple selections is not unique to the Components field. Other field types such as multi select custom fields or labels also allow multiple values so that requirement is not something that only Components can satisfy.

When an exam question asks which capability is unique to a field ask whether other standard fields can do the same. Focus on project level features such as built in views and default assignee behavior to spot the unique answers.

The correct option is Automation rules.

The Automation rules feature lets Alex schedule a rule to run every Monday and then send an email to the three teams. The feature supports scheduled triggers, can include issue fields or filter results in the message, and can target users, groups, or specific email addresses so it is the right tool for recurring status reports.

Notification scheme defines who receives notifications for issue events based on roles and events in a project and it is not designed for scheduling weekly reports. It reacts to issue events rather than running on a recurring schedule.

Saved filter subscription can deliver filter results on a schedule to subscribers but it is limited to sending search results to subscribed users and it does not offer the same formatting, conditional logic, or flexible recipient handling that automation rules provide.

Workflow post function runs when an issue transitions in the workflow and it cannot independently run on a weekly schedule to send reports. It is tied to workflow actions so it is not appropriate for scheduled notifications.

When a question mentions recurring or scheduled emails focus on features that offer scheduled triggers and flexible actions to target recipients and format content.

The correct option is Estimates may use any numeric custom field as the board estimation statistic.

This is correct because boards let you select which numeric field will act as the estimation statistic and that field can be a custom numeric field you create or a built in numeric field. The board uses that numeric field for backlog estimation displays and for reports that aggregate completed estimates per sprint.

Velocity Chart can only show values when story points are used as the estimation metric is incorrect because the velocity chart will display values whenever a numeric estimation statistic is configured and issues in the sprint have values for that field. It does not require the field to be story points specifically.

Every board built on a project must use the same estimation statistic is incorrect because estimation is set at the board level. Different boards in the same project can use different estimation statistics if the field configurations allow it.

Estimations can only be entered for Epic and Story issue types while time can be logged on every issue type is incorrect because whether an issue type can hold estimates depends on whether the estimation field is available to that issue type. Estimation is not limited to Epic and Story by default and time logging availability depends on permissions and field contexts rather than on a strict issue type rule.

Check the board settings to confirm the estimation statistic and then check the project field configuration to see which issue types the numeric field applies to. That quickly tells you how estimates and reports will behave.

The correct options are Original estimate, Time spent, and Remaining estimate.

The Original estimate records the planned amount of time for the work before any time is logged and it serves as the baseline plan for the issue.

The Time spent field captures the actual time that users log against the issue and it represents the recorded effort that has already been consumed.

The Remaining estimate shows how much time is still expected to complete the issue after accounting for logged work and it is updated as progress is made.

The Planned hours option is not a standard Jira time tracking field. It may be used as a custom field in some projects but it is not one of Jira’s built in time tracking names.

The Story points option measures relative size or complexity for agile estimation and it does not represent time, so it is not a time tracking field.

The Time consumed option is not a standard Jira field name. Jira tracks logged work with Time spent rather than a field called Time consumed, so this option is not correct in the default Jira schema.

When asked about Jira time tracking pick the fields that represent the planned amount, the logged effort, and the remaining work. Remember that Story points are for relative estimation and are not measured in time.

The correct options are Users with a Jira Service Management agent license, Any user with an account on the site, Users with Jira Software licenses, and Project administrators.

Team managed projects can be created by users who have the appropriate product access or site account when project creation is enabled. Users with Jira Software licenses typically have the product access that allows them to create team managed projects. Users with a Jira Service Management agent license also have product access that can permit project creation depending on site settings. Any user with an account on the site can create a team managed project when the site allows self service project creation for account holders.

Project administrators can create or configure projects according to the permissions granted to their role and they can create team managed projects if their administrative rights and the site settings permit it.

Anonymous visitors cannot create projects because they are not authenticated users and they do not hold licenses or site accounts that grant creation rights.

Customers of a service desk project are external requesters and they do not have the product access or site permissions required to create team managed projects.

When answering permissions questions focus on whether the person is authenticated and whether they have product access or an assigned license. Site settings that allow self service project creation are also commonly tested.

The correct option is Board Filter.

Board Filter is the saved JQL that defines which issues belong to the board and the Cumulative Flow Diagram is generated from that board scope. Because the CFD uses the board filter the component clause must be included in the board filter for the component to appear in both the board and its CFD.

Quick Filters are temporary view level filters that change what you see on the board in the browser and they do not modify the underlying board JQL so they do not affect the CFD.

Board Sub Filter is an additional restriction sometimes used for special contexts like active sprints and it does not replace the main board filter that the CFD uses so it will not guarantee the component shows in the CFD.

Swimlanes only change how issues are grouped visually on the board and they do not change which issues are included in the board definition so they have no effect on the CFD.

When a question asks what affects both a board and a report focus on saved filters and JQL. Look for the phrase Board Filter as the setting that controls board scope and derived reports.

Several consecutive data points located above the mean line and A sustained upward trend in the rolling average line are correct because they both indicate the team is taking longer to complete work and overall productivity is decreasing.

Several consecutive data points located above the mean line indicate a sustained shift where many cycle times are higher than the expected average. A run of points on one side of the mean suggests the process has changed and that throughput is dropping.

A sustained upward trend in the rolling average line reveals that the smoothed average of cycle times is increasing over time. A rising rolling average filters short term noise and highlights a genuine decline in productivity when it continues upward.

The rolling average line remains very close to the mean line is incorrect because that pattern shows stability and no consistent increase in cycle times. Stability is not evidence of decreasing productivity.

Multiple issues plotted below the average line is incorrect because points below the mean represent faster than average cycle times which would indicate improvement or normal variation rather than decline.

A declining spread in individual cycle times is incorrect because reduced variability means greater consistency and does not by itself show that work is taking longer. A narrowing spread can accompany process improvement.

When evaluating control charts focus on persistent patterns such as sustained runs or trends and treat isolated points as less important. Use runs and trend rules to spot real shifts in performance early.

Managers role is correct.

The Managers role grants the Edit issues permission and the Set issue security permission which are the two capabilities Diane needs. The Edit issues permission lets a user modify issue fields such as the Fix version field and the Set issue security permission lets a user change the issue security level.

Users and Auditors roles is incorrect because that combination does not provide the Set issue security permission and so cannot change the issue security level. Auditors do have Schedule issues but that does not allow changing security levels and Users do not have Edit issues to modify the Fix version field.

Administrators role is incorrect because although Administrators include the required permissions they also carry broad administrative rights that exceed the minimum needed. The question asks for the minimum permissions necessary and Administrators is more permissive than required.

Managers and Auditors roles is incorrect because adding Auditors to Managers is redundant and grants extra permissions such as Schedule issues and manage sprints. The Managers role alone already supplies both Edit issues and Set issue security so the extra role is not necessary.

Map the required user actions to specific project permissions and then choose the role that grants those permissions with the least extra privileges. Verify that the role includes both the ability to edit the Fix version field and to set issue security.

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

The correct answer is Boards can only be created from a single existing company managed project.

This statement is not true because Jira Software does not restrict board creation to a single company managed project. Boards can be created in different ways and their scope is determined by the board filter, so you can design a board to include issues from many sources rather than being limited to one project.

A new board can be created from an existing saved filter is not the correct choice because that statement is true. Jira allows you to create a board from a saved filter so the board shows the issues returned by that filter.

Boards can aggregate issues from multiple existing projects is not the correct choice because that statement is true. A board’s filter can include issues from many projects and the board will display those aggregated issues.

A user can create a board during the setup of a new Software project is not the correct choice because that statement is true. The project creation flow offers options to create a board as part of setting up a new software project.

Read each option carefully and convert it into a yes or no question about actual Jira behavior. Remember that boards are defined by filters so they can span multiple projects and can be created from saved filters.

The correct options are Issues with other labels and without the TASK-342 label will appear in the results, Issues that include the TASK-342 label will be excluded from the results, and labels not in (TASK-342) returns an identical set of issues as labels != TASK-342.

Issues with other labels and without the TASK-342 label will appear in the results is correct because the query filters out issues that contain the TASK-342 label while including issues that have other labels. The operator in this context matches issues where the label field exists and does not include the specified value.

Issues that include the TASK-342 label will be excluded from the results is correct because any issue whose labels contain TASK-342 is removed by the expression, so those issues do not appear in the result set.

labels not in (TASK-342) returns an identical set of issues as labels != TASK-342 is correct because the two forms are equivalent for excluding issues that contain the TASK-342 label. Both expressions target membership and yield the same set of issues in typical JQL usage.

Issues that have no labels will be returned by labels != TASK-342 is incorrect because the != and not in operators do not match empty label fields. Queries that must include unlabeled issues need an explicit check using is EMPTY.

labels is not TASK-342 will behave the same as labels != TASK-342 is incorrect because that phrasing is not the proper way to express a membership comparison in JQL and it is not equivalent to the != or not in operators for labels.

When comparing labels remember that != and not in exclude issues that contain the value and do not match empty fields. Use is EMPTY to find issues with no labels.

The correct options are Project administrators and Jira administrators.

Project administrators can create and manage automation rules that run only within their project. They have access to the project automation settings and can build, edit, and delete rules scoped to that project without needing global permissions.

Jira administrators can create global automation rules that apply across multiple projects and they can configure global automation settings. Global rules and global automation configuration require Jira administrator permissions.

The option Site administrators is incorrect because being a site administrator is an account level role and it does not automatically grant the Jira administration or project administration permissions needed to create automation rules.

The option Project lead is incorrect because the project lead role does not necessarily include project administrator rights. A project lead cannot create project scoped automation rules unless they have been granted project administrator permissions.

When answering remember to match the scope of the rule to the role. Global scope needs Jira administrators and project scope needs Project administrators.

The Done column is not the right most column is correct.

Jira only treats issues as finished for the board when their statuses are mapped to a column that is in the Done category and that column sits at the rightmost side of the board. If the The Done column is not the right most column then issues in that column are not considered to be in the final state for board filtering and they will continue to appear in the backlog after a sprint completes.

The person who completed the sprint does not have the “Manage sprints” project permission is incorrect because this symptom is about how the board treats statuses and columns and not about who has sprint permissions. Sprint permissions affect who can start or complete sprints but they do not change how the board maps done statuses.

The person who finished the sprint is not the board administrator is incorrect because board administrator status does not determine whether issues are excluded from the backlog. The visibility of completed issues is controlled by column and status configuration rather than by the identity of the person who finished the sprint.

The resolution field must be cleared for those issues is incorrect because clearing the resolution would mark issues as unresolved and could make them appear even more in active views. The resolution should usually be set for completed issues and the key requirement here is that the Done status is mapped to a rightmost Done column.

When a backlog still shows completed issues check the board column setup first and confirm that the Done category is mapped to the rightmost column before changing permissions or resolutions.

The correct answer is Single Level Group By Report.

Single Level Group By Report groups issues by a single field such as a custom field and shows aggregated counts and status information for each group so Amira can group by the Deployment Environment field and see the overall status for Production and Non Production.

Time Tracking Report focuses on original estimates, time spent, and remaining time and does not provide a grouped status summary by a custom field.

Two Dimensional Filter Statistics Report creates a matrix of counts by two fields and is meant for cross tabulation rather than a simple single-field group with an overall status summary.

Average Age Report shows how the average age of unresolved issues changes over time and does not present grouped status summaries by a custom field.

Pie Chart Report can show distribution of issues by a field but it does not display the overall status per group in the same way as a group by report and is less suitable for a status summary per Deployment Environment.

Resolution Time Report measures time to resolution and related metrics and does not group current issue status by a custom field for a grouped status overview.

Look for keywords that say whether the report must group by a single field or provide status summaries. If the question asks for grouping by one custom field and an aggregated status choose a single level group by style report.

Radio button field and Single user picker field are correct.

Radio button field enforces a single selectable choice because radio controls allow only one selection. It also supports a default option and custom field contexts let you provide different option lists per project so it meets all three requirements.

Single user picker field allows selecting exactly one user and can be given a default user. It supports project specific behavior through field contexts and schemes so the available values or behavior can vary by project.

Components field is incorrect because component fields are tied to project components and often allow multiple selections rather than enforcing a single selectable value.

Labels field is incorrect because labels are freeform and multi valued. They do not provide a constrained single choice with per project option sets.

Single version picker field is incorrect because version pickers are tied to project versions and do not offer the same configurable list and default behavior across projects as the required custom field types.

Project selector field is incorrect because it chooses a project rather than providing a project specific set of single selectable options within an issue field context.

Single line text field is incorrect because it accepts freeform input and does not provide a predefined single selectable option or project specific selectable values.

When a question asks for a field that is a single choice and can vary by project think of predefined choice controls and pickers rather than free text or label fields. Pay attention to whether the field supports a default value and field contexts.

The correct options are Project name, Project key, Project category, and Project lead.

A project administrator on a team managed project can edit the Project name and the Project key because those control how the project is labeled and how issue keys are generated. The administrator can also change the Project category to group the project with related work and can assign or replace the Project lead who is the accountable user for the project.

Project template is incorrect because the template for a team managed project is selected when the project is created and it is not changed from the project details page. To adopt a different template you normally need to create a new project or migrate content.

Description is incorrect because the project details page does not provide the editable description field in the same way as the core metadata listed above. Description may be shown or edited in other parts of the product but it is not one of the attributes modified on the project details page for team managed projects.

Visualize the actual project details page when answering these questions and focus on core metadata fields. Remember that templates are typically fixed at creation while name, key, category, and lead are commonly editable.

The correct options are Show the Versions panel, Enable the Backlog view, Access the Cycle Time report, and Show the Epics panel.

Both team boards and enterprise managed boards expose core user views and reporting features so they both include release or version information in the UI and allow users to view and manage it. That is why Show the Versions panel is available on both board types. The backlog is a standard board view used for planning and grooming so Enable the Backlog view is present on both. Flow and lead time reporting is provided through standard reports so Access the Cycle Time report is available for both board flavors. Epic grouping and navigation are a common work management feature so Show the Epics panel appears on both team and enterprise managed boards.

Configure automation rules for transitions is incorrect because automation setup is an administrative capability that can be implemented and governed differently between board types and project configurations. That configuration is not guaranteed to be available in the same way on both team boards and enterprise managed boards so it cannot be assumed to be a shared capability.

When the question asks which features are common focus on user-facing views versus administration controls. User views like backlog or epics are more likely to be shared while administration features such as automation configuration often differ.

TaskBoard application access, Browse projects project permission, Schedule issues project permission, and Edit issues project permission are the correct options.

TaskBoard application access is required so the user can open and use the TaskBoard Cloud interface where backlog ordering is performed. If a user cannot access the application they cannot move items inside that app.

Browse projects project permission is required so the user can view the project and its backlog. Without browse rights the backlog and the issues in it are not visible and the user cannot reorder items.

Schedule issues project permission allows the user to change scheduling fields that some boards or backlog views use when repositioning or managing issue order. This permission often underpins reordering actions that adjust planned dates or releases.

Edit issues project permission is required so the user can modify the issue fields that the board uses to reflect position or status. Reordering usually makes changes to issue fields so edit rights are necessary.

Create issues project permission is incorrect because creating new issues is not required to move existing items within the backlog.

Manage sprints project permission is incorrect because managing sprint settings or starting and closing sprints is different from reordering backlog items.

Manage boards project permission is incorrect because changing board configuration is not required for a user to move issues within an existing backlog view.

Rank issues global permission is incorrect in this scenario because the TaskBoard Cloud workflow requires application access along with project level browse, schedule, and edit rights instead of that global permission.

When you see a permissions question think about whether the action requires application access, project visibility, or the ability to change issue fields. Match each action to the minimal permission that enables it.

The correct answers are: The board configuration’s saved filter or its JQL was modified, The viewer has enabled a Quick Filter on the board, and Some statuses are placed in the Unmapped Statuses column.

The board configuration’s saved filter or its JQL was modified is correct because a Scrum board only displays issues that match its saved filter. If that filter or its JQL was changed then issues that still appear in Advanced Issue Search can be excluded from the board view.

The viewer has enabled a Quick Filter on the board is correct because Quick Filters restrict which issues are shown on the board for the current view. Quick Filters do not alter the underlying saved filter so issues may be visible in search but hidden on the board while a quick filter is active.

Some statuses are placed in the Unmapped Statuses column is correct because issues in statuses that are not mapped to any active board column will not appear on the main board columns. Unmapped statuses can be placed in a separate or collapsed column which makes those issues seem missing from the board.

The user lacks Issue Security Level access is incorrect because Maya can see all issues in Advanced Issue Search. If issue security levels were blocking access then those issues would not be visible in search either.

The board has a sub filter JQL that excludes some issues is incorrect in this context because the scenario points to changes in the board filter, active Quick Filters, or unmapped status mappings as the likely causes. While sub-filters can restrict results they are not the most direct explanation given the information provided.

The user lacks Browse Projects permission is incorrect because Maya is able to view the issues in Advanced Issue Search which indicates she has browse permission. Lack of browse permission would prevent those issues from appearing in search as well as on boards.

When issues are visible in search but not on a board first check the board filter, then check any active Quick Filters, and finally check the column status mappings.

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

The correct answer is Single level group by report.

The Single level group by report groups the results of a saved filter by a single field such as Priority and it displays a progress bar for each group that indicates the percent complete along with the number of issues resolved out of the total for that group. This behavior matches the requirement to group issues by priority and show both percent and resolved counts per priority.

The Average age report is incorrect because it shows the average age of unresolved issues and not grouped progress bars by priority or resolved counts.

The Resolution time report is incorrect because it focuses on time to resolution metrics such as average resolution time or time distributions and it does not provide grouped progress bars showing percent resolved per priority.

The Time tracking report is incorrect because it summarizes estimates and time spent and remaining and it does not show the number resolved out of the total or percent resolved grouped by priority.

When a question asks for a report that groups by a field and shows progress per group look for reports that explicitly group by a single field and display progress bars or counts so you can match the wording in the requirements to the report name.

The correct answer is Project administrators.

Project administrators are granted the permissions needed to manage project role membership and to update project settings. They can also maintain boards and configure fields that apply within the project so they match the behaviors Marta needs.

Jira administrators are not the right choice because that role is focused on system and global configuration and it is broader than the project level tasks described.

Jira Software users are regular product users and they do not have rights to manage project roles or change project settings and configurations.

Site administrators manage users and site wide settings and access for the entire Atlassian site and they are not required for routine project level administration.

When a question asks about changing roles or settings that affect a single project think project level and choose a project focused role rather than a global or licensing role.

Single project, Global, Multiple projects, and Project type are correct.

Single project scope limits an automation rule to a single project so the rule only evaluates and acts on issues within that one project. This is useful when a workflow or requirement is unique to a particular project and you do not want the rule to affect other projects.

Multiple projects scope allows a rule to run across a selected set of projects. You can target several projects at once when the same automation logic applies to more than one team or product without making the rule global.

Project type scope enables applying a rule to all projects of a given type. This is helpful when you want a consistent automation across all software projects or all business projects and you want to avoid selecting projects individually.

Global scope runs the rule across the entire instance so it can act on issues in any project. Use this when the automation must apply universally and you have the necessary administrative permissions to create rules at the global level.

User group is incorrect because rule scopes are defined by project boundaries or instance level context rather than by membership of a user group. You can restrict who can trigger or modify rules by permissions but you do not set the automation scope to a user group.

When deciding scope think about the blast radius of the rule and choose the narrowest scope that achieves the requirement. If you need the rule across many projects prefer Multiple projects or Project type rather than making it Global.

The correct answer is 5 days.

The days in columns indicator accumulates the time the ticket spent in the Development column across both visits. The ticket spent 3 days in Development the first time and then 2 more days after returning from Peer Review which totals 5 days.

The option 2 days is incorrect because that would reflect only the time since the ticket was last moved into Development and it ignores the earlier Development time.

The option 3 days is incorrect because that shows only the initial Development period and it does not include the two additional days after the ticket returned to Development.

The option 7 days is incorrect because that adds the time spent in Peer Review as well as Development and the days in columns indicator for Development reports time spent in that specific column rather than total time across all columns.

When a question asks about time in a column check whether the metric is cumulative across multiple visits or shows only the current visit and then add the separate intervals for the same column when needed.

The correct answer is Every user with Jira Software product access can create team managed projects by default.

This is because team managed projects in Jira Cloud are designed to be lightweight and easy for teams to create. By default any user who has Jira Software product access can create a team managed project, and site administrators can change who is allowed to create projects in the site administration settings if they need tighter control.

All Jira Work Management users can create issues in team managed projects when the project visibility is Public is incorrect. Public visibility generally allows viewing of project content but does not automatically grant every Jira Work Management user the permission to create issues. Issue creation is controlled by project membership and the project permissions configured in that project.

Users assigned the default project role Developer can create issues in a team managed project where that role is applied is incorrect. Team managed projects use simplified, project-specific permission schemes and roles are configurable at the project level. The presence of a role named Developer does not by itself guarantee issue creation rights unless the project has been configured to give that role the appropriate permissions.

All Jira Work Management users can set issue due dates in team managed projects whose access level is set to Limited is incorrect. Limited access means only explicitly added users can access the project, and the ability to edit fields such as due dates depends on the edit permissions granted within that project, not merely on product membership or the access level label.

On exam questions remember that product access often controls who can create team managed projects by default and that site administration settings can override the default behavior.

The correct answers are Define a default tag for the “Labels” field, Mark custom fields as required, and Edit the default helper text of the “Description” field.

The Define a default tag for the “Labels” field option is allowed because team-managed project issue layouts let you set default values for certain fields so new issues are prefilled with common tags.

The Mark custom fields as required option is allowed because you can mark custom fields as required on the issue layout to enforce that users provide the necessary information before an issue is created or transitioned.

The Edit the default helper text of the “Description” field option is allowed because the issue layout supports editing helper or placeholder text to guide users on what to enter in the description area.

Move the “Description” field even though the description area only contains “Summary” and “Description” is incorrect because the description area is a fixed part of the issue layout and you cannot reposition the Description independently of that fixed section.

Remove the “Summary” field from the issue form is incorrect because Summary is a required system field and it cannot be removed from the issue form in a team-managed project.

When answering UI configuration questions focus on whether a field is a system field or a custom field and on whether the project is team-managed. System fields are often required or in fixed areas while custom fields and helper text are more configurable.

All exam questions come from my ACP-620 Udemy Course and the certificationexams.pro website.

The correct options are Summary and Description.

Both Summary and Description are core elements of the issue details panel on a company-managed project board and they appear in the default issue layout. Summary supplies the short title that identifies the issue across boards and searches and Description holds the detailed content that explains the work to be done. Because they are fundamental parts of the issue view they cannot be removed from the default layout.

The Status field is governed by the workflow and its visibility can vary or be represented in other parts of the board so it is not guaranteed to be fixed in the default layout.

The Linked issues section shows related or blocked issues but it is an optional panel that can be added or omitted from the layout so it is not always present by default.

The Assignee field is configurable at the project level and teams can choose whether to show or hide it in their layouts so it is not a required part of the default issue details panel.

When a question mentions company-managed and the default layout focus on fields that are part of the core issue view because those are most likely to be fixed like Summary and Description.

The correct options are Only the team lead can view all issues and External customers can only see the tickets they reported.

Only the team lead can view all issues is correct because Jira issue level security schemes let administrators create security levels that restrict who can view an issue to specific users or roles. You can assign a security level that grants view access to a single person or to a defined role such as a team lead.

External customers can only see the tickets they reported is correct because customer access and issue security are commonly combined so that external users or customers only have visibility into the requests they created unless the project is configured to share more broadly.

Only the team lead can move tickets between projects is incorrect because the ability to move issues is controlled by the Move Issues permission and by project configuration rather than by issue visibility settings.

Issue security controls who can edit issues is incorrect because issue security governs who can view an issue and editing is controlled by the Edit Issues permission in the permission scheme.

When you see questions about issue level security think about visibility first and decide whether the feature changes who can see an issue or whether it enables actions like moving or editing.