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

ACP-100 practice questions

One question at a time. Build your ACP-100 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 1Application and Project Configuration

In Jira, which scheme directly determines the set of issue types available when a user creates an issue in a given project?

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

Explanation

An issue type scheme is the association object that maps a chosen set of issue types to one or more projects. The workflow scheme controls which workflows apply per issue type, and field configuration schemes control field behavior, not issue type availability.

Question 2Application and Project Configuration

A project uses a company-managed workflow. Where is the transition property that restricts a transition to specific users configured?

  1. In the issue type scheme
  2. In the project permission scheme
  3. In the field configuration
  4. In the workflow transition's conditions Correct answer.

Explanation

Transition-level restrictions such as conditions, validators, and post functions are configured on the transition itself inside the workflow editor. Permission schemes decide broad abilities, but a condition on a transition narrows who may execute that specific transition.

Question 3Application and Project Configuration

Which statement best describes the relationship between a workflow and a workflow scheme?

  1. A workflow scheme replaces the need for issue type schemes
  2. A workflow scheme maps projects to permission schemes
  3. A workflow scheme stores the statuses used by all workflows
  4. A workflow scheme maps issue types to workflows for a project Correct answer.

Explanation

A workflow scheme is the binding layer: for each issue type in a project it declares which workflow applies. Multiple projects can share one scheme, and one scheme can reference different workflows per issue type.

Question 4Application and Project Configuration

You need a field to be required only on one screen used during issue creation, while remaining optional elsewhere. What is the correct approach?

  1. Make the field required in the issue type scheme
  2. Set the field as mandatory in the project permission scheme
  3. Mark the field required in the field configuration used by that screen's context Correct answer.
  4. Add a workflow validator to every transition

Explanation

Requiredness is controlled at the field configuration level, and different field configurations can be applied through field configuration schemes per issue type. Screens control visibility and placement, while field configurations control whether a visible field must be filled in.

Question 5Application and Project Configuration

A screen scheme associates screens with which three issue operations?

  1. Create, Edit, and View Correct answer.
  2. View, Comment, and Attach
  3. Edit, Assign, and Resolve
  4. Create, Delete, and Transition

Explanation

A screen scheme maps a default screen plus optional operation-specific screens for create, edit, and view. The view screen is what users see when browsing an issue, while create and edit screens govern data entry.

Question 6Application and Project Configuration

Which configuration object must be associated with a project before users can see custom fields on issues?

  1. A field configuration scheme and screens that include the fields Correct answer.
  2. A notification scheme
  3. A permission scheme
  4. An issue security scheme

Explanation

Custom fields appear only when they are added to the screens used by the project and are present in the applicable field configuration. The field configuration scheme determines which field configuration applies per issue type.

Question 7Application and Project Configuration

What is the purpose of a context in a custom field configuration?

  1. To define the workflow statuses where the field is editable
  2. To define which users may edit the field
  3. To define the screen on which the field appears
  4. To define which projects and issue types use a given set of field options or default Correct answer.

Explanation

Contexts let one custom field present different option sets or defaults to different projects and issue types. A field can have multiple contexts, each scoped to specific projects and issue types.

Question 8Application and Project Configuration

A project's permission scheme grants the Browse Projects permission to a group, but a user in that group still cannot see the project. Which is the most likely cause?

  1. The user lacks the global permission to use Jira or the project is restricted by an issue security scheme Correct answer.
  2. The field configuration hides the Summary field
  3. The project uses a workflow scheme without a default workflow
  4. The project's issue type scheme lacks a default issue type

Explanation

Visibility requires both project-level Browse Projects and the global permission to access Jira, and issue security can further restrict individual issues. A missing default workflow or issue type affects creation, not visibility, and hidden fields do not block project access.

Question 9Application and Project Configuration

Which scheme controls the email notifications sent when an issue is created or updated?

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

Explanation

Notification schemes define which events trigger notifications and to which users, groups, or roles. They are associated with projects and can be shared across multiple projects.

Question 10Application and Project Configuration

