I85PREP
⌘ K
ACP-420 study materials
ACP-420 study resources

ACP-420 practice questions

One question at a time. Build your ACP-420 understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Project creation, project types, and project-level configuration

Which Jira Cloud project type uses shared schemes such as permission, notification, and workflow schemes that can be reused by other projects?

  1. Team-managed projects
  2. Company-managed projects Correct answer.
  3. Only projects created from the default template use shared schemes
  4. Both project types use the same shared schemes

Explanation

Company-managed (formerly classic) projects are configured through schemes - issue type, workflow, field configuration, screen, permission, and notification - that can be attached to many projects at once. Team-managed projects keep a simplified configuration inside the project itself.

Question 2Project creation, project types, and project-level configuration

Which of these is a valid project key for a new Jira project?

  1. M-K-T
  2. MKT Correct answer.
  3. MKT 1
  4. 1MKT

Explanation

A project key must be at least two characters long, begin with a letter, and contain only letters and numbers; Jira displays it in uppercase. The key becomes the prefix of every issue key in the project, so it must also be unique across the site.

Question 3Project creation, project types, and project-level configuration

In a company-managed project, which values are offered for the Default Assignee setting?

  1. Project lead or Reporter
  2. Any user or any group
  3. Project lead or Unassigned Correct answer.
  4. Component lead or Unassigned

Explanation

On the project's Details page the default assignee can be set either to the project lead or to Unassigned. When Unassigned is chosen, new issues with no explicit assignee stay unassigned.

Question 4Project creation, project types, and project-level configuration

What is the main purpose of a project category in Jira Cloud?

  1. To set the default assignee for the project's issues
  2. To control which users can browse the project
  3. To define the workflow used by the project's issues
  4. To group related projects together Correct answer.

Explanation

A project category is a label that groups related projects so they can be located and filtered more easily, including through JQL. It has no effect on permissions, workflows, or assignments.

Question 5Project creation, project types, and project-level configuration

When you create a company-managed project, what does the selected template determine?

  1. The Jira license tier required to use the project
  2. The issue types and workflow the project starts with Correct answer.
  3. The maximum number of issues that can be created in the project
  4. The groups that will be granted the Administer Projects permission

Explanation

A template seeds the new project with a starter set of issue types, a workflow, and the related scheme configuration. Administrators can adjust all of it afterwards, but the template defines the starting point.

Question 6Project creation, project types, and project-level configuration

How many permission schemes can be associated with a single company-managed project at one time?

  1. Zero, because permissions are inherited from the site
  2. Up to three
  3. As many as the project requires
  4. Exactly one Correct answer.

Explanation

Every company-managed project is linked to exactly one permission scheme; that scheme may be the default or a custom one, and it may be shared with other projects. Multiple permission schemes cannot be layered on the same project.

Question 7Project creation, project types, and project-level configuration

A team-managed project is set to the Open access level. What does this mean?

  1. Only users explicitly added to the project can view it
  2. Anyone on the site can find and join the project Correct answer.
  3. Anyone on the internet, including anonymous users, can view issues
  4. Only the project administrator can view and edit issues

Explanation

Team-managed projects offer access levels that range from open to private. Open means people on the site can discover the project and join it themselves, while more restrictive levels require someone to add them.

Question 8Project creation, project types, and project-level configuration

Which statement describes what happens when a Jira administrator archives a project?

  1. The project's issues are permanently deleted after 30 days
  2. The project is converted into a team-managed project
  3. The project is hidden from project lists but remains fully editable
  4. The project becomes read-only but keeps its data Correct answer.

Explanation

Archiving takes a project out of active use by making it read-only and removing it from the active project list, while retaining its issues and configuration. The data can be accessed again if the project is restored.

Question 9Project creation, project types, and project-level configuration

In the default permission scheme, which permission is granted to the Project Lead role so the lead can manage the project?

  1. Browse Users and Groups
  2. Share Dashboards and Filters
  3. Administer Projects Correct answer.
  4. Administer Jira

Explanation

The default permission scheme grants Administer Projects to the Project Lead role, letting the lead edit project details, roles, and components. Administer Jira and the other listed permissions are global permissions that are never granted through a project role.

