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

ACP-120 practice questions

One question at a time. Build your ACP-120 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 1Jira Cloud administration fundamentals and system settings

Which global permission grants a user access to Jira's administration settings?

  1. Bulk change
  2. Administer Jira Correct answer.
  3. Browse users and groups
  4. Create shared objects

Explanation

Administer Jira is the global permission that lets a user open Jira settings and manage site-wide configuration such as schemes, custom fields and system settings. It is granted through the global permission scheme and applies across the whole site.

Question 2Jira Cloud administration fundamentals and system settings

A team wants some issues inside a single project hidden from most project members while the remaining issues stay visible to everyone with project access. Which configuration achieves this?

  1. A permission scheme
  2. An issue type scheme
  3. An issue security scheme Correct answer.
  4. A notification scheme

Explanation

An issue security scheme defines security levels that can be set on individual issues, restricting visibility to the users, groups or roles named in that level. A user must satisfy both the project permission check and the issue's security level to see it.

Question 3Jira Cloud administration fundamentals and system settings

Which scheme determines the email messages users receive when issues are created, updated or commented on in a project?

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

Explanation

A notification scheme lists notification events and the recipients, such as the assignee, reporter, a group or a project role, who are emailed for each event. It is associated with projects the same way other scheme types are.

Question 4Jira Cloud administration fundamentals and system settings

What determines which projects and issue types a custom field is available for?

  1. The issue type scheme
  2. The field's context Correct answer.
  3. The screen scheme
  4. The field configuration scheme

Explanation

A custom field has one or more configuration contexts, and each context defines the projects and issue types where the field applies, along with default values and options. A field outside its context will not appear in that project at all.

Question 5Jira Cloud administration fundamentals and system settings

Which statement about project roles is correct?

  1. Roles are global objects whose members are assigned per project Correct answer.
  2. Roles replace permission schemes in team-managed projects
  3. Roles are created inside each project and cannot be reused
  4. Roles can only contain individual users, never groups

Explanation

Project roles are defined once at the site level, so the same role, such as Administrators or Developers, can be used by many projects and referenced in permission and notification schemes. Membership in a role is assigned separately inside each project.

Question 6Jira Cloud administration fundamentals and system settings

In a company-managed project, which setting decides who is assigned an issue when the assignee field is left empty at creation?

  1. The notification scheme
  2. The project's default assignee setting Correct answer.
  3. The workflow's create transition
  4. The global permission scheme

Explanation

Each company-managed project has a default assignee setting that can be set to the project lead or to unassigned. When no assignee is chosen during creation, that project-level setting decides the result.

Question 7Jira Cloud administration fundamentals and system settings

Where can a Jira administrator review a record of configuration changes such as permission scheme edits and user management actions?

  1. The project's change history
  2. The system dashboard
  3. The notification scheme
  4. The audit log Correct answer.

Explanation

The audit log records administrative events across the site, including changes to schemes, projects, users and settings, together with the user and time of the change. It is the standard place to review who changed global configuration.

Question 8Jira Cloud administration fundamentals and system settings

A company-managed project has three issue types that must each follow a different workflow. Which configuration object links each issue type to its workflow?

  1. The workflow scheme Correct answer.
  2. The screen scheme
  3. The issue type scheme
  4. The permission scheme

Explanation

A workflow scheme holds the mapping between issue types and workflows, and that scheme is associated with the project. Several issue types can share one workflow, or each can be mapped to its own.

Question 9Jira Cloud administration fundamentals and system settings

Which change can an administrator make to a system field through a field configuration?

  1. Mark the field as required Correct answer.
  2. Change the field's data type
  3. Restrict the field to certain projects
  4. Make the field searchable in JQL

Explanation

A field configuration controls per-field behaviour such as whether a field is required and what description is displayed to users. Field configurations are then mapped to issue types through a field configuration scheme.

Question 10Jira Cloud administration fundamentals and system settings

A custom field appears when users create issues but is missing when they edit existing issues. What is the most likely cause?

  1. The field is missing from the edit screen Correct answer.
  2. The issue type scheme excludes the field
  3. The field is not in the project's context
  4. The user lacks the Bulk change permission

Explanation

Screens are mapped to operations, so a field is only editable if it appears on the screen used for the edit operation. Adding a field to the create screen does not add it to the edit screen.

Question 11Jira Cloud administration fundamentals and system settings

Which global permission must be granted before a user can run a bulk change on a set of issues?

  1. Browse users and groups
  2. Bulk change Correct answer.
  3. Create shared objects
  4. Administer Jira

