Atlassian ACP-100 Exam Dumps & Practice Test Questions

Question 1:

You are the Jira administrator for your company. Several project managers have requested the ability to customize the issue workflow to better fit their team’s process, including adding new statuses and transitions. However, you want to ensure that workflow changes do not disrupt other projects using the same workflow. 

What is the best approach to allow project-specific workflow customization without affecting other projects?

A. Edit the existing shared workflow directly and notify all project managers about the changes.
B. Copy the existing workflow, customize the copy for the specific project, and associate the project with the new workflow.
C. Use a global workflow scheme to apply changes to all projects simultaneously.
D. Disable workflows for those projects and let teams manage issues without workflows.

Correct Answer: B

Explanation:

In Jira, workflows define the lifecycle and statuses of issues within a project. Workflows can be shared across multiple projects to maintain consistency and reduce administrative overhead. However, when different teams require workflow customizations that are unique to their processes, modifying a shared workflow directly (Option A) risks disrupting all projects using that workflow — often causing confusion, unintended consequences, or process breakdowns elsewhere.

The best practice in this situation is to copy the existing workflow and make the necessary adjustments to the copy (Option B). By creating a new workflow derived from the original, you isolate custom changes so they only apply to the intended project(s). Then, by associating this customized workflow with the specific project through a workflow scheme, the changes impact only that project’s issue lifecycle. This approach preserves the integrity and stability of other projects using the original shared workflow.

Option C, applying changes globally, contradicts the requirement to avoid affecting other projects. Option D, disabling workflows, is not practical since workflows are essential for process enforcement and reporting.

Creating and managing multiple workflows is common for Jira administrators managing diverse teams. Workflow schemes allow flexible assignment of workflows to projects. Careful versioning and naming conventions help keep track of workflow copies and modifications.

In summary, the recommended approach to provide project-specific workflow customization without collateral impact is to duplicate the shared workflow, tailor it as needed, and then assign it to the project—ensuring targeted flexibility with minimal risk.

Question 2:

You are introducing Jira to a small non-profit with up to 15 employees. You need to manage task backlogs, visualize ongoing work, and require minimal IT administration.

Which Jira deployment option is best suited 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:

Choosing the appropriate Jira deployment for a small non-profit organization involves evaluating team size, administrative capacity, and functional requirements. Since your team consists of about 15 employees, and your organization has limited IT support—specifically only a part-time volunteer—the solution must be easy to manage, scalable, and user-friendly.

Jira Service Desk Cloud (A) stands out as the best option because it is a fully hosted solution managed by Atlassian. This means all server maintenance, upgrades, and security patches are handled externally, dramatically reducing the burden on your volunteer IT resource. It offers intuitive tools for backlog management and visualization, including Kanban boards and customizable dashboards, enabling your team to track and visualize progress efficiently.

Additionally, Jira Service Desk Cloud is cost-effective for small teams, provides flexible scalability as your organization grows, and ensures you always have access to the latest features and integrations without manual intervention. Its cloud-based nature also enables easy remote access and collaboration, which can be important for non-profits with distributed teams.

On the other hand, Jira Software Data Center (B) and Jira Service Desk Data Center (C) are designed for larger organizations requiring high availability, performance, and robust IT infrastructure. These options demand more complex setup, ongoing administration, and dedicated IT staff, making them impractical for your scenario.

Jira Core Server (D) requires self-hosting, which involves installing and maintaining your own infrastructure. This option demands significant administrative effort, regular updates, and backups, posing a challenge given your limited IT support.

Therefore, considering your organization's size, need for simple administration, and task-tracking needs, Jira Service Desk Cloud is the most appropriate and practical choice.

Question 3:

The marketing department wants you to embed an issue collector's trigger tab on several internal web pages. They also require customization of its size, color, and text, along with the ability to track which page submitted feedback. Since you are unfamiliar with complex issue collector configurations, 

which type of developer should you consult for help?

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

Correct Answer: B

Explanation:

To successfully embed and customize the issue collector trigger tab on multiple web pages while also tracking the source of feedback, you need a developer skilled in JavaScript. JavaScript is the primary scripting language used on the client side of web applications. It allows dynamic interaction with the webpage content, such as modifying elements' appearance—like size, color, and text—without requiring a full page reload.

Additionally, JavaScript enables event handling, which means it can capture user interactions, such as identifying the exact webpage where the feedback was generated. This capability makes JavaScript the ideal choice to meet the marketing team’s requirements for customization and tracking in real time on the client side.

