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

ACP-620 practice questions

One question at a time. Build your ACP-620 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 Application Administration, Configuration, and System Settings

In Jira, which permission is required for a user to move issues between projects?

  1. Move Issues Correct answer.
  2. Transition Issues
  3. Browse Projects
  4. Assign Issues

Explanation

Moving an issue to another project requires the Move Issues permission in the source project, along with the ability to create issues in the destination project. Browse Projects only grants visibility, and Transition Issues controls workflow status changes rather than project relocation.

Question 2Jira Application Administration, Configuration, and System Settings

Which setting determines whether new users can sign up for Jira on their own?

  1. Public signup Correct answer.
  2. Captcha on login
  3. Default user group
  4. Application access

Explanation

The public signup option in the user management settings enables self-registration, often combined with a captcha. Application access instead controls which products a created account may use.

Question 3Jira Application Administration, Configuration, and System Settings

What does a Jira workflow scheme do?

  1. It assigns permissions to project roles
  2. It stores custom field configurations
  3. It defines the statuses available globally
  4. It maps issue types to workflows per project Correct answer.

Explanation

A workflow scheme associates each issue type in a project with a specific workflow. Statuses are defined inside workflows themselves, and permission schemes are separate configuration objects.

Question 4Jira Application Administration, Configuration, and System Settings

Which issue security level feature restricts who can view individual issues?

  1. Permission schemes
  2. Issue security schemes Correct answer.
  3. Field configuration schemes
  4. Notification schemes

Explanation

Issue security schemes define security levels that can be applied to issues so only specified users or groups can see them. Permission schemes control actions across a project rather than per-issue visibility.

Question 5Jira Application Administration, Configuration, and System Settings

In Jira, what is the purpose of a field configuration scheme?

  1. It controls who may edit a field
  2. It groups custom fields into screens
  3. It defines the options for a select list
  4. It associates field configurations with issue types Correct answer.

Explanation

A field configuration scheme maps issue types to field configurations, which in turn control field descriptions and required status. Option lists belong to the custom field itself, and screens are grouped by screen schemes.

Question 6Jira Application Administration, Configuration, and System Settings

Which Jira feature lets administrators schedule automatic backups of the instance?

  1. Database replication
  2. Audit log
  3. Mail queue
  4. Export scheduled service Correct answer.

Explanation

The export scheduled service, configured under system services, produces automatic XML backups at defined intervals. The audit log records configuration changes but does not create backups.

Question 7Jira Application Administration, Configuration, and System Settings

What is the effect of setting a custom field as required in a field configuration?

  1. Users must supply a value when editing the issue Correct answer.
  2. The field is locked to administrators
  3. The field becomes searchable in JQL
  4. The field is hidden from all screens

Explanation

Marking a field required in a field configuration forces users to provide a value whenever they edit an issue of the associated issue type. It does not control searchability or hide the field.

Question 8Jira Application Administration, Configuration, and System Settings

Which global permission is needed to access Jira administration settings?

  1. Bulk Change
  2. Manage Watchers
  3. Create Shared Objects
  4. Administer Jira Correct answer.

Explanation

The Administer Jira global permission grants access to global administration functions. The other listed permissions relate to specific user actions such as watching issues or bulk edits.

Question 9Jira Application Administration, Configuration, and System Settings

A project uses a permission scheme where the group jira-developers has the Create Issues permission. A user in that group reports they cannot create issues. Which factor should be checked first?

  1. Whether the issue type has a screen
  2. Whether the project uses a workflow scheme
  3. Whether the user has application access to Jira Correct answer.
  4. Whether the user is in a notification scheme

Explanation

Permissions only apply if the user has application access to the relevant Jira product. A user without application access cannot act even when group membership grants project permissions.

Question 10Jira Application Administration, Configuration, and System Settings

An administrator wants two issue types in the same project to follow different workflows. What is the correct configuration?

  1. Add both workflows to a single screen scheme
  2. Create a separate project for each issue type
  3. Assign each issue type to its workflow in the workflow scheme Correct answer.
  4. Set the workflows as global transitions

