• Home
• Atlassian Exams
• ACP-100 - Jira Administrator

ACP-100 Atlassian Practice Test Questions and Exam Dumps

Question No 1:

Which three factors should you consider when deciding between Jira Cloud and Jira Server? (Choose three.)

Answer Choices:

A. The ability to integrate Jira with a cloud-based source repository (e.g. Bitbucket)
B. The amount of time required for system administration
C. The availability of a REST API
D. The commercial apps you would like to use
E. The ability to integrate with an external user directory (e.g. company LDAP directory)
F. The number of workflows you will require

Correct Answers:
B. The amount of time required for system administration
D. The commercial apps you would like to use
E. The ability to integrate with an external user directory (e.g. company LDAP directory)

Explanation:

When deciding between Jira Cloud and Jira Server (Data Center), the following considerations are key:

• B. System Administration Time:
  Jira Cloud is hosted and maintained by Atlassian, reducing the need for system administration. Jira Server requires in-house management, including maintenance, upgrades, and backups.

• D. Commercial Apps Availability:
  Some Marketplace apps are only available (or behave differently) on either Cloud or Server. The availability of apps or specific functionalities may influence your platform choice.

• E. External User Directory Integration:
  Jira Server provides more flexibility to integrate directly with on-premise directories like LDAP or Active Directory, which is crucial for enterprises with strict user management policies.

Why the other options are not correct:

• A. Cloud-based source repository integration:
  Both Cloud and Server can integrate with tools like Bitbucket. This is not a deciding factor exclusive to one.

• C. REST API availability:
  Both versions provide a REST API, although there are some differences. It’s not typically a major factor in deciding between Cloud and Server.

• F. Number of workflows:
  While complex workflows may be easier to manage on Server due to customization, both versions support multiple workflows. This is more about configuration than platform suitability.

Would you like a visual comparison chart between Jira Cloud and Server?

Question No 2:

You want to introduce Jira to your small non-profit organization. Since you are unsure of the optimal deployment option, you have gathered some requirements:

• You need to manage a team of up to 15 employees.

• You need to be able to track a backlog of staff action items.

• You want to easily visualize the progress of ongoing work.
  The solution must require minimal administration since your organization only has a part-time IT volunteer.

What solution is most appropriate for your organization?

A. Jira Service Desk Cloud
B. Jira Software Data Center
C. Jira Service Desk Data Center
D. Jira Core Server

Correct Answer: A

Explanation:

When selecting a Jira deployment option for your small non-profit organization, it’s important to consider the size of the team, the type of work, the ease of administration, and the required features. Let’s analyze each option in the context of your requirements:

A. Jira Service Desk Cloud

• Jira Service Desk Cloud is an ideal solution for small organizations that need to manage work with minimal administration. Cloud solutions are managed by the service provider, meaning you won’t need to worry about server maintenance, updates, or infrastructure management—perfect for an organization with a part-time IT volunteer.

• It provides easy-to-use functionality for tracking backlogs and managing action items, with built-in visualizations like Kanban boards, making it easy to see ongoing work.

• Since it’s a cloud-based solution, it offers flexibility, scalability, and low upfront costs, which is beneficial for small organizations or non-profits.

• Cloud services also provide access to frequent updates, security patches, and integrations with other cloud services without manual intervention.

This option is the most appropriate because it meets your needs for ease of use, low administrative overhead, and a user-friendly interface for tracking tasks and progress.

B. Jira Software Data Center

• Jira Software Data Center is designed for large organizations with higher availability and scalability needs. It requires more administration and IT resources, including handling server setup, scaling, and maintenance. For a small team with minimal IT support, this option is not suitable due to the complexity and management overhead required.

C. Jira Service Desk Data Center

• Jira Service Desk Data Center also targets larger organizations with high availability and performance requirements. Like Jira Software Data Center, it requires more administration and is better suited for organizations with dedicated IT teams. It is not an ideal solution for small, non-technical teams like the one you are managing.

D. Jira Core Server

• Jira Core Server is a self-hosted solution that requires more effort in terms of installation, configuration, and maintenance. For a small non-profit with a part-time IT volunteer, managing this setup could become burdensome. While it provides a robust tool for managing work, the lack of cloud-based convenience and the administration overhead makes it less suitable than Jira Service Desk Cloud.

Given your organization's size, need for minimal administration, and focus on tracking action items and progress, Jira Service Desk Cloud is the best option. It allows you to manage the work of up to 15 employees without the complexity of managing a server, making it the most appropriate solution.

Question No 3:

The marketing team has requested that you embed the trigger tab of an issue collector on multiple internal web pages and customize its size, color, and text. They also want the ability to track which webpage generated the feedback issue. You are not familiar with advanced issue collector configurations. 

Which type of developer should you reach out to for assistance?