The other options are less appropriate because they serve different purposes:

• Groovy is primarily a server-side scripting language often used for automation in tools like Jenkins or Jira backend scripts, not for front-end web customization.

• Velocity is a server-side templating language used in Jira and Confluence to render pages dynamically on the server, but it does not manipulate web page behavior after the page loads.

• Python excels in backend development, data processing, and automation but is rarely used for client-side web page manipulation or interaction.

• SQL is designed for database querying and management and has no role in modifying or embedding elements within web pages.

Therefore, consulting a JavaScript developer is the most appropriate approach to achieve embedding, styling, and tracking functionality for the issue collector on the marketing team’s web pages.

Question 4:

Your Jira instance supports 25,000 active users worldwide, spanning 100 projects and over a million issues. After another admin changes a field configuration scheme, you need to re-index Jira. 

What happens when you perform a foreground re-index?

A. Issues take longer to display during re-indexing.
B. Database backups cannot be run until re-indexing finishes.
C. Configuration changes are not applied until the re-index completes.
D. Searches on the updated field may return incorrect results.
E. All Jira users are locked out until re-indexing completes.

Correct Answer: E

Explanation:

Performing a foreground re-index in Jira is a process where the entire Jira application is taken offline for the duration of the indexing operation. This means all users are effectively locked out of the system until the re-index completes. The system stops accepting any new requests, including viewing, creating, or editing issues. This lockout is necessary to maintain data consistency and integrity while rebuilding the search index, especially after configuration changes like modifications to a field configuration scheme.

Foreground re-indexing is typically used for significant changes requiring immediate re-indexing to reflect updates properly. Because Jira is offline during this operation, users experience a complete interruption of service.

The other options do not fully or correctly describe the impact:

• Option A suggests that issues just take longer to display, but in reality, users cannot access Jira at all during the process.

• Option B claims database backups cannot run during re-indexing, but backups often operate independently of indexing and can still be scheduled or executed. This is not a strict limitation.

• Option C is partly true in that configuration changes won’t be fully applied until re-indexing finishes; however, this is a normal part of the process and does not describe the system lockout.

• Option D suggests searches may return wrong results, but during foreground re-indexing, searches are not possible at all since Jira is offline. Search issues may occur with background re-indexing, not foreground.

In summary, the most critical consequence of a foreground re-index in Jira is the complete lockout of all users until the re-indexing process is finished, making E the correct answer.

Question 5:

Emails are no longer being sent, and failed messages are piling up in the Mail Error Queue. What is the most probable cause of this failure?

A. The volume of emails has increased, and the Timeout setting is too short.
B. The SMTP password has expired.
C. The Jira user account lacks a valid license.
D. The database or server disk space is full.
E. The Jira software license has expired.

Correct Answer: B

Explanation:

When Jira stops sending email notifications and you observe failures accumulating in the Mail Error Queue, the most frequent and likely cause is an authentication failure between Jira and the SMTP server. Typically, this happens when the SMTP password used by Jira has expired or changed, causing Jira to fail to authenticate with the mail server and preventing email dispatch.

SMTP (Simple Mail Transfer Protocol) authentication credentials are crucial for connecting to the email server securely and sending messages. If the password expires (common in enterprise environments with security policies enforcing password rotation) or is updated without reflecting the change in Jira's mail configuration, the connection breaks down, and emails fail to send.

Analyzing the other options:

• A (Email volume increase and timeout): While a surge in email volume could cause delays or sporadic timeouts, it would not cause a consistent backlog of failed emails unless the SMTP connection is outright failing due to authentication or configuration issues.

• C (Jira user license missing): The license of the Jira user account doesn't directly affect email transmission. Licenses control feature access within Jira, not SMTP mail flow.

• D (Full database/server disk): A full disk or database typically results in widespread system issues affecting many functionalities, not just email. You would expect application errors or failures beyond just mail problems.

• E (Jira license expired): Expired Jira licenses may limit functionality but usually don’t disable email notifications immediately.

In conclusion, the expired SMTP password (Option B) is the most technically accurate and common cause for this email failure scenario. Verifying and updating SMTP credentials in Jira’s outgoing mail settings will usually resolve the problem.

Question 6:

Jan created a new Select List custom field called Department for the MCAS project. However, his Jira dashboard gadget that filters issues with an empty Department field shows “No Data Available.” What is causing this?