Explanation

A workflow scheme maps each issue type to a workflow, so differing workflows per issue type are achieved within one scheme. Splitting projects is unnecessary and global transitions do not assign workflows.

Question 11Jira Application Administration, Configuration, and System Settings

A custom field appears on the edit screen but not on the view screen. What is the most likely cause?

  1. The field configuration marks it optional
  2. The field context excludes the project
  3. The field is missing from the view screen configuration Correct answer.
  4. The field has no searcher configured

Explanation

Screens determine which fields appear during view and edit operations, so a field present on edit but absent from view is missing from the view screen. Searchers affect search, not visibility on screens.

Question 12Jira Application Administration, Configuration, and System Settings

Which approach lets an administrator give a group of users access to a single project without granting global rights?

  1. Add the group to the jira-administrators group
  2. Add the group to a project role used in the permission scheme Correct answer.
  3. Grant the group the Administer Jira global permission
  4. Assign the group as project lead

Explanation

Project roles referenced in a permission scheme grant project-scoped permissions without global rights. Global permissions and administrator group membership grant broader access than intended.

Question 13Jira Application Administration, Configuration, and System Settings

What happens when a status used by a workflow is deleted from the global status list?

  1. The status is removed and transitions are deleted
  2. Issues in that status revert to Open
  3. The workflow is automatically deactivated
  4. Deletion is blocked while the status is in use Correct answer.

Explanation

Jira prevents deleting a status that is referenced by any workflow, protecting workflow integrity. Administrators must first remove the status from workflows before deletion succeeds.

Question 14Jira Application Administration, Configuration, and System Settings

Which configuration controls the order and grouping of fields shown when a user transitions an issue?

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

Explanation

A transition can specify a screen that collects input and displays fields during that transition. Field configuration schemes govern required status and descriptions rather than transition layout.

Question 15Jira Application Administration, Configuration, and System Settings

An administrator needs a custom field available only to two projects. Which feature should be used?

  1. A screen scheme applied to both projects
  2. A global field with no context
  3. Field contexts limited to the selected projects Correct answer.
  4. A separate field configuration per project

Explanation

Field contexts let a custom field have different options and availability scoped to selected projects or issue types. Field configurations and screen schemes do not restrict which projects can use a field.

Question 16Jira Application Administration, Configuration, and System Settings

Which Jira setting must be configured so that outgoing email notifications are delivered?

  1. A default notification scheme
  2. A notification scheme assigned to the project
  3. The mail queue disabled
  4. An outgoing mail server in the mail settings Correct answer.

Explanation

Outgoing notifications require a configured SMTP mail server in the global mail settings. Notification schemes decide who is notified but cannot deliver mail without a working server.

Question 17Jira Application Administration, Configuration, and System Settings

Which global setting defines the maximum size of file attachments users can upload?

  1. The attachment size limit in system settings Correct answer.
  2. The project permission scheme
  3. The issue type scheme
  4. The workflow validator

Explanation

The maximum attachment size is a global system setting applied instance-wide. Permission schemes control who may attach files, not the size allowed.

Question 18Jira Application Administration, Configuration, and System Settings

A user can see a project but cannot log work on its issues. Which permission is most directly relevant?

  1. Log In
  2. Resolve Issues
  3. Browse Projects
  4. Work On Issues Correct answer.

Explanation

The Work On Issues permission governs logging work and tracking time on issues. Browse Projects only grants visibility, and Log In merely allows authentication.

Question 19Jira Application Administration, Configuration, and System Settings

Which scheme determines the issue types available in a project and their order?

  1. Issue type scheme Correct answer.
  2. Field configuration scheme
  3. Permission scheme
  4. Workflow scheme

Explanation

An issue type scheme lists the issue types offered in a project and their display order. The workflow scheme maps those types to workflows but does not define the list itself.

Question 20Jira Application Administration, Configuration, and System Settings

