Atlassian ACP-100 Exam Questions

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.

View the Exhibit to see Jan's entire dashboard.

✑ The first gadget shows 26 issues in the project by Status.

✑ The second gadget shows that there are three issues that have the new Department field set.

The last gadget shows "No Data Available". The filter query for that gadget is "project=MCAS and Department is empty."

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

The field is marked Optional in the Field Configuration.

Jan does not have the proper Browse permissions.

The field context on the Department field was not set to allow empty values.

You created the field Department but did not re-index the MCAS project.

The JQL query for the filter is not valid.

There is issue security on the issues.

Correct Answer: D

The fact that the gadget shows 'No Data Available' indicates that Jira is not correctly identifying issues where the Department field is empty. This can often happen if the project was not re-indexed after creating or modifying custom fields. Re-indexing the project will ensure that Jira correctly recognizes and processes the new field and its values. Therefore, re-indexing the MCAS project would likely resolve the issue.

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?

The apps installed on staging are not the same as on production.

The production and staging instances are using different versions of Jira.

You exported the workflow as XML instead of JWB.

Custom post-functions are not included in workflow export.

Correct Answer: B

The production and staging instances are using different versions of Jira. Specifically, staging Jira is on version 6.4 and production Jira is on version 6.3. Since there is a version mismatch between the two Jira instances, not all elements, including post-functions, are guaranteed to be compatible or properly imported. Even though custom post-functions may not always be included in workflow exports, the key issue here is the incompatibility between the two different versions of Jira, which can restrict the import functionality.

You have planned, tested, and performed a Jira upgrade.

The upgrade appeared to be a success; however, after several hours of use, your users are reporting significant problems and you decide to roll back.

Which two effects do you expect to see after the rollback? (Choose two.)

Emails will automatically be sent out to tell people about the rollback.

New issues entered between upgrade and rollback will be lost.

The color scheme will be set back to default to indicate there was a rollback.

Jira will go back to the same schemes as before the upgrade.

Jira will need to be reconnected to other systems it was integrated with.

Correct Answer: BD

After performing a rollback, new issues entered between the upgrade and the rollback will be lost because the rollback reverts to a pre-upgrade state where those issues did not yet exist. Additionally, Jira will revert to the same schemes that were in place before the upgrade, as the rollback process restores the previous configuration and setup.

Your user directories are configured as shown:

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?

Reorder the directories so Company A is before Company B.

Enable the Crowd user directory.

Reorder the directories so the Jira Internal Directory is listed first.

Synchronize the Company A directory.

Disable the Company A directory.

Disable the Company B directory.

Correct Answer: A

To ensure users get the correct group memberships from the new Company A directory instead of the deprecated Company B directory, you should reorder the directories so that Company A is before Company B. This will prioritize the active and updated directory over the old one, ensuring that group membership information is correctly inherited from the new source.

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.)

Ask the System Administrator for catalina.out logs and inspect for stack traces.

Ask the System Administrator to enable the SQL log.

Ask the System Administrator to set package com.atlassian to Trace logging level.

Ask the System Administrator to add the app to the logger.

Ask the System Administrator to set the logging level to FATAL on all package names, Under Logging & Profiling.

Correct Answer: AC

To debug and resolve issues with a Jira app not working reliably after an upgrade, you can use several methods. One effective way is to inspect the catalina.out logs for stack traces, as this file contains application server logs that can help identify errors and issues (option A). Another useful method is to set package com.atlassian to Trace logging level, which will provide detailed logging information that can help in diagnosing the problem at a granular level (option C). Setting the logging level to FATAL (option E) is not helpful for debugging because it only logs critical errors and omits useful information needed for debugging. Enabling the SQL log (option B) might be helpful in some contexts but is not directly relevant to app reliability issues. Adding the app to the logger (option D) might assist, but it is not as impactful as the chosen methods.