Question 10Project creation, project types, and project-level configuration

An administrator adds a group to the Browse Projects permission of a permission scheme that is shared by three projects. What is the result?

  1. The change applies only to newly created projects
  2. Only the project the administrator is viewing is affected
  3. All three projects that use that scheme are affected Correct answer.
  4. The group is added after each project is re-indexed

Explanation

A permission scheme is a standalone object, so editing it changes the permissions of every project that uses it. No per-project action is needed for the change to take effect.

Question 11Project creation, project types, and project-level configuration

Which scheme controls which workflow is used by each issue type in a company-managed project?

  1. The notification scheme
  2. The workflow scheme Correct answer.
  3. The field configuration scheme
  4. The issue type screen scheme

Explanation

A workflow scheme contains the mapping between issue types and workflows, plus a workflow used for any issue type that has no explicit association. The other schemes govern screens, field behaviour, and email notifications.

Question 12Project creation, project types, and project-level configuration

A field configuration scheme maps issue types to field configurations. What does each field configuration control?

  1. Which screens are displayed when an issue is created
  2. Which users may edit a field on an issue
  3. Whether each field is required, optional, or hidden Correct answer.
  4. Which workflow transitions are available for an issue

Explanation

A field configuration sets each field's required, optional, or hidden state and can also hold a field description for that configuration. It does not grant edit rights and does not affect transitions or screens.

Question 13Project creation, project types, and project-level configuration

Which scheme associates issue types with screen schemes so different issue types can display different screens?

  1. Issue type screen scheme Correct answer.
  2. Screen scheme
  3. Field configuration scheme
  4. Issue type scheme

Explanation

A screen scheme maps operations such as create, view, and edit to screens. An issue type screen scheme then maps each issue type to one of those screen schemes, which is how per-issue-type screens are achieved.

Question 14Project creation, project types, and project-level configuration

A user can view issues in a company-managed project but gets a permission error when creating one. Which is the most likely cause?

  1. The project's issue type scheme does not include the issue type chosen
  2. The project has no default assignee configured
  3. The permission scheme does not grant Create Issues to the user Correct answer.
  4. The user is not a member of any project role

Explanation

Viewing issues requires Browse Projects, while creating them requires the separate Create Issues permission. If the user receives Create Issues through no group or role in the permission scheme, creation is blocked even though the project is visible.

Question 15Project creation, project types, and project-level configuration

Which statement about project roles is correct?

  1. Project roles are used only by team-managed projects
  2. Project roles can contain only individual users
  3. Roles are defined per project and can hold users or groups Correct answer.
  4. Project roles are defined globally and shared by all projects

Explanation

Project roles belong to a single project, which is why the same role name can have different members in different projects. Permission and notification schemes reference these roles, and membership can include individual users as well as groups.

Question 16Project creation, project types, and project-level configuration

Who becomes a project administrator of a newly created team-managed project?

  1. The Jira administrator who installed the site
  2. The user who created the project Correct answer.
  3. The project lead of the closest company-managed project
  4. Every user in the site's default group

Explanation

In team-managed projects the creator is made a project administrator and can then manage settings, people, and features for that project. This is why team-managed projects reduce the need for site administrators to handle routine project changes.

Question 17Project creation, project types, and project-level configuration

An issue is moved between two company-managed projects without changing its issue type. Which condition must be satisfied?

  1. The target project must use the same project key
  2. The reporter must be a Jira administrator
  3. The issue type must exist in the target project Correct answer.
  4. The target project must not use a workflow scheme

Explanation

An issue type is available in a project only if it belongs to that project's issue type scheme. If the type is missing in the target project, Jira requires the mover to choose a different issue type during the move.

Question 18Project creation, project types, and project-level configuration

What determines the issue type pre-selected when a user creates an issue from the global Create button in a company-managed project?

  1. The project's default assignee setting
  2. The default issue type of the issue type scheme Correct answer.
  3. The workflow scheme's default workflow
  4. The first screen listed in the issue type screen scheme

Explanation

Each issue type scheme designates one of its issue types as the default, and that type is offered first when a new issue is started. Users can still change the type if more than one is available.