What does an issue security scheme do?

  1. It restricts which users can view individual issues based on a security level Correct answer.
  2. It restricts which users can transition issues
  3. It restricts which fields appear on screens
  4. It restricts which issue types can be created

Explanation

Issue security schemes define security levels, and each level lists the users, groups, or roles allowed to see issues assigned that level. The level is set per issue, so visibility can vary within a single project.

Question 11Application and Project Configuration

A team wants a new project to reuse the exact permission configuration of an existing project. What is the recommended action?

  1. Create a new permission scheme and manually replicate every entry
  2. Copy the existing project's issues into the new project
  3. Change the existing project to use a shared default scheme
  4. Associate the new project with the same permission scheme used by the existing project Correct answer.

Explanation

Schemes are designed to be shared, so associating the new project with the existing permission scheme gives identical permissions without duplication. Copying issues is unrelated to configuration, and manually recreating entries risks drift.

Question 12Application and Project Configuration

Which statement about project roles is accurate?

  1. Roles are project-specific and can be granted to users or groups, and are referenced by schemes Correct answer.
  2. Roles are global and apply to every project automatically
  3. Roles can only contain individual users, never groups
  4. Roles replace permission schemes entirely

Explanation

Project roles are defined per project and can include users and groups, and permission or notification schemes can reference roles. This makes roles a flexible way to grant access without editing schemes for each person.

Question 13Application and Project Configuration

You want a project to use a distinct set of statuses and transitions for its Bug issue type while other issue types keep the default workflow. What must you configure?

  1. A workflow scheme that maps Bug to a separate workflow and other issue types to the default Correct answer.
  2. A new permission scheme for Bug issues
  3. A field configuration scheme with a Bug-specific context
  4. A new issue type scheme containing only Bug

Explanation

Per-issue-type workflow differences are expressed in the workflow scheme, which can assign a different workflow to Bug and keep a default for the rest. Issue type schemes, permission schemes, and field configurations do not control transitions.

Question 14Application and Project Configuration

Which of the following is a valid reason to create a new field configuration rather than editing an existing one?

  1. You want to change the field's type from text to number
  2. Different projects need different requiredness for the same field Correct answer.
  3. You want to rename the field globally
  4. You want to delete the field from all screens

Explanation

Field configurations let the same field behave differently across projects, such as being required in one and optional in another. Renaming a field, changing its type, and deleting it are field-level operations that affect all configurations.

Question 15Application and Project Configuration

In a company-managed project, what does the default assignee setting in the project's configuration control?

  1. The user who receives all notifications
  2. The user who owns the permission scheme
  3. The assignee applied to new issues when no one is specified Correct answer.
  4. The user who approves workflow transitions

Explanation

The default assignee determines who is assigned to newly created issues when the assignee field is left empty. It can be set to the project lead or to unassigned, depending on project settings.

Question 16Application and Project Configuration

A workflow transition has a validator that requires a field to be set. A user reports the transition fails without an error message on screen. What is the most likely explanation?

  1. The notification scheme suppresses the error
  2. The issue type scheme blocks the transition
  3. The validator is disabled by the permission scheme
  4. The field is not present on the transition screen, so the validator cannot be satisfied Correct answer.

Explanation

Validators evaluate fields submitted through the transition screen, so a required field missing from that screen cannot be provided. Adding the field to the transition screen lets users supply the value and see validation feedback.

Question 17Application and Project Configuration

Which object determines the order and grouping of statuses shown on a board column configuration?

  1. The board's column mapping to workflow statuses Correct answer.
  2. The project's field configuration scheme
  3. The project's issue type scheme
  4. The project's notification scheme

Explanation

Board columns are mapped to one or more workflow statuses, which determines how issues appear in each column. The mapping is part of the board configuration rather than the scheme set.

Question 18Application and Project Configuration

What happens when you delete an issue type that is still referenced by an issue type scheme?

  1. The issue type remains but can no longer be used in workflows
  2. The issue type is deleted and existing issues are converted to the default type
  3. Jira prevents deletion until the issue type is removed from all schemes Correct answer.
  4. The issue type is archived and hidden from all projects