A. The field is marked as Optional in the Field Configuration.
B. Jan lacks the Browse Project permission.
C. The Department field’s context does not allow empty values.
D. The MCAS project was not re-indexed after creating the field.
E. The JQL filter query is invalid.
F. Issue security restrictions are preventing data display.

Correct Answer: C

Explanation:

In Jira, how custom fields behave—whether they appear as empty, can be searched, or are required—depends heavily on the field’s context and configuration. In this case, the problem arises because the context of the Department select list field was not set to allow empty (null) values, which causes the JQL query filtering for Department is empty to return no results.

Here’s why this happens:

When you create a select list custom field, Jira can restrict the valid values and contexts where the field applies. If the field context does not permit “no value” (i.e., the field cannot be left empty), Jira will not consider any issues as having an empty Department value, even if none was explicitly set. Consequently, a gadget or filter searching for empty Department values will find no matching issues, resulting in “No Data Available.”

Breaking down the incorrect options:

• A (Optional field): Marking a field as Optional means it’s not mandatory on screens, but this doesn’t affect whether it can be empty or how Jira treats empty values in queries.

• B (Browse permissions): Jan can see other gadgets and issue counts, so his permissions are sufficient to view the data.

• D (Re-indexing): While re-indexing can fix some display or search issues, failure to allow empty values in the field context specifically causes this filter to return no results.

• E (Invalid JQL): The JQL syntax project = MCAS AND Department is empty is valid and should work if the field context permits empty values.

• F (Issue security): If issue security was the problem, it would affect all gadgets or issue visibility, not just this particular filter.

To fix this, you would update the field context to allow empty values or modify the filter logic. This ensures the gadget correctly displays issues where the Department field is unset.

Question 7:

When importing a workflow from your staging Jira (version 6.4) to your production Jira (version 6.3), you receive a notification that post-functions will not be imported. What is the most likely cause?

A) The apps installed on the staging environment differ from those on production.
B) The staging and production Jira versions are different.
C) The workflow was exported using XML instead of JWB format.
D) Custom post-functions are not included in workflow exports.

Correct Answer: A

Explanation:

When migrating workflows between Jira instances, particularly those containing custom post-functions, it is crucial to ensure that the target environment supports those customizations. Post-functions are actions that occur after a transition in a workflow, and many organizations rely on third-party plugins (apps) to add custom post-functions.

The correct answer here is A because if the staging instance has apps or plugins that provide specific post-functions but those apps are not installed or enabled in the production environment, Jira cannot import or reconstruct those post-functions on production. Essentially, the workflow import depends heavily on the availability of the same plugins on both instances.

Option B, which cites version differences, is less likely the cause. Although there might be minor incompatibilities between Jira 6.3 and 6.4, these versions are quite close, and version mismatch alone typically does not cause post-functions to be omitted during import. The presence or absence of supporting plugins plays a far greater role.

Option C is incorrect because Jira exports workflows in XML format. There is no such thing as a JWB format for Jira workflow exports, so this choice is invalid.

Option D suggests that custom post-functions are never included in exports. While it is true that certain custom post-functions may require plugins to be imported properly, the export itself does contain the necessary workflow data. The import failure is due to missing plugins on the target system, not because of an inherent export limitation.

Therefore, missing or different apps on the production system are the root cause of Jira not importing the post-functions successfully.

Question 8:

After upgrading Jira, users experience major problems, so you decide to roll back the upgrade. Which two outcomes should you expect from this rollback? (Choose two.)

A) Users will receive automatic email notifications about the rollback.
B) Any new issues created between the upgrade and rollback will be lost.
C) The Jira color scheme will reset to default to indicate the rollback.
D) Jira will return to the exact configuration it had before the upgrade.
E) Jira will need to be reconnected to external systems it was integrated with.

Correct Answers: B, D

Explanation:

When a rollback is performed after a problematic Jira upgrade, it generally involves restoring Jira to its previous state by using backups taken before the upgrade. Understanding what happens during this process is important for Jira administrators and support personnel.

Answer B is correct because any issues created or changes made after the upgrade will be lost during the rollback. This happens because restoring from a backup replaces the current database with the previous one, effectively erasing any data created after the backup point. This is a critical consideration in rollback planning to avoid data loss surprises.