Explanation

The Bulk change global permission is the site-level switch that allows a user to use the bulk change wizard. The user must still hold the relevant project permissions, such as Edit issues or Transition issues, for the issues being changed.

Question 12Jira Cloud administration fundamentals and system settings

A user needs to share a filter with every logged-in user on the site. Which global permission is required for that sharing scope?

  1. Manage group filter subscriptions
  2. Create shared objects Correct answer.
  3. Browse users and groups
  4. Administer Jira

Explanation

Create shared objects allows a user to share filters and dashboards beyond their own groups, including with all logged-in users. Without it, the user is limited to private sharing and sharing with groups they belong to.

Question 13Jira Cloud administration fundamentals and system settings

Which scheme controls which issue types a company-managed project can use?

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

Explanation

An issue type scheme is an ordered collection of issue types that is associated with one or more projects, and it defines what those projects offer when creating issues. The order also controls how issue types are listed.

Question 14Jira Cloud administration fundamentals and system settings

An administrator wants one project to use a set of priorities different from the rest of the site. Which statement is accurate for Jira Cloud?

  1. Priorities are defined once at the site level and shared by all projects Correct answer.
  2. Priority schemes can be created and associated with individual projects
  3. Priorities can be renamed per project through the issue type scheme
  4. Priorities are controlled by each project's permission scheme

Explanation

In Jira Cloud, priorities are a single site-wide list; the per-project priority schemes that existed in older server versions are not available. Changing or reordering a priority therefore affects every project that uses it.

Question 15Jira Cloud administration fundamentals and system settings

Which statement about sub-tasks is correct?

  1. A sub-task can itself have sub-tasks
  2. Sub-tasks are configured through their own permission scheme
  3. Sub-tasks appear as independent items in the backlog
  4. A sub-task must have a standard issue as its parent Correct answer.

Explanation

Sub-tasks are child issues that must belong to a parent whose issue type is a standard issue type; nesting sub-tasks under sub-tasks is not allowed. They inherit much of their behaviour from the parent project rather than having their own schemes.

Question 16Jira Cloud administration fundamentals and system settings

A user can sign in to the Atlassian site but has no Jira Software product access. What is the outcome?

  1. The user is added to the jira-users group automatically
  2. The user is treated as a project administrator
  3. The user cannot open Jira Software projects Correct answer.
  4. The user can browse all projects in read-only mode

Explanation

Product access is granted per application, so an account that exists on the site still needs Jira Software access to work in Jira Software projects. Without it the user cannot open those projects regardless of any project permissions.

Question 17Jira Cloud administration fundamentals and system settings

Where does a Jira administrator enable time tracking for the whole site?

  1. In the global permission scheme
  2. In each project's issue type scheme
  3. In Jira settings under time tracking Correct answer.
  4. In the workflow scheme of each project

Explanation

Time tracking is a site-wide setting found in Jira settings, where an administrator can enable or disable it and choose the unit options offered to users. Individual projects do not turn time tracking on for themselves.

Question 18Jira Cloud administration fundamentals and system settings

A permission scheme is shared by four company-managed projects. An administrator grants a group the Transition issues permission in that scheme. What is the result?

  1. The group can transition issues only after a workflow condition is added
  2. The group can transition issues in all four projects Correct answer.
  3. The group can transition issues only in the project where the change was saved
  4. The group can transition issues in projects that use the same workflow scheme

Explanation

A permission scheme is a reusable object, so any edit to it applies immediately to every project associated with it. To vary permissions between projects they must use different permission schemes.

Question 19Jira Cloud administration fundamentals and system settings

Which statement about outgoing mail from Jira Cloud is accurate?

  1. Atlassian's mail service handles all outgoing email Correct answer.
  2. Each project selects its own outgoing mail server
  3. Notifications remain disabled until an administrator turns them on
  4. The SMTP server is set in Jira settings

Explanation

Jira Cloud sends notifications through Atlassian's own mail infrastructure, so administrators cannot point the site at a custom SMTP server as they could on a self-hosted instance. Notification content and recipients are still controlled by notification schemes and user preferences.

Question 20Jira Cloud administration fundamentals and system settings

A user is in a group that has Browse projects in the project's permission scheme, but the user is not covered by the issue's security level. What can the user do?

  1. View the issue after switching to a different workflow
  2. Not view the issue at all Correct answer.
  3. View the issue but not comment on it
  4. View the issue only through a shared filter