A. Groovy
B. JavaScript
C. Velocity
D. Python
E. SQL

Answer: B

Explanation:

To embed and customize the issue collector’s trigger tab on your web pages, as well as to modify its appearance (size, color, text) and track which webpage generates the feedback, you need to utilize JavaScript. JavaScript is a front-end programming language that allows you to dynamically manipulate web content. It can handle tasks such as modifying the appearance of elements and capturing user interactions, such as the webpage that triggered the issue collector.

Why the other options are incorrect:

• A. Groovy – This is mainly used for backend scripting, especially in environments like Jenkins, and is not suited for web page manipulation.

• C. Velocity – This is a server-side templating language often used in Jira and Confluence. It is not designed for direct manipulation of client-side elements on web pages.

• D. Python – While Python is great for backend operations and data processing, it is not typically used for direct front-end web development or UI interactions.

• E. SQL – SQL is used for managing and querying databases, not for customizing or embedding UI elements on web pages.

To meet the marketing team's requirements for embedding, customizing, and tracking the issue collector, you should reach out to a JavaScript developer, who can provide the necessary assistance.

Question No 4:

Your Jira has 25,000 active users across the globe using 100 projects with over a million issues. Another administrator has made a change to a field configuration scheme and you now need to re-index Jira.

What would be the impact of rebuilding the index in the foreground?

A. Issues will take longer to display during the re-index.
B. Database backups cannot be run until the re-indexing is complete.
C. The configuration change will not be applied until re-indexing is complete.
D. Searches using the field may show erroneous results.
E. All users will be locked out of Jira until re-indexing completes.

Correct Answer: E. All users will be locked out of Jira until re-indexing completes.

Explanation:

When you choose to perform a foreground re-index in Jira, the system becomes unavailable to all users for the duration of the process. This is a critical operation because Jira stops accepting any interaction—users cannot view, create, or edit issues until the re-indexing finishes. This ensures data integrity and avoids potential inconsistencies while the search index is being rebuilt.

Here's why the other options are incorrect or misleading:

• A. Issues will take longer to display during the re-index.
  Incorrect. In a foreground re-index, issues won’t display at all because the system is entirely offline to users.

• B. Database backups cannot be run until the re-indexing is complete.
  Not necessarily true. Database backups can often be scheduled or run independently, though it's generally advisable not to make large system changes during backups. However, it's not a specific limitation of re-indexing.

• C. The configuration change will not be applied until re-indexing is complete.
  Partially true but misleading. While the change (like to a field configuration) may not be fully reflected in searches until the re-index is done, this is not a unique impact of foreground re-indexing, and it doesn't imply system-wide lockout like option E does.

• D. Searches using the field may show erroneous results.
  Possible during background re-indexing, not during foreground. In a foreground re-index, searches aren't even possible as the system is offline.

Thus, the most critical impact of performing a foreground re-index is that all users are locked out of Jira until it completes, making E the correct and most significant answer.

Question No 5:

Currently, emails are no longer being sent and the failed notifications can be seen in the Mail Error Queue.What is the likely cause of the failure?

A. Email volume has increased and the Timeout is too low.
B. The SMTP password has expired.
C. The user jira has no valid Jira license.
D. The database and/or server disk is full.
E. The Jira license has expired.

Correct Answer: B. The SMTP password has expired.

Explanation:

When email notifications stop sending and failures are accumulating in the Mail Error Queue in Jira, one of the most common and likely causes is a problem with the SMTP server authentication. Specifically, if the SMTP password has expired or has been changed (for example, in the case of OAuth or app-specific passwords), Jira will be unable to authenticate with the mail server to send outgoing messages.

Let’s review the other options:

• A. Email volume has increased and the Timeout is too low
  While a higher volume might cause occasional timeouts or slow delivery, it wouldn't consistently cause failed emails to stack in the error queue unless there's an underlying SMTP configuration issue.

• C. The user jira has no valid Jira license
  Even if the jira user doesn't have a license, this would not typically block email notifications. Licensing issues affect access to the UI or features, not email transmission directly.

• D. The database and/or server disk is full
  If this were the case, you would see broader application issues, such as Jira not functioning at all or error messages related to database writes, not just email failures.

• E. The Jira license has expired
  Jira would continue to work in a limited state, but email sending is not immediately disabled due to an expired license.

An expired SMTP password or broken SMTP credentials are frequent causes of email failures in Jira. Therefore, option B is the most plausible and technically accurate reason for this issue.

Question No 6:

Jan asked you to create a new Select List custom field called Department for his project MCAS.
You created the field in the morning. In the afternoon, Jan notes that his Jira dashboard is not showing the field correctly. He asks to help him troubleshoot.

Dashboard Summary (from Exhibit):