An administrator wants issues created through email to land in a specific project with a preset issue type. Which configuration is required?

  1. A project role for the mail server
  2. A mail handler configured with the target project and issue type Correct answer.
  3. A notification scheme pointing to the project
  4. A workflow validator on issue creation

Explanation

Mail handlers process incoming email and create issues using the project and issue type specified in the handler configuration. Notification schemes only send mail and cannot create issues.

Question 21Jira Application Administration, Configuration, and System Settings

Two projects share a permission scheme, but one project must grant an extra permission to a role. What is the cleanest configuration?

  1. Grant the permission globally
  2. Add the role to the shared scheme
  3. Create a separate permission scheme for that project Correct answer.
  4. Duplicate the project

Explanation

Because permission schemes are shared objects, diverging requirements call for a distinct scheme assigned to the one project. Modifying the shared scheme would affect both projects.

Question 22Jira Application Administration, Configuration, and System Settings

A workflow contains a condition restricting a transition to a project role. A user in that role still cannot see the transition. Which cause is most likely?

  1. The issue type is not on the create screen
  2. The workflow has no validators
  3. The user lacks the Transition Issues permission Correct answer.
  4. The status has no category

Explanation

Conditions and validators are evaluated only after the user passes the base permission check. Without the Transition Issues permission the transition is unavailable regardless of role-based conditions.

Question 23Jira Application Administration, Configuration, and System Settings

An issue security scheme is applied to a project, but some issues show no security level. What explains this?

  1. The project uses a team-managed permission scheme
  2. The field is not on the create screen or was left empty Correct answer.
  3. The issues belong to a subtask type
  4. The security scheme has no default level

Explanation

The security level is set through a field that must be present on the relevant screen and populated. If the field is absent or left blank, the issue has no level and follows the scheme's fallback behavior.

Question 24Jira Application Administration, Configuration, and System Settings

An administrator changes a field configuration to make a field required, but users can still save issues without it. Which explanation is most plausible?

  1. The workflow has a post function
  2. The screen is shared across projects
  3. The issue type uses a different field configuration in the scheme Correct answer.
  4. The field has a searcher configured

Explanation

Field configurations are applied per issue type through the field configuration scheme, so editing one configuration does not affect issue types mapped to another. The required setting only applies where that configuration is used.

Question 25Jira Application Administration, Configuration, and System Settings

A company wants users authenticated against an external directory while keeping local administrator accounts. Which configuration supports this?

  1. An LDAP user directory added alongside the internal directory Correct answer.
  2. Disabling all user directories
  3. A single internal directory with duplicated accounts
  4. Moving administrators to a project role

Explanation

Jira supports multiple user directories, allowing an external LDAP directory to be added while the internal directory continues to hold local accounts. Directory order determines which is queried first.

Question 26Jira Application Administration, Configuration, and System Settings

Which Jira component stores the reusable list of options that a select-type custom field displays?

  1. A custom field option set
  2. A custom field context Correct answer.
  3. A custom field configuration scheme
  4. A global field default

Explanation

When you create a select custom field, Jira creates a configuration context that holds the option list shown to users. Contexts also control which projects and issue types the field applies to, so the option list lives with the context rather than with the field definition itself.

Question 27Jira Application Administration, Configuration, and System Settings

An administrator wants a notification sent only when an issue is assigned, not on every update. Which notification scheme event should be used?

  1. Issue Assigned Correct answer.
  2. Issue Created
  3. Generic Event
  4. Issue Updated

Explanation

Notification schemes map events to recipients, and Jira fires a distinct Issue Assigned event when the assignee field changes. Adding recipients to that event limits mail to assignment changes. The Issue Updated event fires on many modifications and would produce far more mail.

Question 28Jira Application Administration, Configuration, and System Settings

Which permission scheme entry controls whether a user may move an issue from one project to another?

  1. Assign Issues
  2. Administer Projects
  3. Move Issues Correct answer.
  4. Transition Issues

Explanation

Jira exposes a dedicated Move Issues permission that governs relocating an issue to a different project. Transition Issues only covers workflow status changes within the current project, and Assign Issues only covers changing the assignee.