Explanation

Issue level security adds a second check on top of project permissions, and both must pass. A user who has Browse projects but is outside the issue's security level is denied access to that issue entirely.

Question 21Jira Cloud administration fundamentals and system settings

Two issue types in one company-managed project need different required fields. Which configuration accomplishes this?

  1. Mapping the issue types in a field configuration scheme Correct answer.
  2. Giving each issue type its own permission scheme
  3. Giving each issue type its own screen scheme
  4. Giving each issue type its own workflow scheme

Explanation

A field configuration scheme maps each issue type to a field configuration, and field configurations define which fields are required or optional. This is how two issue types in the same project can enforce different required fields.

Question 22Jira Cloud administration fundamentals and system settings

An administrator tries to delete an issue type that existing issues still use. What must happen first?

  1. The issue type must be removed from all screens
  2. The issue type must be renamed
  3. The issues must be moved to another issue type Correct answer.
  4. The project's workflow must be deleted

Explanation

Jira protects data integrity by refusing to remove an issue type while issues of that type exist. The administrator must first migrate those issues to a replacement issue type, after which the original type can be deleted.

Question 23Jira Cloud administration fundamentals and system settings

Which action can a project administrator perform in a company-managed project?

  1. Create a new global custom field
  2. Change the project's workflow scheme
  3. Edit the project's permission scheme
  4. Add users to a project role Correct answer.

Explanation

Project administrators manage the day-to-day running of their project, which includes adding and removing members of project roles. Changing shared schemes or creating global objects requires the Administer Jira global permission.

Question 24Jira Cloud administration fundamentals and system settings

Which setting controls whether issues can be left without an assignee across the whole site?

  1. The allow unassigned issues option Correct answer.
  2. Each project's default assignee setting
  3. The notification scheme's assignee rule
  4. The Assign issues project permission

Explanation

The allow unassigned issues option in general configuration is a site-wide switch; when it is off, an assignee must always be supplied. The project's default assignee setting then decides which user is used when none is selected.

Question 25User, group, and role management

In Jira Data Center, which setting determines the order in which user repositories are queried during login?

  1. The order of user directories Correct answer.
  2. The order of groups shown in the group browser
  3. The order in which global permissions are listed
  4. The order of projects in the project directory

Explanation

Jira consults the configured user directories from top to bottom as they appear on the User Directories page. The first directory that recognises a user handles authentication and profile updates, so reordering the list is how administrators prioritise one repository over another.

Question 26User, group, and role management

Which global permission must a user have before they can sign in to Jira?

  1. Create Shared Objects
  2. Jira Users Correct answer.
  3. Browse Users and Groups
  4. Jira Administrators

Explanation

The Jira Users global permission is the gate that allows an account to authenticate into the application. Holding project permissions or group membership is irrelevant if this global permission has not been granted.

Question 27User, group, and role management

Which entries can be added as members of a project role?

  1. Only individual Jira users
  2. Only groups synchronised from an LDAP server
  3. Only Jira administrators
  4. A user, a group, or a default member Correct answer.

Explanation

A project role accepts individual users, groups, and default members such as Project Lead or Default Assignee. Groups let an administrator manage many people at once, while default members are resolved automatically for each project.

Question 28User, group, and role management

What is the supported way to give a team of new starters access to Jira Software?

  1. Grant each starter the Jira Users global permission
  2. Add each starter to a group with that access Correct answer.
  3. Assign each starter an issue security level
  4. Add each starter to a project role

Explanation

Application access is assigned to groups (or to individual users), so placing starters in a group that already holds Jira Software access is the standard, maintainable approach. The Jira Users global permission only allows sign-in and does not by itself entitle a user to a product.

Question 29User, group, and role management

Which group is created by default to carry Jira Software application access?

  1. jira-users
  2. jira-servicedesk-users
  3. jira-administrators
  4. jira-software-users Correct answer.

Explanation

Out of the box, Jira creates jira-software-users and grants it the Jira Software application access. Adding a user to that group is the fastest way to entitle them to Jira Software.

Question 30User, group, and role management

A user belongs to three groups. Only one of those groups is granted Edit Issues in the project's permission scheme. What is the result?

  1. The user can edit issues only if the grant is repeated for every group.
  2. The user can edit issues only after an administrator approves it.
  3. The user can edit issues; grants from all groups are combined. Correct answer.
  4. The user cannot edit issues; most of their groups lack the grant.

Explanation