Explanation

Jira blocks deletion of an issue type while it is associated with any issue type scheme, forcing you to clean up associations first. This protects existing issues from becoming orphaned.

Question 19Application and Project Configuration

Which configuration is required for a user to log work on an issue?

  1. The Administer Jira global permission
  2. The Work On Issues permission and the time tracking field being available on the relevant screens Correct answer.
  3. The issue security level being set to None
  4. The Browse Projects permission alone

Explanation

Logging work requires the Work On Issues project permission and time tracking fields being present on the screens used for the operation. Browse Projects only allows viewing, and global administration is unrelated.

Question 20Application and Project Configuration

A project must hide a sensitive custom field from most users but show it to a small group. Which combination achieves this?

  1. Add the field to the default screen and rely on the notification scheme
  2. Place the field on a screen used only by that group and restrict screen access through permissions Correct answer.
  3. Add the field to the issue type scheme
  4. Set the field as optional in the field configuration

Explanation

Field visibility follows screens, so a dedicated screen containing the field limits who sees it when combined with permissions controlling access. Field configurations and issue type schemes do not hide fields from specific users.

Question 21Application and Project Configuration

Which statement about sharing a field configuration scheme across projects is correct?

  1. Shared field configurations cannot be edited after association
  2. Changes to a shared field configuration affect all projects using that scheme Correct answer.
  3. Each project receives an independent copy of the field configuration
  4. Sharing is only possible for system fields, not custom fields

Explanation

Schemes are references, not copies, so editing a shared field configuration changes behavior for every project that uses it. This is why separate configurations are created when projects need different behavior.

Question 22Application and Project Configuration

What is the effect of setting a project's default issue type?

  1. It assigns the issue to the project lead
  2. It preselects that issue type on the create issue screen Correct answer.
  3. It forces every new issue to use that type
  4. It removes other issue types from the project

Explanation

The default issue type is preselected when a user opens the create issue dialog, but users can still choose other available types. It does not restrict the issue type list or affect assignment.

Question 23Application and Project Configuration

Which of the following best explains why a user can edit an issue even though the Edit Issues permission is not granted to them directly?

  1. They are listed as a watcher on the issue
  2. They have the Browse Projects permission
  3. They belong to a group or role that is granted Edit Issues in the permission scheme Correct answer.
  4. The issue's security level is set to a public level

Explanation

Permissions are granted to users, groups, roles, or lead, so membership in a granted group or role confers the ability. Watching an issue and browsing it do not grant edit rights.

Question 24Application and Project Configuration

What is the primary function of a field configuration scheme?

  1. To associate workflows with issue types
  2. To associate notification events with recipients
  3. To associate field configurations with issue types within projects Correct answer.
  4. To associate screens with issue operations

Explanation

A field configuration scheme maps issue types to field configurations, allowing different requiredness and rendering per issue type. Screens, workflows, and notifications are handled by their own scheme types.

Question 25Application and Project Configuration

A workflow post function is configured to set a field value on transition. The value does not appear on the issue afterward. Which is the most likely cause?

  1. The permission scheme denies Browse Projects
  2. The notification scheme is disabled
  3. The post function is ordered after the reindex or the field is not editable in the field configuration Correct answer.
  4. The issue type scheme lacks the field

Explanation

Post functions run in sequence, and ordering matters; a field update placed after a reindex step may not be reflected, and a field configuration that hides or locks the field can also interfere. Notification and issue type schemes do not affect stored field values.

Question 26Application and Project Configuration

A project administrator needs a new company-managed project to start with the same issue type set and workflow mapping as an existing project. Which approach follows recommended practice?

  1. Create a new issue type scheme and workflow scheme that copy the existing project's selections, then associate them with the new project
  2. Reuse the existing project's schemes by associating the same schemes with the new project Correct answer.
  3. Edit the existing project's schemes directly and add the new project to them
  4. Delete the existing project's schemes after recording their settings, then rebuild them for the new project