Question 19Project creation, project types, and project-level configuration

Which scheme determines who receives email notifications about issue activity in a company-managed project?

  1. The issue type scheme
  2. The field configuration scheme
  3. The permission scheme
  4. The notification scheme Correct answer.

Explanation

The notification scheme lists events such as issue created or commented, together with the users, groups, or roles notified for each event. Permission schemes control what people can do rather than what mail they receive.

Question 20Project creation, project types, and project-level configuration

Where does a project administrator change the project's lead and project category?

  1. In the project's issue type scheme
  2. On the project's Details page Correct answer.
  3. In the permission scheme of the project
  4. In the global project category settings page

Explanation

The Details page in project settings holds the project name, key, lead, default assignee, category, and URL. Editing it requires the Administer Projects permission, which project leads typically hold.

Question 21Project creation, project types, and project-level configuration

A Jira administrator deletes a company-managed project. What is possible during the following 30 days?

  1. Only the project's issues can be recovered, not its configuration
  2. It can be restored from the trash along with its issues Correct answer.
  3. The project can be restored only by Atlassian Support
  4. The project can be restored only if a backup was taken first

Explanation

Deleting a project moves it to the trash, where a site administrator can restore it complete with its issues and configuration. After 30 days the project and its data are permanently removed.

Question 22Project creation, project types, and project-level configuration

Two company-managed projects use different workflow schemes, but both schemes reference the same workflow for the Bug issue type. An administrator edits that workflow to add a new status. What is the effect?

  1. Both projects are affected because they share the same workflow Correct answer.
  2. Only issues created after the change will see the new status
  3. Only the project whose workflow scheme lists the workflow first is affected
  4. Neither project is affected until each workflow scheme is re-saved

Explanation

Workflows are standalone objects that workflow schemes reference, so editing one changes behaviour for every scheme and project that uses it. The new status is therefore available to existing and new issues in both projects at once.

Question 23Project creation, project types, and project-level configuration

Which configuration is available in a company-managed project but not in a team-managed project?

  1. Choosing a project avatar
  2. Adding new members to the project
  3. Renaming the project
  4. Using a shared permission scheme Correct answer.

Explanation

Team-managed projects keep permissions inside the project and configure them through access levels and project administrators. Only company-managed projects can attach a permission scheme that is shared with other projects.

Question 24Project creation, project types, and project-level configuration

An administrator assigns a new workflow scheme to a company-managed project, but the new workflow lacks the status 'In Review' that some existing issues currently have. What happens?

  1. The issues in the missing status are deleted during the migration
  2. The new workflow must be edited to include every status used by existing issues before it can be assigned
  3. The workflow scheme cannot be changed once issues exist
  4. Each affected issue is migrated to a status in the new workflow chosen by the administrator Correct answer.

Explanation

When a workflow scheme change leaves issues in statuses the new workflow does not contain, Jira runs a migration step where the administrator maps each old status to a new one. The workflow therefore does not need to contain every previous status.

Question 25Project creation, project types, and project-level configuration

An administrator wants to remove the Epic issue type from a project that uses an issue type scheme shared with two other projects. What must the administrator consider?

  1. The issue type can be deleted directly from the project's issue types page
  2. The other two projects lose that issue type as well Correct answer.
  3. Removing the issue type from the scheme affects only the current project
  4. The issue type is removed automatically once no issues of that type remain open

Explanation

Issue types become available to a project through its issue type scheme, so removing one affects every project that shares that scheme. Existing issues of the removed type must also be moved to another issue type.

Question 26Project creation, project types, and project-level configuration

A user creates a new team-managed project and selects a template during creation. What does that template determine?

  1. The notification scheme that emails the project's members
  2. The Jira license consumed by the users who join the project
  3. The issue types, fields and workflow the project starts with Correct answer.
  4. The permission scheme shared with other projects on the site

Explanation

A team-managed project is created from a template, and the template defines the initial issue types, the fields shown on its screens and the workflow the project uses. Because a team-managed project's configuration is contained inside the project, that starting configuration does not touch any other project. Access and notifications for such a project are also configured within the project rather than through site-wide schemes.