Jira permission checks are additive: every grant matched through any group, role, or direct user entry is combined into a single effective permission set. A single matching grant is therefore sufficient.

Question 31User, group, and role management

A new project is created without selecting a permission scheme. Which scheme applies?

  1. A new scheme is generated automatically for the project.
  2. The scheme marked as the default permission scheme. Correct answer.
  3. No scheme; permissions are inherited from Jira's defaults.
  4. The scheme of the most recently created project.

Explanation

Jira associates whichever permission scheme is flagged as the default with any project that does not specify one during creation. An administrator can change the association afterwards in the project's permissions settings.

Question 32User, group, and role management

An administrator must give exactly one person a permission in a project's permission scheme without affecting anyone else. Which grant type should be used?

  1. Group
  2. Single user Correct answer.
  3. Any logged in user
  4. Project role

Explanation

Permission schemes support a Single user grant that matches one named account only. The other grant types resolve to broader sets of people and would extend the permission beyond the intended individual.

Question 33User, group, and role management

An issue carries the security level Confidential. A user has Browse Projects in the project but is not an actor on that level. What happens?

  1. The user sees the issue because they are its reporter.
  2. The user sees the issue in search results only.
  3. The user cannot see the issue at all. Correct answer.
  4. The user sees the issue but cannot comment on it.

Explanation

Issue-level security adds a further restriction on top of project permissions. A user who does not match any actor on the issue's security level cannot see the issue, in search results or anywhere else.

Question 34User, group, and role management

A leaver's Jira account is deactivated rather than deleted. What is the outcome?

  1. They are removed from every permission scheme.
  2. They cannot log in, but history stays intact. Correct answer.
  3. Their comments and history are deleted.
  4. They are removed from all groups and roles.

Explanation

Deactivation blocks sign-in while retaining the account and its attribution on issues, comments, and work logs. Deleting the user is what removes the account record and frees the username.

Question 35User, group, and role management

A user cannot see colleagues' names in the assignee picker or the user browser. Which global permission is missing?

  1. Administer Jira
  2. Browse Users and Groups Correct answer.
  3. Jira System Administrators
  4. Jira Users

Explanation

The Browse Users and Groups global permission controls whether a user can see other users and groups in selectors and the user browser. Without it, names are hidden even though the user can sign in and work on issues.

Question 36User, group, and role management

An administrator deletes a group that is referenced in several permission schemes. What happens to those grants?

  1. They remain in the schemes but no longer grant anything. Correct answer.
  2. They are reassigned to the jira-users group.
  3. The affected permission schemes are deleted too.
  4. They keep applying to the group's former members.

Explanation

Jira does not clean up permission scheme entries when a group is removed. The grant entry stays in the scheme but no longer resolves to any members, so the permission is effectively revoked for the former group.

Question 37User, group, and role management

A user account originates from a connected LDAP directory. Which actions does Jira allow on that account from the Users page?

  1. Resetting its password only
  2. Deleting the account and resetting its password
  3. Deleting the account only
  4. Neither deleting the account nor resetting its password Correct answer.

Explanation

Accounts held in external directories are read-only inside Jira: existence and credentials are managed in the directory itself. Jira can deactivate such a user, but not delete the account or change its password.

Question 38User, group, and role management

Under the default configuration, which member is added automatically to the Administrators role of a newly created project?

  1. Every member of jira-administrators
  2. The creator of the first issue
  3. The default assignee
  4. The project lead Correct answer.

Explanation

Default role membership resolves to the project lead for the Administrators role and to the default assignee for the developers-style role. This lets the person who owns the project administer it immediately after creation.

Question 39User, group, and role management

An administrator builds an issue security scheme with two levels, but no security levels can be selected on issues in the target project. What should be checked first?

  1. Whether the scheme is associated with the project Correct answer.
  2. Whether the project has a default assignee
  3. Whether Browse Projects is granted to the project role
  4. Whether the users belong to the jira-users group

Explanation

An issue security scheme has no effect until it is selected for the project in the project's issue security settings. Only then do its levels become selectable on issues.

Question 40User, group, and role management

A project must be readable by people who are not logged in. Which entry in the permission scheme provides this?

  1. Project role: Users
  2. Anyone Correct answer.
  3. Application access
  4. Any logged in user

Explanation

The Anyone grant matches every visitor, including anonymous ones, when anonymous access is enabled. Any logged in user and role or application-access grants all require a signed-in account.

Question 41User, group, and role management