Question 29Jira Application Administration, Configuration, and System Settings

What does the Default Assignee setting in a project's configuration determine?

  1. The lead shown on the project summary page
  2. The assignee applied to new issues when none is chosen Correct answer.
  3. The user who approves workflow transitions
  4. The user who receives all project notifications

Explanation

The default assignee setting supplies an assignee automatically when an issue is created without one. It can be set to the project lead or to unassigned. It does not affect notifications, project leadership, or approvals.

Question 30Jira Application Administration, Configuration, and System Settings

An administrator wants every new issue in a project to start in a status other than the workflow's initial status. Which mechanism accomplishes this?

  1. A field configuration default for the status field
  2. A transition on the Create step leading to the desired status Correct answer.
  3. A workflow post function that sets the status
  4. A status scheme applied to the project

Explanation

The status of a newly created issue is determined by the Create transition's destination step. To start elsewhere, the workflow must route the Create transition to the step representing that status. Status is not a field that can be defaulted, and no status scheme exists.

Question 31Jira Application Administration, Configuration, and System Settings

A project's issues must be visible only to members of a specific group, regardless of other permissions. Which feature enforces this?

  1. A notification scheme that excludes other users
  2. An issue security scheme with a level restricted to that group Correct answer.
  3. A field configuration hiding fields from other users
  4. A permission scheme granting Browse Projects to the group

Explanation

Issue security schemes add a second gate on top of Browse Projects: users must both have the browse permission and match the issue's security level. Setting a level limited to the group hides those issues from everyone else. Hiding fields or notifications does not restrict visibility of the issue itself.

Question 32Jira Application Administration, Configuration, and System Settings

A user reports that a custom field is missing from an issue even though the field is on the screen. Which configuration should be checked first?

  1. The field's searcher configuration
  2. The field context scope for the project and issue type Correct answer.
  3. The field's default value
  4. The field's description text

Explanation

A custom field only appears when a context includes the project and issue type being viewed. If the context is limited to other projects, the field is silently absent even though the screen contains it. Default values, searchers, and descriptions do not affect whether the field renders.

Question 33Jira Application Administration, Configuration, and System Settings

Which Jira feature should be used to record who changed an issue and when, without installing an app?

  1. A comment added by a workflow post function
  2. The issue history tab Correct answer.
  3. The project activity stream
  4. A custom field of type user picker

Explanation

Jira automatically records every field change, comment, and transition in the issue history, including the author and timestamp. This built-in audit trail requires no configuration. The other options either capture only selected data or depend on manual entry.

Question 34Jira Application Administration, Configuration, and System Settings

An administrator wants to reuse one set of workflow statuses and transitions across many projects while still allowing project-specific edits later. Which approach fits best?

  1. Copy the workflow into each project individually
  2. Use a single global workflow for all projects
  3. Create a shared workflow and assign it through a workflow scheme Correct answer.
  4. Rebuild the workflow per issue type

Explanation

A workflow scheme maps issue types to workflows per project, and multiple projects can share the same scheme and workflow. Sharing keeps maintenance centralized while still permitting a project to be moved to a different scheme later if it needs changes. Copying duplicates effort and global workflows remove flexibility.

Question 35Jira Application Administration, Configuration, and System Settings

A user has the Transition Issues permission but cannot see a particular transition button. What is the most likely cause?

  1. The transition has no post functions
  2. The user lacks the Browse Projects permission
  3. The issue type is not on the project's issue type scheme
  4. A workflow condition on that transition is not satisfied Correct answer.

Explanation

Workflow conditions hide transitions from users who do not meet the criteria, even when they hold the Transition Issues permission. The permission grants the ability to transition in general; conditions then filter which specific transitions appear. Post functions and issue type schemes do not hide buttons.

Question 36Jira Application Administration, Configuration, and System Settings

Which setting determines the maximum number of issues returned by a single JQL search in the user interface?

  1. The project's issue type scheme
  2. The JQL search result limit in general configuration Correct answer.
  3. The attachment size limit
  4. The maximum issues per dashboard gadget

Explanation