• Gadget 1: Shows 26 issues in the project by Status

• Gadget 2: Shows 3 issues that have the new Department field set

• Gadget 3: Uses the filter: project = MCAS AND Department is empty — shows "No Data Available"

Why does Jan's third gadget say "No Data Available"?

A. The field is marked Optional in the Field Configuration.
B. Jan does not have the proper Browse permissions.
C. The field context on the Department field was not set to allow empty values.
D. You created the field Department but did not re-index the MCAS project.
E. The JQL query for the filter is not valid.
F. There is issue security on the issues.

Correct Answer: C. The field context on the Department field was not set to allow empty values.

Explanation:

In Jira, custom field behavior (like whether a field appears, can be empty, or is searchable) depends on the field context and configuration. Here’s what likely happened:

• You created the Department field and applied it to the MCAS project.

• It is a Select List field. Select List fields cannot be "empty" if the context is incorrectly configured.

• The gadget with the JQL project = MCAS AND Department is empty expects issues with no value set for Department.

• However, if the field’s context does not include "None" or blank values, Jira won’t treat those fields as empty in search — meaning the query will return no results, even if issues don’t have the field set.

Why the other options are incorrect:

• A. Optional fields still allow empty values in JQL — this setting controls whether the field is required on screens, not in filters.

• B. Jan can see other gadgets and counts, so his permissions are fine.

• D. Re-indexing might fix some display issues, but it wouldn't cause this specific gadget result.

• E. The JQL is syntactically correct and valid.

• F. Issue security would block all gadgets, not just one with a specific filter.

Would you like a brief guide on fixing the field context in Jira to allow empty values?

Question No 7:

You are moving a workflow from your staging Jira instance to production. On importing the workflow, Jira notifies you that the post-functions will not be imported.

Staging Jira is on version 6.4 and production Jira is on version 6.3.Why did this happen?

A. The apps installed on staging are not the same as on production.
B. The production and staging instances are using different versions of Jira.
C. You exported the workflow as XML instead of JWB.
D. Custom post-functions are not included in workflow export.

Correct Answer: A. The apps installed on staging are not the same as on production.

Explanation:

When moving workflows between Jira instances, especially if they contain custom post-functions, Jira will not export/import those post-functions unless the corresponding apps (plugins) are also installed and enabled on the target instance.

• Option A is correct because if the staging instance has apps (like a post-function plugin) that are not installed or enabled on the production instance, Jira cannot import or recreate those post-functions.

• Option B — While version mismatch might cause some compatibility issues, Jira versions 6.3 and 6.4 are fairly close, and version difference alone doesn't result in missing post-functions. It's the plugin availability that matters most here.

• Option C — Jira workflow exports are done via XML; there is no .JWB export format. This is incorrect.

• Option D — While it’s true that custom post-functions may not be included, the reason they’re not imported is because the target system lacks the required plugins, not due to a limitation in the export format itself.

Therefore, the missing apps (or add-ons) on the production instance are the root cause of Jira not importing the post-functions.

Question No 8:

After performing a Jira upgrade, users report significant issues, and you decide to roll back the upgrade. What are two expected outcomes of the rollback? (Choose two.)

A. Emails will automatically be sent to inform users about the rollback.
B. Any new issues created between the upgrade and rollback will be lost.
C. The color scheme will reset to default to indicate the rollback.
D. Jira will revert to the configurations it had before the upgrade.
E. Jira will need to be reconnected to other systems it was integrated with.

Answer: B, D

Explanation:

When a rollback is performed after an upgrade, certain effects are typically expected based on the backup and restoration process:

• B. Any new issues created between the upgrade and rollback will be lost.
  This is true because during a rollback, Jira is restored to the state it was in prior to the upgrade, meaning any data created after that point will not be retained.

• D. Jira will revert to the configurations it had before the upgrade.
  This is also correct. A rollback often involves restoring the system using a backup from before the upgrade, meaning all settings and configurations, such as workflows, schemes, and permissions, will be reverted to their previous state.

The other options do not apply because:

• A is incorrect since Jira does not automatically send emails about rollbacks.

• C is incorrect; the color scheme typically does not change to indicate a rollback.

• E is incorrect because system integrations should remain intact if the rollback is done using a full backup, unless changes were made during the upgrade that affected those connections.

Question No 9:

The Active Directory administrators have just started the process of copying all the users from the old Company B directory to Company A directory. During this process, the group membership is being changed to allow for more fine-grained security control. A large number of migrated users complain that they do not have the correct new group memberships. 

Which configuration change should you perform?

A. Reorder the directories so Company A is before Company B.
B. Enable the Crowd user directory.
C. Reorder the directories so the Jira Internal Directory is listed first.
D. Synchronize the Company A directory.
E. Disable the Company A directory.
F. Disable the Company B directory.