Explanation

Schemes are shared configuration objects, so several projects can be associated with the same issue type scheme and workflow scheme. Sharing avoids duplicated maintenance and keeps behavior consistent across projects. Copying or editing existing schemes is unnecessary when the goal is identical configuration.

Question 27Application and Project Configuration

Which configuration object determines which custom fields are available on issues in a company-managed project?

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

Explanation

A field configuration scheme maps issue types to field configurations, and those configurations decide which fields appear and whether they are required. Associating the scheme with a project is what makes the fields visible there. Permission and notification schemes govern access and messaging, not field availability.

Question 28Application and Project Configuration

A project uses a workflow where the "In Review" status must be reachable only by members of a specific project role. Which workflow element enforces this?

  1. A property on the status itself
  2. A validator on the transition leading into the status
  3. A condition on the transition leading into the status Correct answer.
  4. A post function on the transition leading into the status

Explanation

Conditions restrict who may execute a transition, so a role-based condition prevents unauthorized users from moving an issue into the status. Validators check data entered during the transition rather than the actor's identity. Post functions run side effects after the transition succeeds.

Question 29Application and Project Configuration

A team wants every new issue of type Bug in a project to be created with priority set to High unless the reporter chooses otherwise. Which configuration achieves this?

  1. A post function that sets priority on the create transition
  2. A default value configured for the priority field in the field configuration Correct answer.
  3. A field configuration that marks priority as required
  4. A workflow validator that rejects issues without a priority

Explanation

Field configurations can define a default value that pre-populates a field on the create screen, while still allowing the reporter to change it. Requiring the field only forces a choice and does not preselect High. A post function would overwrite the reporter's choice after submission.

Question 30Application and Project Configuration

Which statement describes the relationship between an issue type scheme and a workflow scheme in a company-managed project?

  1. The workflow scheme must contain exactly the same issue types as the issue type scheme
  2. The issue type scheme assigns issue types to each workflow defined in the workflow scheme
  3. The two schemes are independent and cannot reference the same issue types
  4. The workflow scheme assigns a workflow to each issue type offered by the issue type scheme Correct answer.

Explanation

The issue type scheme decides which issue types a project offers, and the workflow scheme maps each of those issue types to a workflow. The two schemes therefore work together, and the workflow scheme must cover the issue types in use. They are separate objects that reference issue types rather than containing each other.

Question 31Application and Project Configuration

A project manager wants to change the name shown for a status on one project's board without affecting other projects. Which configuration should be changed?

  1. The status name in the global status settings
  2. The issue type name in the issue type scheme
  3. The workflow name in the workflow scheme
  4. The column name in the board configuration Correct answer.

Explanation

Board columns can be given display names that apply to that board only, leaving the underlying status unchanged elsewhere. Renaming a global status affects every project and board that uses it. Workflow and issue type names are unrelated to board column labels.

Question 32Application and Project Configuration

A project has a permission scheme granting the Assign Issues permission only to the group "Developers". A user in that group reports they cannot assign an issue. Which additional factor most likely explains this?

  1. The user lacks the Browse Projects permission
  2. The user's issue type scheme does not include the issue type
  3. The issue security level excludes the user from the issue Correct answer.
  4. The project's notification scheme omits the user

Explanation

Issue security levels can restrict visibility of individual issues even when project permissions are granted. If the user cannot see the issue, they cannot act on it regardless of the Assign Issues permission. Permission checks are evaluated together with issue-level security.

Question 33Application and Project Configuration

Which configuration object controls the order in which statuses appear when a user views the workflow on an issue?

  1. The board's column order
  2. The issue type scheme ordering
  3. The workflow's transition order
  4. The status category of each status Correct answer.

Explanation

Each status belongs to a status category such as To Do, In Progress, or Done, and the category grouping drives how statuses are organized in views. Transition order affects available paths, not display grouping. Board column order applies only to boards, not to the issue view.

Question 34Application and Project Configuration