Question 27Project creation, project types, and project-level configuration

Which pair of project types can a user choose from when creating a project in Jira Cloud?

  1. Classic and next-gen
  2. Shared and private
  3. Company-managed and team-managed Correct answer.
  4. Software and service

Explanation

Jira Cloud offers exactly two project types: company-managed projects, whose configuration is owned by Jira administrators through shared schemes, and team-managed projects, whose configuration is contained in and controlled by the project itself. The choice of type fixes how the project is administered for its entire lifetime.

Question 28Project creation, project types, and project-level configuration

A team wants its existing company-managed project turned into a team-managed project so members can edit the configuration themselves. What is the supported approach in Jira Cloud?

  1. Ask Atlassian Support to convert the project type for the site
  2. Create a team-managed project and move the issues into it Correct answer.
  3. Change the project type on the Project settings > Details page
  4. Disable the shared schemes so the project becomes team-managed

Explanation

A project's type is fixed at creation and Jira Cloud provides no setting that switches an existing project between company-managed and team-managed. The documented path is to create a new project of the required type and move the issues across. The original project can then be archived or deleted once the migration is verified.

Question 29Project creation, project types, and project-level configuration

In a company-managed project, the Default Assignee is set to Project Lead. An issue is created with the Assignee field left empty. What happens?

  1. The issue is assigned to the user who reported it
  2. The issue is assigned to the administrator who set the option
  3. The issue stays unassigned until someone assigns it
  4. The issue is assigned to the project's current lead Correct answer.

Explanation

The Default Assignee setting on a company-managed project decides who receives an issue when no assignee is chosen during creation. With Project Lead selected, Jira resolves the project lead role at that moment, so assignments automatically follow a later change of lead. The alternative value for this setting is Unassigned.

Question 30Project creation, project types, and project-level configuration

A Jira administrator deletes a project category that is currently assigned to five company-managed projects. What is the result?

  1. The five projects are moved into a default category automatically
  2. The projects remain unchanged but no longer belong to a category Correct answer.
  3. The projects are deleted together with the category
  4. The projects are archived until a new category is assigned

Explanation

A project category is purely an organisational grouping used to arrange projects in the project directory and in reports. It carries no permissions, workflow or other configuration, so removing it leaves the projects and their schemes intact. The projects simply have no category until an administrator assigns one again.

Question 31Issue types, schemes, and issue type schemes

Which setting determines the list of issue types that users can select when creating an issue in a company-managed project?

  1. The issue type scheme associated with the project Correct answer.
  2. The field configuration scheme associated with the project
  3. The issue type screen scheme associated with the project
  4. The workflow scheme associated with the project

Explanation

An issue type scheme holds the set of issue types offered to a project, and the project's association with that scheme defines its available types. Screen, workflow and field configuration schemes consume issue types but do not decide which types exist for the project.

Question 32Issue types, schemes, and issue type schemes

How are issue types stored in a Jira Cloud site?

  1. Once per workflow, so each workflow owns its types
  2. Separately inside each project's configuration
  3. Once at the site level and shared with projects through schemes Correct answer.
  4. Per user, based on the user's project role

Explanation

Issue types are site-level objects created once by an administrator and reused everywhere. A project only sees the subset of those types that its issue type scheme contains.

Question 33Issue types, schemes, and issue type schemes

What is the purpose of the Default Issue Type setting on an issue type scheme?

  1. It is preselected when a user creates an issue without choosing a type Correct answer.
  2. It forces every new issue in the project to be created with that issue type
  3. It sets the issue type that Jira automation rules will use
  4. It defines the issue type displayed on the project's roadmap

Explanation

The default issue type is the value pre-filled in the issue type field when a user creates an issue and does not pick one. Users can still change the selection to any other type in the scheme before saving.

Question 34Issue types, schemes, and issue type schemes

An administrator tries to delete a custom issue type and Jira reports that the type is in use. What must the administrator do first?

  1. Archive the projects that contain issues of that type
  2. Migrate the existing issues of that type to a different issue type Correct answer.
  3. Remove the issue type from every issue type scheme
  4. Delete the workflow associated with the issue type