Jira's general configuration includes a limit on how many issues a JQL search returns to the interface. This protects performance by capping result sets. Attachment limits, gadget settings, and issue type schemes govern unrelated behavior.

Question 37Jira Application Administration, Configuration, and System Settings

An administrator needs users to authenticate through a corporate identity provider while a few local accounts remain for emergencies. Which configuration supports this?

  1. Move all accounts into a single external group
  2. Enable SAML single sign-on and keep local accounts with passwords Correct answer.
  3. Disable all password authentication for every account
  4. Require every user to use an API token instead of a password

Explanation

Jira Cloud supports SAML SSO tied to an identity provider while still permitting designated local accounts to sign in with passwords. This gives centralized authentication for most users with a fallback for emergencies. Disabling all password logins removes the fallback.

Question 38Jira Application Administration, Configuration, and System Settings

A workflow transition must require a value in a custom field before the user can proceed. Which configuration achieves this reliably?

  1. Add a validator to the transition that requires the field Correct answer.
  2. Make the field required in the field configuration
  3. Add a post function that sets the field
  4. Add a condition that checks the field

Explanation

Transition validators block the transition until their criteria are met, so a validator requiring the field prevents submission while it is empty. Conditions only hide or show the transition, and post functions run after the fact. Field configuration requirements apply to screens in general, not specifically to one transition.

Question 39Jira Application Administration, Configuration, and System Settings

Two projects share a workflow, but one project needs an extra status that the other must not have. What is the cleanest configuration?

  1. Give the project its own workflow and map it in its workflow scheme Correct answer.
  2. Add a screen that shows the extra status
  3. Add the status to the shared workflow and hide it with a condition
  4. Create a new global status and delete the old one

Explanation

Workflow schemes let each project map issue types to different workflows, so the project needing the extra status can use a separate workflow. Editing the shared workflow would affect both projects. Conditions hide transitions, not statuses, and screens do not define statuses.

Question 40Jira Application Administration, Configuration, and System Settings

An administrator deletes a group that is referenced in several permission schemes. What is the immediate effect?

  1. The affected projects become private
  2. All users in the group are deleted from Jira
  3. The permission schemes are deleted automatically
  4. Those permission grants stop matching any user Correct answer.

Explanation

Permission scheme entries reference groups by name; when the group no longer exists, the grant matches no one and effectively stops applying. User accounts are separate objects and remain intact. Schemes and projects are not removed automatically.

Question 41Project Configuration and Project Administration

In Jira, which project role determines whether a user can administer a project's configuration, such as editing its workflow or permission scheme, without necessarily being a Jira administrator?

  1. The Service Desk Team project role
  2. The Developers project role
  3. The Users project role
  4. The Administrators project role Correct answer.

Explanation

Project administration is delegated through project roles, and the Administrators role is the standard mechanism for granting a user control over a project's configuration. A Jira administrator can grant this role to people who are not global administrators. The other roles are for ordinary work or service desk participation.

Question 42Project Configuration and Project Administration

A project administrator wants new issues to start in a status other than the default first step of the workflow. What is the correct place to configure the initial status for created issues?

  1. The project's notification scheme, which controls which status is announced
  2. The project's issue type scheme, which lists the statuses available on creation
  3. The workflow's create transition, where the destination step defines the initial status Correct answer.
  4. The project's permission scheme, which filters who may create issues

Explanation

The status an issue has immediately after creation is the destination step of the create transition in the workflow. To change it, you edit the workflow so that the create transition targets the desired step. Schemes such as issue type, notification, and permission do not set the initial status.

Question 43Project Configuration and Project Administration

Which statement accurately describes the relationship between a permission scheme and a project?

  1. A scheme can be shared by many projects, and each project references exactly one permission scheme Correct answer.
  2. A permission scheme is assigned to a user group rather than to a project
  3. A scheme can be shared by many projects, and each project may reference several permission schemes
  4. Each project must have its own unique permission scheme that cannot be shared

Explanation