Answer: A

Explanation:

When dealing with multiple user directories in systems like Jira, Confluence, or any Atlassian-based product that integrates with external directory services such as Active Directory, the order in which the directories are listed is critical. Jira checks user identities and group memberships in the order that the directories appear. If a user exists in more than one directory (for example, the same username in both Company A and Company B directories), Jira will use the first match it finds.

In the scenario described, users are being migrated from Company B to Company A, and their group memberships are being modified in the Company A directory to enable more precise security control. If Jira or the integrated system still lists Company B before Company A in the directory order, Jira will authenticate users against Company B, ignoring the updated group memberships in Company A.

This explains why users are complaining about not having the correct group memberships — the system is still referencing outdated information from the old Company B directory. Therefore, the logical step is to reorder the directories so that Company A appears before Company B. This ensures that Jira will check the new directory first, where the updated and correct group memberships reside.

Let’s analyze the incorrect options:

• B. Enable the Crowd user directory: This only applies if Crowd (Atlassian’s centralized identity management system) is being used and is currently disabled. There's no indication that this is the case or that it’s relevant to the current issue.

• C. Reorder the directories so the Jira Internal Directory is listed first: The internal directory is used for administrative accounts or in situations where external directories fail. It's not a solution to the directory priority issue between Company A and Company B.

• D. Synchronize the Company A directory: While synchronization ensures that user and group data is up to date, it does not change the priority or order of directory checks. If Company B is still listed first, synchronization alone won’t fix the problem.

• E. Disable the Company A directory: This would remove access for all migrated users now meant to authenticate through Company A, making the situation worse.

• F. Disable the Company B directory: While this might seem like a potential fix, it’s risky if the migration isn't fully complete or if some users still need access from Company B. Reordering is a safer, non-destructive step during transition.

Hence, reordering the directories so Company A comes before Company B (Option A) is the correct solution. This approach allows the system to authenticate users and apply group memberships from the updated directory, without prematurely cutting off access or disabling necessary directories.

Question No 10:

After a recent upgrade to your Jira system, one of the apps your organization depends on is not working reliably. 

Which two methods can you use to debug and resolve this issue? (Choose two.)

A. Ask the System Administrator for catalina.out logs and inspect for stack traces.
B. Ask the System Administrator to enable the SQL log.
C. Ask the System Administrator to set package com.atlassian to Trace logging level.
D. Ask the System Administrator to add the app to the logger.
E. Ask the System Administrator to set the logging level to FATAL on all package names, Under Logging & Profiling.

Answer: A and D

Explanation:

When dealing with issues after a Jira upgrade—especially when third-party or custom apps begin behaving erratically—debugging methods must focus on identifying what went wrong at both the application and server levels. In this case, gathering logs and increasing logging specificity are two essential strategies.

Option A (Ask the System Administrator for catalina.out logs and inspect for stack traces) is a sound approach. The catalina.out file is a Tomcat log that includes vital server-side logs, including those generated during application errors, failed service calls, and exceptions. Reviewing this log file often reveals Java stack traces and other error messages that can help pinpoint what part of the application or plugin is misbehaving. It’s particularly useful for spotting compatibility issues that arose due to an upgrade, missing dependencies, or misconfigured resources.

Option D (Ask the System Administrator to add the app to the logger) is another appropriate choice. By adding the specific app’s package or namespace to the logger, you can configure Jira’s built-in logging and profiling tools to collect detailed debug information only from the relevant app. This helps narrow down the source of the issue without overwhelming the log files with unrelated data. It allows you to isolate the component's behavior in real-time and track what it's doing (or failing to do) under the new Jira version.

Option B (Ask the System Administrator to enable the SQL log) is not usually the most helpful method in this scenario. SQL logging is more appropriate for tracking database performance or identifying slow or faulty queries. While it can help in specific plugin debugging cases, it's not the primary go-to method when a plugin simply isn't functioning after a Jira upgrade.

Option C (Set package com.atlassian to Trace logging level) is typically discouraged because Trace is an extremely verbose logging level. Applying it to a broad package like com.atlassian can generate excessive log data, possibly degrading system performance or masking the relevant information amid the noise. This setting should be used sparingly and only for narrow, targeted packages.

Option E (Set the logging level to FATAL on all package names) is inappropriate. The FATAL level only captures the most severe errors—those that cause the system to crash or severely malfunction. Using this level would likely suppress useful ERROR, WARN, or DEBUG messages, making it harder to debug the issue rather than easier.

In summary, the most effective actions are to review detailed server logs for stack traces and add the specific app to the logger to capture targeted logs, both of which allow you to investigate what specifically is breaking or misbehaving in the newly upgraded environment. These approaches are grounded in Jira’s standard troubleshooting methodology.