Answer D is also correct. Since rollback typically involves restoring both the database and application files from a pre-upgrade backup, all configurations—including workflows, permissions, plugins, and system settings—will revert to how they were before the upgrade. This ensures the system returns to a known, stable state.

Option A is incorrect because Jira does not have a built-in feature that automatically sends emails to users about rollbacks. Communication regarding rollbacks must be handled manually by administrators.

Option C is false since the Jira color scheme or user interface settings do not automatically reset or change to indicate a rollback occurred.

Option E is incorrect because integrations with other systems should remain intact after a rollback, provided the backup fully captured the integration configurations. Unless changes were made during the upgrade that altered integration settings, reconnecting is typically not required.

In summary, the most important rollback effects are data loss of any changes made after the backup and restoration of prior configurations, making B and D the correct responses.

Question 9:

During the migration of users from Company B’s Active Directory to Company A’s directory, group memberships are being adjusted for better security control. However, many users report they do not have the correct group memberships after the migration. 

What configuration change should you implement to fix this issue?

A. Change the order of directories to list Company A before Company B.
B. Activate the Crowd user directory.
C. Move the Jira Internal Directory to the top of the directory list.
D. Synchronize the Company A directory.
E. Disable the Company A directory.
F. Disable the Company B directory.

Correct Answer: A

Explanation:

When integrating multiple user directories with systems such as Jira or Atlassian products, the sequence in which directories are checked plays a critical role in authentication and group membership resolution. These systems validate user credentials and group associations by searching directories in the order they appear in the configuration.

In this scenario, users are migrated from Company B’s Active Directory to Company A’s, with group memberships updated in Company A to reflect improved, fine-grained security. However, if the directory order places Company B before Company A, the system authenticates users against the old directory first. Consequently, it applies outdated group memberships from Company B, ignoring the updates in Company A. This explains why users complain about incorrect access rights.

The solution is to reorder the directories so that Company A precedes Company B. This change forces Jira or the system to query the updated directory first, ensuring users are authenticated with the correct group memberships and security policies.

Other options are less suitable: enabling Crowd (B) is irrelevant unless Crowd is used; prioritizing the Jira Internal Directory (C) affects only internal users and won't help with external directory conflicts; syncing Company A (D) keeps data current but doesn’t fix directory priority; disabling Company A (E) removes access entirely; and disabling Company B (F) risks cutting off users who haven’t migrated fully.

Therefore, simply reordering the directories so Company A is listed before Company B is the safest and most effective method to ensure that user authentications and group memberships reflect the latest changes during migration.

Question 10:

After upgrading your Jira system, a critical app used by your organization starts malfunctioning. Which two steps would be best to diagnose and resolve this problem? (Choose two.)

A. Request the system administrator to review catalina.out logs for error stack traces.
B. Ask the system administrator to enable SQL query logging.
C. Have the system administrator set the logging level of package com.atlassian to Trace.
D. Instruct the system administrator to add the app’s package to the Jira logger for detailed logging.
E. Request the logging level for all packages be set to FATAL in the Logging & Profiling settings.

Correct Answers: A, D

Explanation:

When a Jira upgrade causes an app to behave unpredictably or stop working correctly, effective troubleshooting focuses on identifying the exact cause via logs and focused diagnostics.

First, reviewing the catalina.out log (Option A) is a crucial step. This file contains Tomcat server logs, including Java stack traces and error messages generated during application runtime. Stack traces often pinpoint the exact code failures or exceptions that cause the app malfunction. Accessing these logs helps identify compatibility issues, missing dependencies, or configuration problems introduced by the upgrade.

Secondly, adding the specific app’s package or namespace to Jira’s logger (Option D) is highly valuable. This action configures Jira’s logging subsystem to capture detailed debug information for just the problematic app, isolating its internal behavior without overwhelming the logs with unrelated information. It allows for real-time monitoring of the app’s operations, which aids in quickly pinpointing the root cause.

Other options have limitations or risks: enabling SQL logs (B) might help with database query issues but is generally not the primary step for app failures post-upgrade; setting the entire com.atlassian package to Trace (C) produces extremely verbose logs that may degrade performance and make pinpointing problems harder; setting logging to FATAL (E) reduces the log detail to only the most severe errors, likely hiding useful warnings or errors needed for debugging.

In summary, combining server log review (catalina.out) with targeted logging for the app provides the best balance of information and manageability to effectively troubleshoot and resolve app issues after a Jira upgrade.