Which task can a user who holds only the Administer Projects permission in a project perform?

  1. Edit the project's versions and components. Correct answer.
  2. Back up the Jira instance.
  3. Create and delete user accounts.
  4. Change the project's permission scheme.

Explanation

Administer Projects covers project-level housekeeping such as editing project details, versions, and components. It does not extend to Jira-wide administration, permission schemes, or system tasks.

Question 42User, group, and role management

Which global permission controls whether a user can create shared filters and shared dashboards?

  1. Administer Jira
  2. Jira Users
  3. Create Shared Objects Correct answer.
  4. Browse Users and Groups

Explanation

Create Shared Objects is the global permission that lets a user share filters and dashboards with other users or groups. Without it, the user can still create private objects.

Question 43User, group, and role management

A user can browse a project and holds Assign Issues, but does not appear in the assignee list. Which permission do they most likely lack?

  1. Assignable User Correct answer.
  2. Browse Projects
  3. Jira Users
  4. Resolve Issues

Explanation

The Assignable User permission determines who can be selected in the assignee field, while Assign Issues only controls whether a user may change that field. Both are granted through the project's permission scheme.

Question 44User, group, and role management

Jira must honour a group whose members include another group. What is required for this to work?

  1. The groups must be duplicated in Jira's internal directory.
  2. The permission scheme must name the nested group directly.
  3. The directory storing the groups must support nesting. Correct answer.
  4. The outer group must be added to the jira-users group.

Explanation

Nested group resolution depends on the underlying directory; Jira traverses nesting only when the directory exposes it, such as LDAP or Crowd configured for nested groups. Granting the outer group then reaches the users inside the nested one.

Question 45User, group, and role management

A user who holds the Jira Administrators global permission reports that they cannot view issues in a project. What explains this?

  1. Global administration does not grant project permissions. Correct answer.
  2. Global permissions override project permissions only for system administrators.
  3. The project's permission scheme is corrupted.
  4. The user must also be in the jira-software-users group.

Explanation

Global permissions govern administration features, while access to project content is decided by the project's permission scheme. An administrator must be granted Browse Projects like any other user.

Question 46User, group, and role management

A user is in the Developers project role of Project A but has no role membership in Project B. Project B's permission scheme grants Edit Issues to the Developers role. What can the user do?

  1. Edit issues in Project A only. Correct answer.
  2. Edit issues in both projects, because the role name is the same.
  3. Edit issues in Project B only.
  4. Edit issues in neither project.

Explanation

Role membership is stored per project, so membership in Project A's Developers role says nothing about Project B. The shared role name in the permission scheme links the two, but the members behind each role are independent.

Question 47User, group, and role management

Two projects use the same permission scheme. An administrator adds a group to the Browse Projects grant. What is the effect?

  1. The change applies after the next Jira restart.
  2. Each project must confirm the change first.
  3. Only the project open in the admin session changes.
  4. Both projects grant Browse Projects to the group at once. Correct answer.

Explanation

A permission scheme is a shared object, so edits apply immediately to every project associated with it. To change one project alone, that project needs its own scheme.

Question 48User, group, and role management

A group holds Jira Software application access. An administrator removes that access from the group, and the affected users have no other source of it. What happens?

  1. The users keep access until their next password change.
  2. The users can still log in but see no projects.
  3. The users keep access but lose their project roles.
  4. The users can no longer log in to Jira Software. Correct answer.

Explanation

Application access is the entitlement that authorises sign-in to a product, so removing it from the only group that granted it blocks the affected users. Users who still hold access through another group keep working normally.

Question 49Project configuration and project types

A project administrator wants to add a new status to a project's workflow in Jira Cloud without asking a Jira administrator for help. Which project setup makes this possible?

  1. A team-managed project, whose workflow belongs to that project alone Correct answer.
  2. A business project created from a company-managed template
  3. A company-managed project, whose workflow is defined in a shared workflow scheme
  4. A company-managed project whose workflow scheme is shared with other projects

Explanation

Team-managed projects hold their own simplified configuration, so the workflow is edited inside the project by anyone with project administration rights. Company-managed projects rely on shared schemes that only a Jira administrator can modify.

Question 50Project configuration and project types

Which value is a valid Jira project key?

  1. 1ABC
  2. TEAM1 Correct answer.
  3. ab-cd
  4. PROJ_2

Explanation

A project key must begin with a letter and may contain only letters and numbers, and it is conventionally uppercase. Punctuation such as underscores and hyphens, and leading digits, are not allowed.