Explanation

Jira cannot delete an issue type while issues still reference it, so the deletion flow requires reassigning those issues to another existing type. Scheme membership is updated as part of that reassignment and is not the blocking factor on its own.

Question 35Issue types, schemes, and issue type schemes

How many issue type schemes can a single company-managed project use at one time?

  1. As many as the project has workflows
  2. One per issue type
  3. Up to five
  4. Exactly one Correct answer.

Explanation

A company-managed project is associated with exactly one issue type scheme, which supplies all of its available types. If no scheme is chosen explicitly, the default issue type scheme applies.

Question 36Issue types, schemes, and issue type schemes

A scheme named Service Scheme is shared by four company-managed projects. The administrator adds a new issue type to it. What is the result?

  1. The projects must be re-indexed before the type is usable
  2. All four projects can create issues of the new type Correct answer.
  3. Only the project that first used the scheme gains the new issue type
  4. The new type appears in the projects only after a Jira restart

Explanation

An issue type scheme is a shared object, so edits take effect immediately for every project associated with it. There is no concept of an owning project for a scheme.

Question 37Issue types, schemes, and issue type schemes

In a company-managed project, which issue type hierarchy levels apply by default?

  1. Epic at -1, standard issue types at 0, sub-tasks at 1
  2. Epic at 1, standard issue types at 0, sub-tasks at -1 Correct answer.
  3. Epic at 0, standard issue types at 1, sub-tasks at 2
  4. Epic at 2, standard issue types at 1, sub-tasks at 0

Explanation

Jira places Epic one level above standard issue types and places sub-tasks one level below them. Administrators can add further levels above Epic or below sub-task.

Question 38Issue types, schemes, and issue type schemes

What must be true for users to create sub-tasks in a company-managed project?

  1. The project must use the default issue type scheme
  2. The sub-task must be the default issue type of the project
  3. A sub-task type must be in the project's issue type scheme Correct answer.
  4. A separate sub-task issue type scheme must be associated with the project

Explanation

Sub-task issue types are ordinary issue types with a sub-task hierarchy level, so they follow the same rule as any other type. A project only offers the types that its issue type scheme includes.

Question 39Issue types, schemes, and issue type schemes

A project that uses Scheme A must move to Scheme B, which does not include the Bug issue type, and the project contains many open bugs. What is the safest administrative action?

  1. Switch the project, since Jira adds missing types to the new scheme
  2. Delete the bugs before switching the project to Scheme B
  3. Rename Scheme A to Scheme B and leave the project on it
  4. Add Bug to Scheme B first, or migrate the bugs to an available type Correct answer.

Explanation

Before a project changes schemes, the new scheme must be able to accommodate the issue types already in use, either by containing them or by having the issues migrated. Renaming a scheme does not change which projects it serves.

Question 40Issue types, schemes, and issue type schemes

An administrator is editing an issue type scheme and wants to change its default issue type. Which type may be selected?

  1. Only the Epic issue type
  2. Any standard issue type in the scheme Correct answer.
  3. Any sub-task issue type in the scheme
  4. Only a type that currently has no open issues

Explanation

The default must be a standard, non-sub-task type that is already a member of the scheme. Sub-task types cannot serve as defaults because they cannot exist without a parent issue.

Question 41Issue types, schemes, and issue type schemes

How is issue type configuration handled in team-managed projects?

  1. Team-managed projects share one site-wide issue type scheme
  2. Team-managed projects cannot use custom issue types
  3. Issue types are managed in each project's own settings, not through a scheme Correct answer.
  4. Team-managed projects require an administrator to assign an issue type scheme

Explanation

Team-managed projects give their own project administrators control over issue types inside project settings. Issue type schemes are a company-managed project concept and are not applied to team-managed projects.

Question 42Issue types, schemes, and issue type schemes

An administrator creates a new issue type named Incident. Which projects can use it right away?

  1. No project until the site is re-indexed
  2. Only projects whose issue type scheme includes the new type Correct answer.
  3. Only projects where an administrator has enabled custom issue types
  4. Every project on the site

Explanation