An administrator needs a custom field to be mandatory on the Create screen for Bugs but optional for Tasks within the same project. Which configuration is required?

  1. A single field configuration with the field marked optional
  2. A permission scheme that hides the field from Task reporters
  3. Two field configurations mapped to the two issue types through the field configuration scheme Correct answer.
  4. A workflow validator applied to the Bug workflow only

Explanation

Required-ness is set per field configuration, and a field configuration scheme maps different issue types to different configurations. Creating separate configurations for Bugs and Tasks lets the same field be required for one and optional for the other. A single configuration cannot express both behaviors.

Question 35Application and Project Configuration

What is the effect of associating a screen scheme with an issue operation such as Create?

  1. It determines which fields appear when that operation is performed Correct answer.
  2. It determines which users may perform that operation
  3. It determines which notifications are sent for that operation
  4. It determines which workflow is used for that operation

Explanation

A screen scheme maps operations to screens, and each screen defines the fields presented during that operation. Permissions decide who may act, while notifications and workflows are governed by other schemes. Screens therefore shape data entry, not authorization.

Question 36Application and Project Configuration

A project needs a custom field visible only to a small support group while remaining hidden from all other users. Which combination is appropriate?

  1. Add the field to the default screen and rely on the permission scheme to hide it
  2. Add the field to the issue type scheme used by the project
  3. Mark the field as required in the field configuration used by the project
  4. Place the field on a screen used only by a workflow transition restricted to the support group Correct answer.

Explanation

Screens control where fields appear, and a transition condition can limit who may use that transition, effectively limiting field visibility. Permission schemes operate on actions rather than individual fields. Field configuration settings control required-ness and description, not user-specific visibility.

Question 37Application and Project Configuration

Which statement about a permission scheme is accurate?

  1. It can be associated with only one project at a time
  2. It applies to all projects in the instance by default
  3. It is stored inside the project and cannot be reused
  4. It can be shared by multiple projects and edited in one place Correct answer.

Explanation

Permission schemes are standalone objects that can be associated with many projects, so a single edit propagates to every associated project. This shared model is why changes should be reviewed carefully. They are not embedded in a single project, and no scheme applies globally unless explicitly associated.

Question 38Application and Project Configuration

An administrator changes a shared workflow to add a new transition. Which projects are affected?

  1. Every project whose workflow scheme uses that workflow Correct answer.
  2. Only the project where the change was initiated
  3. Only projects that share the same issue type scheme
  4. No projects until each project is reindexed

Explanation

Workflows are shared objects referenced through workflow schemes, so editing a workflow affects every project whose scheme points to it. There is no per-project copy unless a separate workflow was created. Reindexing refreshes search data but does not determine which projects receive the change.

Question 39Application and Project Configuration

A project requires that only users in the "Approvers" role may execute a specific transition, and that the transition records who approved the issue. Which pair of workflow elements should be used?

  1. A validator requiring a field, and a condition restricting the transition
  2. A post function restricting the transition, and a validator recording the approver
  3. A condition restricting the transition to the role, and a post function that updates a field Correct answer.
  4. A screen scheme for the role, and a notification scheme for the approver

Explanation

Conditions gate who may run a transition, while post functions can update fields as part of the transition to record the approver. Validators only check input and cannot restrict the actor. Screens and notification schemes do not control transition execution.

Question 40Application and Project Configuration

Which object must be associated with a project before users can select a custom issue type on that project?

  1. A permission scheme that includes the issue type
  2. An issue type scheme that includes the issue type Correct answer.
  3. A notification scheme that includes the issue type
  4. A field configuration scheme that includes the issue type

Explanation

Issue types become selectable in a project only when an issue type scheme containing them is associated with that project. Field configuration, notification, and permission schemes do not manage the list of available issue types. This is why new issue types often require updating the scheme.

Question 41User Management, Groups, and Permissions

In Jira, which permission must a user have to be able to see a project and its issues at all?

  1. Transition Issues
  2. View Issues
  3. Browse Projects Correct answer.
  4. Access Jira