Permission schemes are reusable: one scheme may be associated with any number of projects, and every project has exactly one permission scheme at a time. Assigning a different scheme changes all permissions for that project at once. Schemes are associated with projects, not with groups.

Question 44Project Configuration and Project Administration

An administrator needs a project where a specific group can edit issues but cannot transition them to a particular restricted status. Which configuration element is the right tool for that restriction?

  1. A project category that hides the status from the group
  2. A workflow condition on the transition into the restricted status Correct answer.
  3. A notification scheme entry for the restricted status
  4. An issue type scheme that excludes the restricted status

Explanation

Restricting who may move an issue into a status is done with a workflow condition (or a validator) on the relevant transition. Conditions evaluate the acting user at transition time and can limit by group, role, or permission. Notification schemes, issue type schemes, and project categories do not gate transitions.

Question 45Project Configuration and Project Administration

What is the primary purpose of a project category in Jira?

  1. To set the default assignee for new issues
  2. To group related projects for organization and reporting in shared views Correct answer.
  3. To define which issue types are available within a project
  4. To determine the permission scheme applied to a project

Explanation

A project category is a label that groups projects, which is useful for filtering project lists and organizing large instances. It does not carry permissions, issue types, or assignee defaults. Those behaviors are controlled by schemes and project settings.

Question 46Project Configuration and Project Administration

A company wants every new project created from a template to automatically include the same set of custom fields on its screens. Which approach best achieves consistent configuration with the least manual effort?

  1. Create shared screen schemes and field configurations, then use a project template that references them Correct answer.
  2. Create a separate custom field for every project to avoid conflicts
  3. Instruct each project administrator to add fields manually after creation
  4. Rely on the default screen because field configurations cannot be shared

Explanation

Shared schemes and field configurations let many projects use one definition, and project templates can bundle those schemes so new projects inherit them. This avoids duplicated fields and manual setup. Field configurations are explicitly designed to be shared across projects.

Question 47Project Configuration and Project Administration

Which Jira feature lets an administrator define a reusable set of issue types that multiple projects can use?

  1. Notification scheme
  2. Workflow scheme
  3. Issue type scheme Correct answer.
  4. Permission scheme

Explanation

An issue type scheme bundles issue types and can be associated with many projects, controlling which types appear. Permission, notification, and workflow schemes govern other aspects of project behavior. Sharing an issue type scheme keeps issue type availability consistent.

Question 48Project Configuration and Project Administration

An administrator assigns a new workflow scheme to a project that already has issues in statuses that do not exist in the new workflows. What must be handled during the migration?

  1. The issues are automatically deleted because their statuses are invalid
  2. The old statuses are retained permanently alongside the new workflow
  3. The permission scheme must be reset before the workflow scheme can change
  4. A migration mapping must associate existing issues with valid statuses in the new workflow Correct answer.

Explanation

When switching workflow schemes, Jira requires a migration step that maps each existing issue to a status valid in the new workflow. Without a valid mapping, the change cannot complete. Issues are not deleted, and the permission scheme is unrelated to this step.

Question 49Project Configuration and Project Administration

Which element of a notification scheme specifies the event that triggers an email?

  1. The project category assignment
  2. The permission scheme entry for the project
  3. The issue type scheme mapping
  4. The event, such as issue created or issue updated Correct answer.

Explanation

A notification scheme pairs events with recipients, so each row names an event and the users, groups, or roles to notify. The permission scheme, issue type scheme, and project category do not define notification triggers. Events are the trigger mechanism for notifications.

Question 50Project Configuration and Project Administration

A project administrator wants only members of a specific project role to be able to delete issues. Which configuration achieves this?

  1. Add the role to the notification scheme for the issue deleted event
  2. Assign the role to the issue type scheme
  3. Grant the Delete Issues permission in the permission scheme to that project role Correct answer.
  4. Add a workflow condition to the closed status

Explanation

Deleting issues is governed by the Delete Issues permission, which is granted in the permission scheme to users, groups, roles, or other grantees. Restricting the grantee to a project role limits deletion to that role's members. The other schemes do not grant action permissions.