Creating an issue type adds it to the pool of site-level types but not to any scheme. It becomes selectable in a project only after it is added to that project's issue type scheme.

Question 43Issue types, schemes, and issue type schemes

What does the ordering of issue types within an issue type scheme control?

  1. Which workflow each issue type uses
  2. The hierarchy level that each type is assigned
  3. Which type is used when an issue is moved between projects
  4. The order the types appear in issue type selectors Correct answer.

Explanation

The scheme order is preserved in the interface, so administrators can sequence types so the most used ones appear first. Hierarchy level and workflow are separate properties of the issue type itself.

Question 44Issue types, schemes, and issue type schemes

An administrator wants to delete a custom issue type scheme. Which condition prevents the deletion?

  1. The scheme contains a sub-task issue type
  2. The scheme is associated with at least one project Correct answer.
  3. The scheme was renamed after it was created
  4. The scheme contains more than five issue types

Explanation

Jira blocks deletion of any scheme currently in use, so projects must first be associated with another scheme. The system default issue type scheme is also protected from deletion regardless of its project associations.

Question 45Issue types, schemes, and issue type schemes

How does an issue type screen scheme differ from an issue type scheme?

  1. It determines the default issue type that is preselected when new issues are created
  2. It replaces the issue type scheme entirely in team-managed projects
  3. It maps types to screens, while the issue type scheme decides what a project offers Correct answer.
  4. It controls which issue types are available across the whole site

Explanation

An issue type screen scheme assigns screen configurations to issue types, controlling which fields users see. The issue type scheme is a separate object that governs which types a project can use at all.

Question 46Issue types, schemes, and issue type schemes

A user moves an issue from company-managed project A to project B, whose issue type scheme does not include the issue's current type. What happens during the move?

  1. The user must select a different issue type available in project B Correct answer.
  2. The issue keeps its type but becomes uneditable
  3. The move is blocked with no workaround
  4. Jira adds the missing issue type to project B's scheme automatically

Explanation

The move wizard requires a target issue type drawn from the destination project's scheme. If the original type is unavailable there, the user picks one that is, effectively changing the issue's type.

Question 47Issue types, schemes, and issue type schemes

An administrator adds a new issue type hierarchy level above Epic and assigns issue types to it. Which statement about removing that level later is accurate?

  1. The level can be removed at any time regardless of the issues
  2. Only Atlassian Support can remove an added hierarchy level
  3. Issues at that level must be moved or deleted before removal Correct answer.
  4. Removing the level automatically converts its issues to Epics

Explanation

A hierarchy level that still has issues assigned to it cannot be deleted, because those issues would be orphaned. Administrators must first move the issues to a type at another level or remove them.

Question 48Issue types, schemes, and issue type schemes

Which projects use the scheme labelled as the default issue type scheme?

  1. All projects that were created before this issue type scheme existed
  2. Only projects that were created by a Jira site administrator
  3. Only projects with fewer than 100 issues
  4. Company-managed projects with no other scheme assigned Correct answer.

Explanation

The default scheme acts as the fallback for company-managed projects that have not been given a specific issue type scheme. Creation date, creator and project size play no part in the association.

Question 49Issue types, schemes, and issue type schemes

An issue type is removed from an issue type scheme that several projects use. What happens to existing issues of that type?

  1. They are automatically converted to the scheme's default issue type
  2. They keep their type, but no new issues of that type can be created Correct answer.
  3. They are moved to the Jira trash and can be restored within 30 days
  4. They are deleted along with the scheme entry

Explanation

Removing a type from a scheme only affects what users can select going forward; existing issues retain their type. This is why the change can be made without data loss but also without cleaning up old issues.

Question 50Issue types, schemes, and issue type schemes

An administrator needs to apply one issue type scheme to 40 company-managed projects. Which approach is most efficient?

  1. Re-index the site and select the scheme during re-indexing
  2. Delete the default issue type scheme and recreate it for the 40 projects
  3. Open each project's settings and change the scheme one at a time
  4. Associate several projects at once from the schemes page Correct answer.

Explanation

The issue type schemes administration page lets an administrator select a scheme and add multiple projects to it in a single action. Editing each project individually works but is far slower at scale.