Explanation

Browse Projects is the gateway permission for a project. Without it, a user cannot view the project or any of its issues, regardless of other project permissions granted to them.

Question 42User Management, Groups, and Permissions

A Jira administrator wants to grant a permission to a single named user without creating a group for that person. Which permission scheme grant type should be used?

  1. Project Role
  2. Application access
  3. Group
  4. Single User Correct answer.

Explanation

A permission scheme can grant a permission to a single user directly, which is useful for one-off exceptions. Group and project role grants are used when the access should be managed collectively.

Question 43User Management, Groups, and Permissions

Which statement best describes a Jira group?

  1. A set of issues linked by a common label
  2. A set of projects that share the same workflow
  3. A set of users that can be granted permissions and used for sharing and notifications Correct answer.
  4. A set of permission schemes applied to one project

Explanation

Groups are collections of user accounts managed at the global level. They are the primary way administrators assign global permissions, project permissions, and sharing rights in bulk.

Question 44User Management, Groups, and Permissions

Which global permission is required for a user to log in to Jira at all?

  1. Create Projects
  2. Jira Users Correct answer.
  3. Administer Jira
  4. Browse Users

Explanation

The Jira Users global permission, usually granted through an application access group, allows a user to use the Jira application. Without it the account cannot log in to Jira.

Question 45User Management, Groups, and Permissions

A project administrator needs to give the QA team permission to edit issues in one project only. What is the most appropriate approach?

  1. Create a project role for QA and grant Edit Issues to that role in the project's permission scheme Correct answer.
  2. Give each QA member the Administer Jira global permission
  3. Add the QA team to the Jira Administrators global permission
  4. Grant Edit Issues to the jira-users group in the permission scheme

Explanation

Project roles are designed to grant project-specific access to a defined set of users. Assigning the QA team to a role and granting Edit Issues to that role keeps the permission scoped to the project.

Question 46User Management, Groups, and Permissions

In a permission scheme, a permission is granted to 'Project Role: Developers'. Who receives this permission?

  1. All users who created an issue in the project
  2. All users who are assigned the Developers role in that project Correct answer.
  3. All users with the Developers application access group
  4. All members of any group named Developers

Explanation

A project role grant applies to users who hold that role in the specific project. Role membership is managed per project, so the grant is scoped accordingly.

Question 47User Management, Groups, and Permissions

A user can see issues in a project but cannot comment on them. Which permission is most likely missing?

  1. Resolve Issues
  2. Create Issues
  3. Add Comments Correct answer.
  4. Browse Projects

Explanation

Commenting on issues requires the Add Comments permission in the project's permission scheme. Browse Projects only allows viewing, and the other permissions govern different actions.

Question 48User Management, Groups, and Permissions

What is the purpose of a permission scheme in Jira?

  1. To define the statuses and transitions of an issue type
  2. To define how issues are displayed on a board
  3. To define which users or groups receive which permissions for a project Correct answer.
  4. To define which notifications are sent on events

Explanation

A permission scheme is a reusable collection of permission grants. It maps each permission to users, groups, roles, or other assignees, and is associated with one or more projects.

Question 49User Management, Groups, and Permissions

A company wants every new employee to automatically receive access to a standard set of projects. Which approach best supports this?

  1. Grant Single User permissions to each new employee in every project
  2. Add each new employee to a group that is granted permissions in the relevant permission schemes Correct answer.
  3. Assign each new employee the Administer Projects global permission
  4. Add each new employee to the jira-administrators group

Explanation

Group-based grants are the scalable way to give a population of users consistent access. Adding a user to the group automatically confers all permissions granted to that group.

Question 50User Management, Groups, and Permissions

Which permission allows a user to move an issue from 'In Progress' to 'Done'?

  1. Transition Issues Correct answer.
  2. Schedule Issues
  3. Edit Issues
  4. Link Issues

Explanation

Transition Issues controls whether a user can execute workflow transitions. Moving an issue between statuses is a transition, so this permission is required.