Jira ACP-120 Exam Dump and Braindumps

You were hired to replace the former Jira administrator at a company called Nimbus Apps. The organization has fewer than 110 staff and uses a single domain example.com. Two weeks ago the Jira Software annual plan was increased from 80 seats to 160 seats. Since that change you have noticed that nearly all Jira seats are now allocated. The previous admin says they have not approved any user access requests and that every employee uses one corporate email at example.com. What is the most likely cause of this situation?

• ❏ A. The company domain example.com has been verified in Atlassian Access

• ❏ B. An invite link for Jira Software was turned on

• ❏ C. The company domain example.com was added to an automatic approval allowlist

• ❏ D. Site access has been configured as public allowing anyone to join

Mira is the Jira administrator and project lead for the company-managed project “FIN” which is used by distributed team members across several regions and working in different languages. Mira must present workflow statuses in the local languages for users in that project. Which Jira configuration should Mira use to translate status names?

• ❏ A. Install a language pack app from the Marketplace

• ❏ B. Use the Issue Attributes Statuses administration page to define localized status names

• ❏ C. Add the required language in the Language support project settings

• ❏ D. Set the transition property jira.i18n.title to translate status labels

Ryan opened the issue “SITE-72” in the company managed project “SITE” and assigned it to Priya. The project notification scheme sends an email on issue creation to the reporter the current assignee the project lead and all watchers. Priya received the notification after the issue was created but Ryan did not even though his personal settings show that “You’re the reporter” is enabled “You’re the assignee of the issue” is enabled and “Watch your issues” is set to Enabled. Ryan did receive an email when Priya later edited the description. Why did Ryan not get the email notification after creating the issue?

• ❏ A. The Jira user default setting AutoWatch own issues is turned off

• ❏ B. He has not enabled the personal setting “You make changes to the issue” in his profile

• ❏ C. An issue security level is preventing Ryan from getting the creation notification

• ❏ D. Outgoing mail has been disabled on the instance

• ❏ E. Ryan lacks the Browse Projects permission in the project

When creating a new team-run project in Atlasboard which project access levels can the project creator select? (Choose 3)

• ❏ A. Limited visibility

• ❏ B. Public listing

• ❏ C. Private project

• ❏ D. Restricted access

• ❏ E. Personal workspace

• ❏ F. Open access

Mina is the scrum master for a product team at Aurora Systems and she is preparing to finish a sprint. When she closes the sprint she needs to ensure every issue has a Fix Version value assigned. Which project permission must Mina hold so she can update the Fix Version field?

• ❏ A. Close Issues permission

• ❏ B. Resolve Issues permission

• ❏ C. Manage Sprints permission

• ❏ D. Edit Issues permission

• ❏ E. Version Issues permission

Priya can attach files on nearly every issue in the company managed project “CORE” except when an issue is in the “Obsolete” status. What could explain this restriction?

• ❏ A. A workflow transition property is configured

• ❏ B. The project permission scheme does not grant the Attach Files permission

• ❏ C. The attachment field is absent from the issue screen

• ❏ D. A workflow condition prevents the action

• ❏ E. A workflow status property is configured to restrict attachments

Rina’s team uses the Default Screen Scheme and must add several screens to a centrally managed project. The project includes four issue types Epic Story Defect and Task. The requirements are Defect needs a new screen for the View operation Defect and Task need a new screen for the Edit operation Story needs a new screen for the View operation Task needs a new screen for the Create operation and the workflow statuses Completed and Backlog require a transition screen. How many new screen schemes must Rina create?

• ❏ A. Four screen schemes

• ❏ B. One screen scheme

• ❏ C. Three screen schemes

• ❏ D. Two screen schemes

• ❏ E. Five screen schemes

Earlier this week Priya changed the issue layout for every issue type in the company managed project named “NovaCo”. Today she discovers that she cannot update the layout for one specific issue type in the “NovaCo” project. What is the most likely cause of this loss of access?

• ❏ A. An issue security scheme is preventing Priya from changing the issue layout

• ❏ B. The project permission named “Edit issues layout” was removed from Priya

• ❏ C. A Jira administrator revoked the “Administer projects” permission for Priya in the project

• ❏ D. The ability to change settings for that particular issue type was taken away from Priya

• ❏ E. Priya was removed as the project lead of the “NovaCo” project

Marina saves a filter called “SkillUp” to collect all training related issues for her team. Which of the following JQL expressions will return issues from that saved filter that do not yet have a resolution? (Choose 3)

• ❏ A. filter = SkillUp OR resolution is EMPTY

• ❏ B. filter = “SkillUp” AND resolution is EMPTY

• ❏ C. filter = ‘SkillUp’ AND resolution equals EMPTY

• ❏ D. filter = SkillUp AND resolution = EMPTY

• ❏ E. filter = ‘SkillUp’ AND resolution is EMPTY

• ❏ F. filter = “SkillUp” AND resolution is NULL

IssueFlow Cloud provides a Time Tracking feature that lets team members record hours spent on tasks. Which statements about Time Tracking in IssueFlow Cloud are accurate? (Choose 4)

• ❏ A. Users can change their default time unit for entries

• ❏ B. Users can hide or disable the Time Tracking feature entirely for a cloud project

• ❏ C. Users can set how many working days they have in a week in their account preferences

• ❏ D. Users need the Plan Tasks permission to record time on tasks

• ❏ E. Users can set their default number of working hours per day in their profile settings

• ❏ F. Users can change the duration display format used by Time Tracking

All exam questions come from my Jira ACP-120 Udemy course and certificationexam.pro

Marco administers a large Jira Cloud instance for a community project and his users can share saved filters with other people inside the site but they cannot make those filters public. What is the most likely reason?

• ❏ A. The global permission “Share dashboards and filters” is not granted to the users

• ❏ B. The site level toggle “Allow users to share dashboards and filters with the public” is disabled

• ❏ C. The default user preference “Default sharing for filters and dashboards” is set to Private

• ❏ D. Users do not have the global permission “Manage group filter subscriptions”

Taylor, the Jira administrator for the cloud site phoenix-team.scrumtuous.com, has just removed a user from that Jira Cloud site. Which statement is definitely true?

• ❏ A. Removing the user from the site also revokes their access to every Jira Cloud site and organization they belong to

• ❏ B. Saved searches and filters that mention the removed account will stop working until someone updates them manually

• ❏ C. The removed user can be reinvited to the Jira Cloud site phoenix-team.scrumtuous.com

• ❏ D. User picker fields that reference the removed account will be automatically cleared or reassigned

Ravi manages issue flows for Nimbus Solutions and he must find every issue that was transitioned back into the To Do status so he can reassign them to his team. The project only uses the statuses To Do, In Progress and Done. Which JQL will return those reopened issues?

• ❏ A. status changed from Done to ‘To Do’

• ❏ B. status was not in (‘In Progress’, ‘Done’)

• ❏ C. status was Done AND status = ‘To Do’

• ❏ D. status = ‘To Do’ AND resolution is EMPTY

• ❏ E. status = Reopened

Maya created issue RTN-49 and she received email alerts after the issue was created and for every transition comment and update. After RTN-49 was moved to the status “PENDING_APPROVAL” she stopped receiving email notifications while other watchers continued to get them. The RTN project is a company managed project created from a Scrum template and it uses the default notification scheme. The project configuration has not been changed since Maya opened the issue. Which configuration is most likely causing Maya to stop receiving email notifications?

• ❏ A. Project permission scheme

• ❏ B. Issue security level

• ❏ C. User profile notification preferences

• ❏ D. Notification scheme

Mira has 14 issues using the issue link type ‘blocks’ and 2 issues using the issue link type ‘blockz’. Because the link type name was entered incorrectly she wants to consolidate ‘blockz’ into ‘blocks’. What action must she take to accomplish this?

• ❏ A. Rename the incorrect link type to the desired link type name

• ❏ B. Attempt to merge the two link types into a single link type

• ❏ C. Delete the wrong link type and swap its existing uses to the correct link type during deletion

• ❏ D. Use a bulk edit of issues to update the linked issue type references

A new company managed project called “Orion” was created from a Kanban template and Ryan was given the “Administrators” project role for the project. Ryan must remain the only project administrator to keep configurations consistent. Ryan gathered these requirements from his team. Create components named “UI” “API” and “Security”. Create a new Kanban board inside the project that displays only stories. Show the due date on every screen and on the issue layouts used by the project. Update the issue layout so that fields are hidden when they are empty. Grant the Delete issues project permission to the project lead for the Orion project. All global permissions are left at their default settings and have never been changed. Which configuration tasks will Ryan not be able to perform? (Choose 2)

• ❏ A. Create a new Kanban board inside the project that only shows stories

• ❏ B. Grant the Delete issues project permission to the project lead of the Orion project

• ❏ C. Create components named “UI” “API” and “Security”

• ❏ D. Update the issue layout so that fields are hidden when they are empty

• ❏ E. Show the due date on every screen and ensure the due date appears in the issue layouts used by the project

Coral manages a Jira workflow for her team and needs these controls in place. Team members must not be able to log work when an issue is in the Closed status. The team should receive a prompt asking them to confirm the issue is ready before moving it into Closed status. The workflow should require a specific custom field to be filled when transitioning an issue from On Hold to Closed status. Which workflow components does Coral need to modify to implement these rules? (Choose 3)

• ❏ A. Conditions

• ❏ B. Post Functions

• ❏ C. Transition Properties

• ❏ D. Status Properties

• ❏ E. Validators

• ❏ F. Transition Screen

Emily is the release manager for the project “ZETA” and the project currently contains two archived releases labeled 2.1 and 3.0. Release 2.1 was in the status “RELEASED” before archiving and release 3.0 was in the status “UNRELEASED” before archiving. Emily accidentally archived both releases and she now wants to know whether she can restore them and whether she should do that. Which statement is correct?

• ❏ A. Emily cannot unarchive either release 2.1 or 3.0

• ❏ B. Unarchiving release 2.1 will change its status to “UNRELEASED”

• ❏ C. Emily can and should unarchive both releases 2.1 and 3.0 to correct her mistake

• ❏ D. Emily will be able to unarchive only release 3.0

• ❏ E. Emily will be able to unarchive only release 2.1

Taskline Cloud accepts issue reports via an internal mail pipeline that first retrieves inbound messages and then inspects them for non request content and anomalies. Which component is responsible for marking messages as spam?

• ❏ A. Mail handler

• ❏ B. Cloud Pub/Sub

• ❏ C. Email processor

• ❏ D. Email fetcher

• ❏ E. Email puller

All exam questions come from my Jira ACP-120 Udemy course and certificationexam.pro

Anyone who signs in to Meridian’s Jira instance can search for view create and edit issues. Which team managed project access level matches this requirement?

• ❏ A. Public

• ❏ B. Limited

• ❏ C. Open

• ❏ D. Private

A support engineer at BluePeak accidentally created a custom field named “Priority” that duplicates Jira Cloud’s built in Priority field. If someone runs the JQL query priority = High what behavior will occur?

• ❏ A. The JQL will match values from both the built in Priority field and the custom Priority field

• ❏ B. The JQL will fail and show a name conflict error

• ❏ C. Jira will resolve the name to the built in Priority system field and use its values

• ❏ D. Jira will use values from the custom Priority field instead of the system field

Jordan is the lead for Meridian Labs and has requested that the custom field “Acceptance Criteria” be removed from the project “NOVA” because it is no longer used. Filters and reports should not break after the change so end users will not need to update saved filters, and reports and filters for project “NOVA” should display an empty value for that custom field. Management also requires that all historical values be preserved. What is the best course of action?

• ❏ A. Delete the “Acceptance Criteria” custom field from the global custom fields list

• ❏ B. Archive the “Acceptance Criteria” custom field for project “NOVA”

• ❏ C. Set the “Acceptance Criteria” custom field to hidden in every field configuration assigned to project “NOVA”

• ❏ D. Remove the “Acceptance Criteria” custom field from every screen used by project “NOVA”

• ❏ E. Create a project specific field context for the “Acceptance Criteria” custom field that has no default values for project “NOVA”

Marco and Priya are working together in the same company-managed Jira project. Both users can view the project issues. Marco can assign an issue to Priya but Priya cannot assign that issue to Marco. What could explain this situation? (Choose 2)

• ❏ A. A project issue security level hides Marco from the assignee picker

• ❏ B. Priya lacks the Assign Issues project permission

• ❏ C. Marco does not have the Assign Issues project permission

• ❏ D. Marco is not configured as an assignable user in the project

• ❏ E. Priya is not a member of the Project Administrators group

A regional software studio running Jira Cloud wants to export the site so it can be restored into Jira Server. Which site configuration must be completed before creating a Jira Cloud site backup to make the backup compatible with Jira Server?

• ❏ A. Disable outgoing email for the site

• ❏ B. Disable all team managed projects so they can be re enabled after the export

• ❏ C. Convert team managed projects to company managed projects

• ❏ D. Remove only unneeded team managed projects from the site

• ❏ E. Delete every team managed project from the site

Which of these JQL expressions will return issues that were resolved on or after the tenth day of the current month? (Choose 3)

• ❏ A. resolutiondate > startOfMonth(“+8d”)

• ❏ B. resolutiondate = startOfMonth(9d)

• ❏ C. resolutiondate >= startOfMonth(“+9d”)

• ❏ D. resolutiondate > startOfMonth(9d)

• ❏ E. resolutiondate > startOfMonth(“+9d”)

• ❏ F. resolutiondate > startOfMonth(“9d”)

Ravi has received these requirements for issues in the “CSRV” company managed project at Mosaic Support. Only users in the project role Analysts should be permitted to edit issues that are in the “Resolved” status. Only members of the group help-desk-managers should be able to see the transition labeled “Reopen”. Which workflow configurations should Ravi apply to meet these requirements? (Choose 2)

• ❏ A. Workflow validators

• ❏ B. Step properties

• ❏ C. Workflow post functions

• ❏ D. Workflow conditions

• ❏ E. Workflow triggers

The excerpt of the permission scheme for the “MOBILITY-APP” project is shown below. Only the global permission “Administer Jira” is granted and all other global permissions are unassigned. Members of the group “app-mobile-group” must frequently change the reporter field for a large batch of issues in the “MOBILITY-APP” project where there are over 125 issues. Which two combined actions will allow them to do this? (Choose 2)

• ❏ A. Add app-mobile-group to Project Role “Analysts”

• ❏ B. Add app-mobile-group to Make bulk changes global permission

• ❏ C. Add the Project Role “Developers” to Make bulk changes global permission

• ❏ D. Add app-mobile-group to Project Role “Scrum Team”

• ❏ E. Add app-mobile-group to Project Role “Developers”

• ❏ F. Assign Make bulk changes global permission to the Project Role “Analysts”

Diego manages the company managed project “REMEDY” at BlueMarble and the project uses three issue types which are Epic Story and Task. The team requires the following field behavior. For the Priority system field Epics must be hidden Stories must be shown and optional and Tasks must be required. For the Business Value custom field Epics must be required with options C1 C2 C3 Stories must be required with options C10 C20 C30 and Tasks must have the field hidden. For the Score custom field Epics must be required and Stories and Tasks must have the field hidden. Which configuration change will satisfy all these requirements?

• ❏ A. Create three field configurations and add two custom field contexts

• ❏ B. Create three field configurations and add three custom field contexts

• ❏ C. It is not possible to meet all requirements

• ❏ D. Create two field configurations and establish two custom field contexts

• ❏ E. Use a single field configuration for the project

Asha the project lead created the issue “ENG-123” in the company managed project “ENG” and assigned it to Luis and outgoing mail is enabled and both Asha and Luis can view the issue and the notification scheme for the Issue Created event sends messages to the reporter the current assignee the project lead and all watchers and Asha and Luis have these personal notification settings You’re the reporter enabled enabled You’re the assignee of the issue disabled disabled Watch your issues enabled enabled You make changes to the issue enabled disabled Which statement correctly describes the notification email that will be sent after the creation of issue “ENG-123”?

• ❏ A. Both Asha and Luis will receive notification emails

• ❏ B. Notification depends on project permissions assigned to the users

• ❏ C. Asha will receive a notification email while Luis will not

• ❏ D. Notification depends on the issue security level

• ❏ E. Neither Asha nor Luis will receive a notification email

• ❏ F. Luis will receive a notification email while Asha will not

A reorganization at Halcyon Analytics requires Maya to update her Jira project settings. As the Jira administrator for her group, which project detail edits are optional for Maya to make? (Choose 3)

• ❏ A. Project type

• ❏ B. Project description

• ❏ C. Avatar

• ❏ D. Project URL

• ❏ E. Project name

• ❏ F. Project category

Which statements correctly describe relocating issues between projects in a Jira Cloud instance? (Choose 4)

• ❏ A. Users require the “Move Issues” permission in the source project

• ❏ B. Issues cannot be transferred from an enterprise-managed project to a team-managed project

• ❏ C. Users can change an issue type as part of the move operation

• ❏ D. Users must have the “Edit Issues” permission in the origin project

• ❏ E. The move action only allows changing the issue’s project and nothing else

• ❏ F. Users need the “Create Issues” permission in the destination project

You manage a large Jira Cloud instance for SummitSoft that supports many active users and roughly four hundred agile teams. A scrum master reports that three JQL searches should add up but the totals do not match and asks you to investigate. The queries returned the following results (A) project = “CORE” returned 1500 issues (B) project = “CORE” and fixVersion = 12 returned 30 issues © project = “CORE” and fixVersion != 12 returned 260 issues How would you resolve the mismatch?

• ❏ A. Use double quotes around the fixVersion value so it becomes fixVersion = “12”

• ❏ B. Trigger a background reindex of the Jira Cloud site

• ❏ C. Modify query © to project = “CORE” and (fixVersion != 12 OR fixVersion is EMPTY)

• ❏ D. Adjust the issue security scheme so the scrum master has access to every security level

• ❏ E. Announce downtime to users and perform a full reindex of the Jira Cloud instance

Several staff at Cloudline Solutions are reporting that notification emails from Jira arrive as plain text and appear outdated. They want HTML formatted notifications with clickable links and images enabled for every account. Your IT director asked you to configure the instance so that all users receive HTML emails. What is the most appropriate action to take?

• ❏ A. Create a support ticket with the software vendor and request that they change every user to receive HTML email

• ❏ B. Change the system user default preference “Email format” to HTML and click Apply to enforce it for every user

• ❏ C. Adjust the outgoing notification templates to always wrap messages in HTML

• ❏ D. Send all users a step by step message explaining how to change their own notification format settings

Priya must build a JQL query that returns issues she reported where the summary contains the words “urgent” or “critical” what JQL should she use? (Choose 2)

• ❏ A. creator in (Priya) AND (summary ~ “urgent” OR summary ~ “critical”)

• ❏ B. reporter = Priya AND (summary ~ “\[urgent\]” OR summary ~ “\[critical\]”)

• ❏ C. reporter = Priya AND summary ~ (“urgent, critical”)

• ❏ D. reporter = Priya AND (summary ~ “urgent” OR summary ~ “critical”)

• ❏ E. reporter = Priya AND summary in (urgent, critical)

• ❏ F. reporter = Priya AND summary ~ “urgent” OR summary ~ “critical”

Maya can view issue RTL-972 in the Retail company-managed project but she cannot change the issue security level. You verified that Maya has the Browse Projects permission and the Set issue security permission and the Create issue permission. The issue security scheme for the Retail project contains 4 security levels. What are possible reasons Maya cannot change the security level for issue RTL-972? (Choose 2)

• ❏ A. Maya does not have the “Transition issues” project permission

• ❏ B. Maya is not the project administrator

• ❏ C. Maya lacks the “Edit issues” project permission

• ❏ D. Maya is not included in the other security levels that would allow changing the issue security

• ❏ E. Maya does not have the “Resolve issues” project permission

• ❏ F. Maya is not listed as the project lead

Maya added a new custom field called “Project Goal” but she only sees it on a subset of issues within the same project. What could explain this behavior? (Choose 2)

• ❏ A. The field scope context limits the custom field to specific issue types or projects

• ❏ B. Issue level security is applied so some issues hide the field from certain users

• ❏ C. The custom field is set to hide when it has no value so it disappears on issues with empty values

• ❏ D. Maya lacks the Browse Projects permission for that project

• ❏ E. “Project Goal” is configured as a hidden field in the project field configuration

Marco is updating a workflow for the Nova team and has these rules to enforce. Users must not be able to select the ‘Approval’ resolution when an issue is in the ‘Done’ status. Only members of the leadership group should see the transition control that moves an issue to ‘Done’. A field value must be cleared automatically when an issue moves from ‘Pending’ to ‘Done’. Which workflow elements does Marco need to modify? (Choose 3)

• ❏ A. Conditions

• ❏ B. Status Properties

• ❏ C. Transition Screen

• ❏ D. Post Functions

• ❏ E. Validators

• ❏ F. Transition Properties

At SolvaTech the admin portal provides different levels of control for managing the instance and products. Which administrator role can access the billing and subscription management page?

• ❏ A. Both Platform Administrator and Jira Administrator

• ❏ B. Jira Administrator

• ❏ C. Platform Administrator

• ❏ D. Project Administrator

Elena created a filter subscription but she cannot see the project role in the recipients list, what could explain why the role does not appear?

• ❏ A. She is not assigned to that project role

• ❏ B. Project roles cannot be selected as recipients in filter subscriptions

• ❏ C. She lacks the Manage group filter subscriptions global permission

• ❏ D. She does not have the required project permission to view the project

All exam questions come from my Jira ACP-120 Udemy course and certificationexam.pro

You have provisioned a new Jira Cloud instance and created the company managed project “TIMELINE” from a Kanban template. Your manager asked you to update the project notification scheme so that external email recipients are informed when issues transition to status “COMPLETE”. What additional configuration is required to permit the project notification scheme to send emails to external users?

• ❏ A. Atlassian support must be contacted to activate outbound notifications to external accounts

• ❏ B. Grant the group “Anyone” the Browse projects project permission

• ❏ C. Enable a global system setting named Send external notifications

• ❏ D. Configure the project to send outgoing mail from an email address on a verified domain

A support agent corrected a typo in an issue type label within a customer project. After renaming the issue type which related configuration should an administrator check to make sure users still find the same issues through saved queries?

• ❏ A. Dashboard gadgets that filter by the renamed issue type

• ❏ B. Issue type screen schemes that reference the renamed issue type

• ❏ C. Saved searches that reference the renamed issue type

• ❏ D. Global automation rules that refer to the issue type name

• ❏ E. Issue type schemes that include the renamed issue type

Which actions can an organization administrator perform on a managed user account in the corporate user directory? (Choose 3)

• ❏ A. Modify the account language setting

• ❏ B. Upload or replace the account profile photo

• ❏ C. Change the managed account email address

• ❏ D. Change the account default time zone

• ❏ E. Revoke API tokens issued by the account

• ❏ F. Reset the managed account password

Your engineering group uses a team-managed project to track work for release 1.2 which currently shows the status UNRELEASED. They want to move every unresolved issue from release 1.2 into the newly created release 2.5 and they also want to keep release 1.2 available in the Affects Versions field. Which operation should you perform?

• ❏ A. Merge release 1.2 into 2.5

• ❏ B. Archive release 1.2

• ❏ C. Release version 1.2

• ❏ D. Delete version 1.2

A support ticket was generated from an external client email at Northbridge Tech. The client did not receive a response from support lead Maya Ortiz so they sent a fresh separate email. What will happen?

• ❏ A. A new subtask will be added to the existing ticket

• ❏ B. A separate new issue will be created

• ❏ C. A new comment will be appended to the current issue

• ❏ D. Nothing will happen since the message content is identical

• ❏ E. A new issue will be created and linked to the existing ticket

Maya created a Jira filter using the JQL resolution CHANGED TO Unresolved AND assignee = currentUser() and then she created a subscription on that filter with the recipients set to the project-leads group which includes Maya and her colleague Leo?

• ❏ A. Leo will receive unresolved issues that are assigned to him

• ❏ B. Maya will receive only issues assigned to her that had their resolution cleared

• ❏ C. The JQL is invalid so the filter cannot be saved

• ❏ D. Leo will receive unresolved issues that are assigned to Maya

Maya manages board tasks for the company managed project “ORBIT” and she cannot change the component lead. The following summary shows the ORBIT project permission scheme where Administer Projects is assigned to the project role “Administrators” and Browse Projects is assigned to the project roles “Dev Team” and “Scrum Lead” and “Product Manager” and Edit issue is assigned to “Product Manager” and “Dev Team” and Resolve issues is assigned to “Dev Team” and “Scrum Lead” and Close issues is assigned to “Product Manager”. The ORBIT project configuration must be changed so Maya can update the component lead. What change is required?

• ❏ A. Add Maya to the “Dev Team” project role

• ❏ B. Add Maya to the “atlassian-addons-project-access” project role

• ❏ C. Add Maya to the “Administrators” project role

• ❏ D. Make Maya the Project lead

• ❏ E. Add Maya to the “Product Manager” project role

Marcus from HarborTech added a new status called ‘Closed’ and later saw that many issues in that status do not have a resolution set. What steps must Marcus take to update every issue that has an empty resolution to the ‘Closed’ resolution? (Choose 2)

• ❏ A. Create an Automation rule to set the resolution for issues in the ‘Closed’ status

• ❏ B. Run a bulk Edit operation to set the resolution field

• ❏ C. Add a post function to the ‘Closed’ transition that sets the resolution

• ❏ D. Request the Edit Issues project permission for the users who will update issues

• ❏ E. Use the bulk change feature with a Transition Issues operation to apply the new resolution

Priya has just created her first team-managed Scrum project at BluePeak Software and she wants to estimate work using Time rather than Story points. Which section of the project settings lets her change the estimation method?

• ❏ A. Board

• ❏ B. Issue types

• ❏ C. Features

• ❏ D. Access

• ❏ E. Details

• ❏ F. It is not possible to change the estimation setting for a team-managed Scrum project

Lina has been asked to audit a company managed project at HorizonsTech that uses two issue types called “Enhancement” and “Feature request”. She believes the two are redundant and plans to convert all “Enhancement” issues to the “Feature request” type and then remove the “Enhancement” issue type from the project. Which project settings should Lina review to confirm that deleting the “Enhancement” issue type will not cause issues? (Choose 2)

• ❏ A. Screens

• ❏ B. Notification scheme

• ❏ C. Workflows

• ❏ D. Permission scheme

• ❏ E. Field contexts

• ❏ F. Issue security levels

Which statement about creating links between issues in the issue tracker is correct?

• ❏ A. Outward link description and inward link description must be different names

• ❏ B. Issue linking cannot be turned off from the global administration settings

• ❏ C. Linking issues requires a project permission called “Link Issues”

• ❏ D. Only site administrators can define new types of issue links in the instance

A small development team at BrightLeaf Software uses Jira Cloud and they want to know which statements about team-managed projects are accurate? (Choose 3)

• ❏ A. A team can run parallel sprints that span several team-managed projects

• ❏ B. Any user with a Jira license can create and administer a team-managed project

• ❏ C. Project settings for a team-managed project can be shared with other projects

• ❏ D. Project administrators can define new roles within a team-managed project

• ❏ E. Team-managed projects allow adding custom quick filters on top of the board filter

• ❏ F. You can make a team-managed project publicly readable to anonymous visitors

A software team at Orbix Solutions reported that after a recent administrator update nobody can create issue links in either team-managed projects or company-managed projects and automation rules also fail when they try to add links. What is the most likely cause of this problem?

• ❏ A. A marketplace app or automation script interfered with the linking functionality

• ❏ B. The Link issues project permission was removed from every project permission scheme

• ❏ C. All link types were renamed in the instance

• ❏ D. The system setting for issue linking was switched off globally

Maya and Omar manage two company-owned projects named Campaigns and MobileClient. Both users can view every issue in those projects. Maya cannot link a ticket from Campaigns to MobileClient while Omar can link his ticket. What configuration should Maya request from an administrator so she can link her issue?

• ❏ A. Issue security scheme

• ❏ B. Project permission

• ❏ C. Permission scheme

• ❏ D. Issue linking global setting

Marco from AtlasSoft set up a subscription for his squad using the JQL project = “backend” and text ~ “urgent” and resolution is EMPTY. The team can view matching issues in the Issue Navigator yet they sometimes receive an email that contains no issues. What explanations might account for the empty notification? (Choose 3)

• ❏ A. The notification schedule is restricted to business hours only

• ❏ B. The project key must match capitalization exactly in JQL

• ❏ C. The subscription owner enabled sending notifications even when the query returns no matches

• ❏ D. The JQL currently yields no results at the time the subscription job ran

• ❏ E. All of the issues that would match were resolved before the scheduled run

• ❏ F. The recipients lack the Browse Projects permission to view issues

Sam manages two company managed projects called Acme Alpha and Acme Beta. Which of the following situations would require Sam to create a new issue type?

• ❏ A. Acme Alpha must use an entirely different workflow for every issue type

• ❏ B. Acme Alpha requires a unique field configuration scheme applied only to that project

• ❏ C. Acme Alpha needs a new custom field shown on the view issue screen

• ❏ D. Acme Alpha must have a different option set for a select custom field

The correct answer is An invite link for Jira Software was turned on.

An invite link lets users join a Jira site without the administrator manually approving each request. When the plan was increased from 80 to 160 seats the link could have been used by many employees to join the site and consume seats quickly even though the former admin did not explicitly approve each user.

The company domain example.com has been verified in Atlassian Access is incorrect because domain verification by itself does not automatically add users to product sites. Domain verification is used to assert ownership of an email domain and to enable organization level controls but it does not cause immediate seat allocation without additional provisioning or approval rules.

The company domain example.com was added to an automatic approval allowlist is incorrect in this scenario because that setting would require explicit configuration in Atlassian Access or identity provisioning. It is a possible cause in general but it is less likely here since the simpler explanation of an active invite link fits the sudden, broad onboarding without manual approvals.

Site access has been configured as public allowing anyone to join is incorrect because Jira site visibility and project access are different from account provisioning. Making content public does not automatically create user accounts and fill product seats, so it would not explain the rapid increase in allocated Jira seats.

When many seats appear unexpectedly check for an active invite link first and then review organization provisioning rules and domain verification settings.

Use the Issue Attributes Statuses administration page to define localized status names is correct.

The Issue Attributes Statuses administration page is the built in place where you define localized labels for workflow statuses so users see status names in their chosen language. Defining translations there changes only the displayed label and does not alter the workflow logic, and it is the supported approach for company managed projects when you need per language status names.

Install a language pack app from the Marketplace is incorrect because adding an app is not required to translate status names when Jira provides an administration page for localized status labels. A marketplace app might add features but it is not the standard method for this specific task.

Add the required language in the Language support project settings is incorrect because project language settings control general language preferences and interface behavior rather than providing a place to define per status translations. Localized status names must be defined in the Issue Attributes Statuses area.

Set the transition property jira.i18n.title to translate status labels is incorrect because transition properties affect transition behavior and transition titles rather than the status label translations. The jira.i18n.title property is not the supported mechanism for localizing status names.

When a question asks about localization look for answers that point to a specific administration page for translations and not solutions that require installing apps. Prefer native translation features when the question refers to built in configuration.

The correct answer is He has not enabled the personal setting “You make changes to the issue” in his profile.

This is because Jira suppresses notifications to the user who performs the action unless that user has explicitly allowed notifications for their own changes. As the creator and assigner Ryan was the actor during issue creation so he would not receive the creation email unless He has not enabled the personal setting “You make changes to the issue” in his profile were enabled. He did receive a notification when Priya edited the description because a different user performed that change.

The Jira user default setting AutoWatch own issues is turned off is not the reason because Ryan’s personal watch setting is shown as enabled and he did receive later update notifications. Autowatch defaults would not block a creation notification sent to the reporter when another setting is blocking self notifications.

An issue security level is preventing Ryan from getting the creation notification is incorrect because issue security would prevent Ryan from seeing the issue at all or from receiving any notifications about it, and he was able to receive the later update. The behaviour fits self notification suppression rather than security restrictions.

Outgoing mail has been disabled on the instance is wrong because notifications were successfully sent to Priya and Ryan later, so outbound mail is working on the instance.

Ryan lacks the Browse Projects permission in the project is not correct because Ryan created the issue so he necessarily had the ability to view or interact with that project at creation time, and he received a later update notice which shows permissions and access were functioning.

When you see questions about missing notifications think about who performed the action and check the user setting “You make changes to the issue”. The system will usually avoid emailing the actor unless that personal setting is enabled.

Limited visibility, Private project, and Open access are correct.

Private project is selected when the creator wants the project to be accessible only to invited team members and not visible to users outside the team.

Limited visibility is selected when the creator wants the project to appear in listings while keeping membership and detailed content restricted to authorized team users.

Open access is selected when the creator intends the project to be viewable or joinable by a broad audience without requiring individual invitations.

Public listing is incorrect because it merely describes being listed and does not represent a distinct access control setting in this scenario.

Restricted access is incorrect because it is not one of the selectable access levels for a team-run project here and it overlaps conceptually with the listed correct options.

Personal workspace is incorrect because that refers to an individual user area and not to a team-run project access level.

Read each option and map the wording to whether it controls who can see the project or who can join the project. Pay attention to the words visibility and private as they usually indicate different scopes of access.

The correct answer is Resolve Issues permission.

The Resolve Issues permission is required because closing a sprint normally involves transitioning issues to a resolved or done state and setting the Fix Version as part of that resolution. Having this permission lets Mina perform the resolution transition and apply or update the Fix Version value during that process.

Close Issues permission is incorrect because Jira does not rely on a distinct close permission to control resolution actions in most project permission schemes. Closing is handled through workflow transitions and the Resolve Issues permission.

Manage Sprints permission is incorrect because that permission controls creating and editing sprints and moving issues between sprints. It does not grant the rights to perform issue resolution or to set the Fix Version during a resolve transition.

Edit Issues permission is incorrect because although it allows editing issue fields directly, updating Fix Version during the sprint close is typically done as part of the resolve transition and that action requires Resolve Issues. Edit rights alone may not permit performing the resolution step.

Version Issues permission is incorrect because that permission governs creating and administering project versions rather than changing the Fix Version value on individual issues. It does not by itself allow resolving issues or setting Fix Version during a resolution.

When a question mentions updating fields as part of finishing work think about whether the action is part of a workflow transition. If it is then Resolve Issues is often the permission being tested.

The correct answer is: A workflow status property is configured to restrict attachments.

A workflow status property can prevent certain operations while an issue remains in a particular status. If the Obsolete status has a property that disables or blocks attachments then users will be able to add files on other issues but not when an issue is in Obsolete. That behaviour fits Priya’s scenario because the restriction applies only while the issue is in that status.

A workflow transition property is configured is incorrect because transition properties apply during the transition itself and not to actions performed while the issue is in a status. A transition property would not cause attachments to be blocked when an issue is sitting in Obsolete.

The project permission scheme does not grant the Attach Files permission is incorrect because a missing attach permission would block attachments across the project for the affected users. The problem described only occurs for issues in a single status so a project permission issue is unlikely.

The attachment field is absent from the issue screen is incorrect because hiding a field on the screen would affect visibility for all issues on that screen and would not selectively block attachments only when an issue is in the Obsolete status. Attachments can also be added by other means such as drag and drop or the API.

A workflow condition prevents the action is incorrect because workflow conditions control who can execute transitions and when transitions are available. Conditions do not prevent users from performing actions like adding attachments while the issue remains in a given status.

When a restriction applies only in a specific status first consider workflow status properties. Remember that transition properties and conditions act at transition time and project permissions affect all issues in the project.

The correct answer is Three screen schemes.

You need a separate screen scheme for each distinct set of operation screens that an issue type requires. Defect requires a unique view screen and a shared edit screen, Task requires a unique create screen and the same shared edit screen, and Story requires a unique view screen. That makes three distinct screen scheme mappings so you must create three screen schemes.

Workflow transition screens are applied to transitions and are separate from screen schemes. Adding transition screens for Completed and Backlog does not require additional screen schemes so they do not change the count.

Four screen schemes is incorrect because the changes do not produce four different operation mappings. Two of the changes share an edit screen which reduces the number of distinct screen schemes.

One screen scheme is incorrect because you need different mappings for at least Defect, Task, and Story so one scheme cannot cover all required operation differences.

Two screen schemes is incorrect because Task and Defect differ on create and view operations so they cannot both be represented by the same scheme even though they share the edit screen.

Five screen schemes is incorrect because transition screens do not count as screen schemes and there are only three unique operation mappings required among the issue types so five is too many.

When counting screen schemes identify each unique set of Create Edit and View mappings that an issue type needs. Remember that transition screens are configured on workflow transitions and do not require additional screen schemes.

A Jira administrator revoked the “Administer projects” permission for Priya in the project is correct.

The most likely reason is that editing issue layouts in a company managed project is a project administration task and it is controlled by the “Administer projects” permission. When that permission is removed a user loses the ability to change project configuration items such as issue layouts, which explains why Priya could change layouts earlier and now cannot update the layout for a specific issue type.

An issue security scheme is preventing Priya from changing the issue layout is incorrect because issue security schemes govern who can view or access individual issues and they do not control the project configuration screens used to edit issue layouts.

The project permission named “Edit issues layout” was removed from Priya is incorrect because there is not a distinct permission named “Edit issues layout” in standard Jira permission schemes. Layout editing is covered by project administration rights instead.

The ability to change settings for that particular issue type was taken away from Priya is incorrect because issue type settings and the layout configuration are managed at the project administration level rather than by a separate per issue type permission. Removing project admin rights would produce the observed loss of access.

Priya was removed as the project lead of the “NovaCo” project is incorrect because the project lead role mainly affects defaults and notifications and does not by itself remove project administration permissions unless the underlying permission was explicitly changed.

On the exam remember that configuration tasks such as editing issue layouts require the Administer projects permission and that answer choices mentioning a non standard permission name are often wrong.

The correct answers are filter = “SkillUp” AND resolution is EMPTY, filter = SkillUp AND resolution = EMPTY and filter = ‘SkillUp’ AND resolution is EMPTY.

All three of these use a saved filter and then narrow that set to issues with an empty resolution using the EMPTY keyword. Quoting the filter name with double quotes single quotes or leaving it unquoted are all acceptable depending on whether the name contains spaces. The important part is combining the saved filter with resolution is EMPTY or resolution = EMPTY so only unresolved issues from that saved filter are returned.

filter = SkillUp OR resolution is EMPTY is incorrect because it uses OR and that will return any issue that has no resolution as well as all issues in the saved filter. That broadens the result set beyond issues that are both in the saved filter and unresolved.

filter = ‘SkillUp’ AND resolution equals EMPTY is incorrect because JQL does not use the word equals as an operator. You must use = or is with the EMPTY keyword in JQL.

filter = “SkillUp” AND resolution is NULL is incorrect because NULL is not the JQL keyword for an empty field. The correct keyword to test for no value in the resolution field is EMPTY.

When you see a saved filter combined with a resolution check look for the use of AND and the EMPTY keyword. Also remember that filter names can be quoted or unquoted when they contain no spaces.

Users can change their default time unit for entries, Users can set how many working days they have in a week in their account preferences, Users can set their default number of working hours per day in their profile settings, and Users can change the duration display format used by Time Tracking are correct.

Users can change their default time unit for entries is correct because the Time Tracking feature lets individuals choose their preferred unit for logging so entries match how they work and reporting stays consistent.

Users can set how many working days they have in a week in their account preferences is correct because account preferences include workweek configuration so weekly totals and capacity calculations reflect each user s actual availability.

Users can set their default number of working hours per day in their profile settings is correct because that profile value is used to convert between days and hours and to compute daily capacity for planning and reporting.

Users can change the duration display format used by Time Tracking is correct because the system supports different duration formats so users can view time in the style they prefer without changing the recorded values.

Users can hide or disable the Time Tracking feature entirely for a cloud project is incorrect because the product does not provide a global hide or disable switch for Time Tracking at the cloud project level and access is controlled through permissions and configuration instead.

Users need the Plan Tasks permission to record time on tasks is incorrect because recording time is controlled by logging or time tracking permissions rather than the planning permission, so plan rights are not a prerequisite for entering hours.

Focus on whether a statement describes a user preference, a project setting, or a permission. Preferences are usually per account or profile and permissions control who can act, and that distinction often reveals the correct answers.

The site level toggle “Allow users to share dashboards and filters with the public” is disabled.

This site level toggle controls whether any user on the Jira Cloud site can make dashboards or saved filters publicly accessible outside the site. If the toggle is disabled users will still be able to share filters with other people inside the site but they will not have the option to publish them to the public.

The global permission “Share dashboards and filters” is not granted to the users is unlikely because that permission governs sharing within the application and not whether public sharing is allowed at the site level. The fact that users can share inside the site but not publicly points to the site toggle instead.

The default user preference “Default sharing for filters and dashboards” is set to Private is not the main cause because that preference only controls the initial default when a user creates a filter or dashboard. Users can change the sharing level after creation if site settings permit public sharing.

Users do not have the global permission “Manage group filter subscriptions” is incorrect because that permission relates to managing subscriptions to filters for groups and does not affect the ability to publish filters or dashboards publicly.

When a question contrasts internal sharing with public sharing check the site or global sharing settings first because public access is often controlled by a site level toggle.

The correct option is The removed user can be reinvited to the Jira Cloud site phoenix-team.scrumtuous.com.

When a user is removed from a specific Jira Cloud site the action removes their site membership but does not delete the underlying Atlassian account or the record of their activity. Administrators can invite the same Atlassian account back to that site using the normal invite process. That is why The removed user can be reinvited to the Jira Cloud site phoenix-team.scrumtuous.com is definitely true.

Removing the user from the site also revokes their access to every Jira Cloud site and organization they belong to is incorrect because removing a user from one site does not automatically remove them from other sites or from an organization. Organization and site memberships are managed separately and other site or organization admins must remove the user there if they want to revoke access globally.

Saved searches and filters that mention the removed account will stop working until someone updates them manually is incorrect because Jira retains issue assignments and user references even when a user is deactivated or removed from a site. Filters that rely on account identifiers will generally continue to return issues for the deactivated account rather than simply stopping to work.

User picker fields that reference the removed account will be automatically cleared or reassigned is incorrect because those fields keep referencing the deactivated or removed account. Jira does not automatically clear or reassign user picker values when a user is removed from a site and any changes must be made manually by an administrator or through a scripted update.

When you see questions about removing users think about the difference between an Atlassian account and a site membership and remember that removal from a site is often reversible while data and references usually remain intact. Consider whether the action affects the account or just the site membership.

The correct answer is status was Done AND status = ‘To Do’.

status was Done AND status = ‘To Do’ works because status was Done finds issues that at some point had the Done status and status = ‘To Do’ restricts results to issues that are currently in To Do. Together they return issues that were Done in the past and are now back in To Do which matches the definition of reopened for this project.

status changed from Done to ‘To Do’ is incorrect because that clause only matches issues that had a single direct transition from Done to To Do. It can miss issues that were Done and then passed through other statuses before returning to To Do.

status was not in (‘In Progress’, ‘Done’) is incorrect because it finds issues that were never in In Progress or Done. That is the opposite of what is required and it will not locate issues that were previously Done.

status = ‘To Do’ AND resolution is EMPTY is incorrect because it returns all unresolved issues currently in To Do. New issues that were never Done will also match this query so it does not specifically find reopened items.

status = Reopened is incorrect because the project uses only To Do, In Progress and Done. There is no Reopened status in this project so that query will not return the reopened issues described in the question.

When you need to find issues that were in one status and are in another now use a historical check with status was and combine it with a current check such as status = to filter the current state.

Issue security level is the correct configuration causing Maya to stop receiving email notifications.

Issue security levels control who can view a specific issue and Jira will only send notifications to users who have permission to see that issue. When RTN-49 was moved to the PENDING_APPROVAL status a security level was likely applied that excludes Maya while still including other watchers. That change in visibility explains why the other watchers continued to receive emails but Maya did not.

Project permission scheme is unlikely because project permission schemes govern broad project level abilities and would not normally change for a single issue when its status changes. A permission scheme change would also usually affect many users and not just one watcher.

User profile notification preferences is unlikely because Maya was receiving notifications earlier and the problem started only after the issue moved to a specific status. Personal notification settings would prevent all notifications for that user across events and would not explain why the stoppage aligns with a status transition.

Notification scheme is unlikely because the project is using the default notification scheme and other watchers are still receiving notifications. A change to the notification scheme would typically alter who gets messages for events globally and would not selectively stop one existing watcher from receiving alerts when issue visibility is the simpler explanation.

When one watcher stops getting alerts after a status change check the issue security level first because notifications are only sent to users who can view the issue.

The correct action is Delete the wrong link type and swap its existing uses to the correct link type during deletion.

Delete the wrong link type and swap its existing uses to the correct link type during deletion performs the consolidation in the administration UI by moving existing link usages from the incorrect type to the chosen correct type in one operation. This preserves the existing links and avoids manually editing each linked issue.

Rename the incorrect link type to the desired link type name is incorrect because you cannot rename an item into a name that is already in use and the system prevents duplicate link type names. Renaming will not consolidate two distinct link types when the target name already exists.

Attempt to merge the two link types into a single link type is incorrect because there is no dedicated merge operation for link types in the administration interface. The supported approach is deletion with a swap to reassign usages rather than a merge feature.

Use a bulk edit of issues to update the linked issue type references is incorrect because link types are configuration items and bulk editing issues is not a reliable or efficient way to change link type definitions. Bulk edits would be more error prone and would not provide the clean swap that preserves link metadata.

When consolidating configuration entries check the administration settings for a delete and swap option because it usually preserves links and is faster than editing issues one by one.

The configuration tasks Ryan will not be able to perform are Grant the Delete issues project permission to the project lead of the Orion project and Show the due date on every screen and ensure the due date appears in the issue layouts used by the project.

Grant the Delete issues project permission to the project lead of the Orion project is something Ryan cannot do because the Delete Issues right is granted through the project’s permission scheme and changing permission schemes or their global associations requires Jira administrator access rather than project administrator access.

Show the due date on every screen and ensure the due date appears in the issue layouts used by the project is also not possible for Ryan to enforce across all screens because adding fields to screens or changing screen schemes is a global configuration task that needs Jira administrator privileges in a company managed project.

Create a new Kanban board inside the project that only shows stories is something Ryan can do as a project administrator because boards can be created for the project and the board filter or board settings can be set to display only issues of the Story type.

Create components named “UI” “API” and “Security” is allowed because managing components is part of the project settings and a project administrator can add or edit components for their project.

Update the issue layout so that fields are hidden when they are empty is something Ryan can change at the project level because issue view layout settings that control visibility of empty fields are configurable from the project settings and do not require site administration.

When a task touches permission schemes or screens check whether it requires a Jira Administrator role. First verify whether the project is company-managed or team-managed to know which settings a project admin can change.

The correct options are Status Properties, Validators, and Transition Screen.

Status Properties are used to change behavior while an issue remains in a given status and they can be used to prevent actions such as logging work when an issue is in the Closed status.

Validators run when a transition is attempted and they can enforce that a specific custom field is populated when moving from On Hold to Closed so the transition will be blocked until the field is filled.

Transition Screen is the component that presents input to the user during a transition and it can be used to prompt users to confirm that the issue is ready to be closed or to collect a confirmation field before the transition completes.

Conditions are incorrect because they control who can see or execute a transition and they do not prompt users or enforce field values during the transition.

Post Functions are incorrect because they execute after a transition completes so they cannot prevent a transition or collect confirmation before an issue is moved to Closed.

Transition Properties are incorrect because they attach metadata to a transition and they do not disable actions while an issue is in a status or present a confirmation prompt to users during the transition.

When you see questions about preventing actions while an issue is in a status think status properties. When you need to enforce input use validators and when you need to ask the user or collect confirmation use a transition screen.

Emily can and should unarchive both releases 2.1 and 3.0 to correct her mistake. This is correct because unarchiving restores each archived release and returns it to the state it had before archiving, so 2.1 will be restored as RELEASED and 3.0 will be restored as UNRELEASED.

Unarchiving is the appropriate corrective action when releases were archived by accident because it preserves the original release records and statuses. If Emily has the release manager permissions she can reverse the archive and retain accurate release history.

Emily cannot unarchive either release 2.1 or 3.0 is incorrect because archived releases are recoverable and are not permanently removed by the archive action.

Unarchiving release 2.1 will change its status to “UNRELEASED” is incorrect because unarchiving restores the previous status, and 2.1 was RELEASED before it was archived.

Emily will be able to unarchive only release 3.0 is incorrect because both archived releases can be restored, not just 3.0.

Emily will be able to unarchive only release 2.1 is incorrect because both archived releases can be restored, not just 2.1.

When a question concerns archived items think about whether the system preserves prior states and check the release history before answering.

The correct answer is Email processor.

The Email processor is the component that inspects inbound messages and runs spam detection and classification logic, so it marks messages as spam. In a mail pipeline the processor is responsible for analyzing message content, applying rules or models, and annotating or flagging messages for downstream handling.

The Email processor typically updates message headers or metadata to indicate spam and then allows the routing or delivery components to act on that classification. This separation keeps fetching and transport duties distinct from content analysis and makes it clear that marking for spam belongs to the processor.

Mail handler is usually a routing or delivery component and it does not perform the content analysis needed to mark spam, so it is not the right choice.

Cloud Pub/Sub is a messaging transport that moves events between services and it does not analyze or classify message content, so it would not mark messages as spam.

Email fetcher retrieves inbound messages from external servers and focuses on collection rather than inspection, so it would not be responsible for marking spam.

Email puller is similar to a fetcher and its role is to pull messages into the pipeline rather than to perform classification, so it would not mark spam.

Focus on the verbs in the question. If a component is said to inspect or classify messages then the processor is the likely choice. If it is said to fetch or transport then it is not.

The correct option is Open.

Open is the team managed project access level that allows any user who can sign in to the Jira site to search for view create and edit issues which exactly matches the requirement.

Public is incorrect because that option would allow anonymous access without signing in or may not be offered for team managed projects in some configurations so it does not match a requirement that specifies signed in users.

Limited is incorrect because it restricts access to a subset of authenticated users or specific groups and therefore does not allow every signed in user to view or edit issues.

Private is incorrect because it limits access to explicit project members and administrators and it prevents general signed in users from creating or editing issues unless they are added to the project.

When a question says anyone who signs in can access content look for the access level that grants rights to all authenticated users. In team managed projects that is Open.

Jira will resolve the name to the built in Priority system field and use its values is correct.

When JQL evaluates a query it maps the field name to a single field id and system fields take precedence. Creating a custom field called Priority does not change which field id the name resolves to in queries. The built in Priority system field therefore supplies the values that the JQL expression uses when you run priority = High.

The JQL will match values from both the built in Priority field and the custom Priority field is incorrect because JQL does not merge values from two different fields with the same display name. The query only evaluates the single field id that the name resolves to.

The JQL will fail and show a name conflict error is incorrect because Jira does not present a name conflict error in this case. The system resolves the name to a field and executes the query rather than failing with an error.

Jira will use values from the custom Priority field instead of the system field is incorrect because custom fields do not override built in system fields for JQL name resolution. The built in Priority field remains the source of values for queries that reference that name.

When a question mentions fields with the same name remember that system fields take precedence in JQL and you can verify which field a name maps to by checking field ids in the admin console.

The correct answer is Set the “Acceptance Criteria” custom field to hidden in every field configuration assigned to project “NOVA”.

Hiding the field in the field configuration keeps the custom field defined globally while preventing it from appearing on issues in that project. This preserves all stored values in the database so historical values are retained and saved filters and reports do not break because the field still exists for queries. For the NOVA project users will see an empty value in lists and reports for that custom field because it is hidden by the project’s field configuration.

Delete the “Acceptance Criteria” custom field from the global custom fields list is incorrect because deleting a global custom field removes its stored values and can break saved filters and reports that reference that field.

Archive the “Acceptance Criteria” custom field for project “NOVA” is incorrect because archiving is not a standard per project operation that safely preserves values while hiding the field, and it would not meet the requirement to keep reports and filters working without updates.

Remove the “Acceptance Criteria” custom field from every screen used by project “NOVA” is incorrect because removing a field from screens is more error prone and does not reliably produce the required empty display in reports and filters for that project while also preserving behavior for saved queries.

Create a project specific field context for the “Acceptance Criteria” custom field that has no default values for project “NOVA” is incorrect because a field context controls options and defaults but does not clear or hide existing historical values in reports and it does not guarantee the field will appear empty for that project’s issues.

When a question asks to remove a field from a project but preserve historical values and saved queries choose a non destructive configuration change that hides the field rather than deleting it.

The correct answer is: Priya lacks the Assign Issues project permission and Marco is not configured as an assignable user in the project.

Priya lacks the Assign Issues project permission means she does not have the project permission that allows a user to set or change the assignee on an issue. If the permission scheme does not grant her Assign Issues then the assignee picker will not let her assign issues even though she can view them.

Marco is not configured as an assignable user in the project means Marco will not appear in the assignee selector for other users. Jira only lists users who are eligible to be assigned based on the project People settings and the roles or groups that are allowed to be assignees. If Marco is not in that assignable users list then Priya cannot pick him as an assignee.

A project issue security level hides Marco from the assignee picker is unlikely because issue security controls who can see an issue rather than who appears in the assignee selector. The scenario states both users can view the project issues so issue security would not explain the asymmetry.

Marco does not have the Assign Issues project permission is incorrect because Marco can assign an issue to Priya as described. That demonstrates Marco already has the Assign Issues permission so it cannot be the reason Priya cannot assign to him.

Priya is not a member of the Project Administrators group is not relevant because being a project administrator is not required to assign issues. What matters is the Assign Issues permission and whether the target user is configured as assignable in the project.

When troubleshooting assignment problems check the user’s effective project permissions and confirm whether the target is listed as an assignable user in the project People settings.

The correct option is Delete every team managed project from the site.

Jira Server and Data Center expect company managed project schemas and the Cloud site export for a Server restore will not produce a compatible backup if any team managed projects remain. Removing all team managed projects beforehand ensures the exported XML contains only supported project structures and reduces the risk of restore failures on Server.

Disable outgoing email for the site is incorrect because outgoing mail settings do not affect the structure or compatibility of the site backup and will not make team managed projects compatible with Server.

Disable all team managed projects so they can be re enabled after the export is incorrect because disabling projects does not change their type or make their data compatible with a Server restore. The projects would still be team managed and could cause incompatibility.

Convert team managed projects to company managed projects is incorrect in this context because conversion is not an automatic part of the site backup process and may require manual steps and validations. The exam answer expects removal of team managed projects to guarantee a compatible backup.

Remove only unneeded team managed projects from the site is incorrect because leaving any team managed projects on the site can still prevent a successful Server restore. The safe approach for a Server-compatible site backup is to delete every team managed project.

Focus on compatibility when you see Cloud to Server migration questions. Ask whether a feature is Cloud only and then choose the action that eliminates the incompatible elements before creating the backup.

The correct answers are resolutiondate >= startOfMonth(“+9d”), resolutiondate > startOfMonth(9d), and resolutiondate > startOfMonth(“+9d”).

The function startOfMonth with a “+9d” offset returns the instant at the start of the tenth day of the current month. Using resolutiondate >= startOfMonth(“+9d”) therefore includes that instant and any later timestamps and so returns issues resolved on or after the tenth.

Both resolutiondate > startOfMonth(9d) and resolutiondate > startOfMonth(“+9d”) refer to the same offset in practice and are accepted forms. Using the greater than operator with that offset will return issues resolved after the midnight instant that startOfMonth returns and that covers resolutions occurring on the tenth day in normal timestamp scenarios.

The expression resolutiondate > startOfMonth(“+8d”) is incorrect because startOfMonth with a “+8d” offset begins at the ninth day. That query would include issues resolved on the ninth day and so it is too early for the requirement.

The expression resolutiondate = startOfMonth(9d) is incorrect because the equals operator matches a single instant. That will rarely match real resolution timestamps and it does not mean on or after the tenth day.

The expression resolutiondate > startOfMonth(“9d”) is incorrect because the quoted form without a leading plus is not the intended offset syntax here. It will not behave as the valid startOfMonth(“+9d”) or unquoted startOfMonth(9d) forms and so it does not reliably return issues from the tenth day onward.

When selecting a day within the month use startOfMonth with a day offset and check whether you need to include the midnight instant by choosing >= or >.

The correct answer is Workflow conditions and Step properties.

Step properties are applied to a workflow status and they can control permissions and behavior while an issue is in that status. You can add a property that restricts the Edit operation so that only members of the project role Analysts can modify issues when they are in the Resolved status.

Workflow conditions are applied to transitions and they control who can see or execute a transition. You should add a condition on the Reopen transition that limits visibility to members of the help-desk-managers group so only those users see and can trigger that transition.

Workflow validators are not correct because validators check inputs when a transition is attempted and they do not control whether a transition is visible to or available for a particular user.

Workflow post functions are not correct because post functions run after a transition completes to update fields or trigger other actions and they do not restrict who can see or execute transitions or who can edit an issue while it stays in a status.

Workflow triggers are not correct because triggers automate transitions in response to external events and they do not provide per user or per group visibility controls for transitions or status level edit permissions.

When a question asks about who can see or use a transition think conditions. When it asks who can perform actions while an issue is in a status think step properties. Use the exact project role or group names when you configure the condition and the property.

The correct options are Add app-mobile-group to Project Role “Scrum Team” and Add app-mobile-group to Make bulk changes global permission.

Add app-mobile-group to Make bulk changes global permission gives the users the global ability to run bulk operations across the entire set of issues, which is required to process more than 100 issues in a single operation. Without the global bulk change permission the bulk change feature will not allow a user to operate on that large batch.

Add app-mobile-group to Project Role “Scrum Team” grants the group the project level permissions that the Scrum Team role has in the MOBILITY-APP project, and those project permissions include the ability to edit issues and change the reporter when the permission scheme is configured that way. Both the global bulk change grant and the project level edit/modify rights are required for this task.

Add app-mobile-group to Project Role “Analysts” is incorrect because the Analysts role does not provide the required project permissions in this project setup. Simply adding the group to Analysts will not allow the reporter to be changed if that role lacks edit or modify reporter rights.

Add the Project Role “Developers” to Make bulk changes global permission is incorrect because granting the global bulk change permission to a project role in that way is not the correct method to enable bulk operations for this group. The practical requirement is to give the app-mobile-group the global bulk change permission and place the group into the appropriate project role.

Add app-mobile-group to Project Role “Developers” is incorrect because being in the Developers role alone does not solve the global permission requirement for bulk operations and will not allow the large batch update unless the group also has the global bulk change permission.

Assign Make bulk changes global permission to the Project Role “Analysts” is incorrect because assigning the global permission to that role will not help unless the app-mobile-group is a member of that role and the role actually contains the necessary project edit rights. The scenario requires granting the global bulk change right directly to the group and placing the group into the project role that already has the needed project permissions.

When a question mentions bulk operations check both global and project permissions and remember that Make bulk changes is a global permission while changing the reporter requires project level edit or modify reporter rights.

The correct answer is It is not possible to meet all requirements.

The requirements mix per‑issue‑type visibility and requiredness with different option sets for the same custom field. Field configurations control whether a field is hidden or required and you can map different field configurations to different issue types via a field configuration scheme. Custom field contexts control which option values are available and they can be scoped by project and by issue type. These two mechanisms do not converge into a single, atomic per‑issue‑type rule for both visibility/requiredness and option sets for the same field in the way the team requires. To achieve everything as stated you would need separate custom fields or other add ons rather than only field configurations and contexts. For that reason the correct choice is It is not possible to meet all requirements.

Create three field configurations and add two custom field contexts is incorrect because simply adding two contexts does not resolve the conflict between per‑issue‑type option sets and per‑issue‑type visibility and requiredness for the same field. Contexts only control available options and field configurations control visibility and requiredness. Those controls do not fully satisfy the mixed requirements for all three issue types.

Create three field configurations and add three custom field contexts is incorrect for the same reason. Even three contexts would only change option lists but would not remove the need to duplicate the field if you want totally independent visibility and requiredness plus distinct option sets for the same custom field across issue types.

Create two field configurations and establish two custom field contexts is incorrect because two field configurations cannot express the three distinct visibility and requiredness states required by Epic Story and Task at the same time.

Use a single field configuration for the project is incorrect because a single field configuration cannot provide different hidden or required settings per issue type within the same project.

When you see a mix of different visibility/required rules and different option sets for the same custom field across issue types think about whether you need separate custom fields or an app. Field configurations control requiredness and visibility while custom field contexts control options. They are complementary but not a silver bullet for all per‑issue‑type combinations.

Asha will receive a notification email while Luis will not is correct.

The project notification scheme sends Issue Created notifications to the reporter and to the current assignee and outgoing mail is enabled and both users can view the issue so the scheme will attempt to send to both roles. Asha is the reporter and her personal “You’re the reporter” email setting is enabled so she will receive the email. Luis is the current assignee but his personal “You’re the assignee of the issue” setting is disabled so he will not receive the email even though assignees are included by the scheme.

Both Asha and Luis will receive notification emails is incorrect because Luis has his assignee notification preference turned off so he will not get the email.

Notification depends on project permissions assigned to the users is incorrect because both users can view the issue so permissions do not block the notification in this scenario and the deciding factor is the personal notification settings and the notification scheme.

Notification depends on the issue security level is incorrect because no security level is restricting visibility here and issue security only affects who can see the issue not the users personal email preferences for notifications.

Neither Asha nor Luis will receive a notification email is incorrect because the reporter is eligible and has reporter notifications enabled so Asha will receive the email.

Luis will receive a notification email while Asha will not is incorrect because Asha as the reporter has reporter notifications enabled and Luis as the assignee has assignee notifications disabled so the opposite is true.

When you see notification questions check the notification scheme and then verify each user personal email preference and issue visibility before deciding who actually gets the message.

All exam questions come from my Jira ACP-120 Udemy course and certificationexam.pro

The correct options are Project description, Project URL, and Project category.

Project description is metadata that describes the purpose and scope of the project and it can be edited by the project administrator without changing the project’s identity. Updating the description is optional and it is used for clarity and documentation rather than for system configuration.

Project URL is an optional field that lets teams link to external documentation or repositories. It is a convenience metadata field and it can be added or changed at any time without affecting project functionality.

Project category is a grouping attribute used to organize projects for reporting and navigation. Assigning or changing a category is optional and it is used for organization rather than core project behavior.

Project type is incorrect because the project type is a core setting chosen at creation and it often cannot be freely changed by a project admin or it may require higher administrative privileges. This makes it not an optional detail in the same sense as descriptive metadata.

Avatar is incorrect in this question because the avatar is a cosmetic element and may be managed separately from the project detail fields referenced here. The exam item treats avatar as not part of the optional project detail edits being asked about.

Project name is incorrect because the name is a primary identifier for the project and changing it has broader implications and may be restricted. The project name is not considered a mere optional metadata field in this context.

When you see choices about what is optional think about whether the field is metadata or a core identifier. Metadata like description, URL, and category are usually optional and editable by project admins.

The correct answers are Users require the “Move Issues” permission in the source project, Users need the “Create Issues” permission in the destination project, Users can change an issue type as part of the move operation and Users must have the “Edit Issues” permission in the origin project.

The move operation requires permissions in both projects so the Users require the “Move Issues” permission in the source project is needed to initiate the transfer and the Users need the “Create Issues” permission in the destination project is needed to create the issue in the target project. The system enforces both sides to prevent unauthorized removal or creation of issues.

The move process may need to update fields while transferring an issue which is why Users must have the “Edit Issues” permission in the origin project is also required. This permission allows the wizard to populate or change values that are necessary for the destination project and type.

The move wizard lets you change the issue type and map fields and workflows, so Users can change an issue type as part of the move operation is correct. The tool guides you through mapping required fields and statuses when the issue type or project changes.

Issues cannot be transferred from an enterprise-managed project to a team-managed project is incorrect because you can move issues between different project types. There are often extra mapping steps and limitations for fields, workflows and permissions when moving between company or enterprise managed projects and team managed projects, but the transfer itself is supported.

The move action only allows changing the issue’s project and nothing else is incorrect because the move workflow also lets you change the issue type and remap fields and statuses as required by the destination project.

Check the source and destination project permissions when you answer move questions and remember the move wizard can also change issue type and map required fields.

Modify query © to project = “CORE” and (fixVersion != 12 OR fixVersion is EMPTY) is correct.

The reason is that JQL uses != to filter out values that are present and different but it does not match issues that have no value set. Many issues in project CORE have no fixVersion at all so they are not counted by either project = “CORE” and fixVersion = 12 or project = “CORE” and fixVersion != 12. By adding OR fixVersion is EMPTY you include the issues that lack a fixVersion and the three queries will add up.

Use double quotes around the fixVersion value so it becomes fixVersion = “12” is incorrect because quoting the version name does not change how empty values are treated and it will not resolve the missing issues.

Trigger a background reindex of the Jira Cloud site is incorrect because reindexing will not change the semantics of JQL operators and Jira Cloud manages indexing differently from server installations. Reindexing would not make fixVersion != 12 match empty values.

Adjust the issue security scheme so the scrum master has access to every security level is incorrect because this problem is a JQL logic issue rather than a permissions issue. Changing security would only affect visibility for that user and would not cause the arithmetic mismatch caused by empty fixVersion values.

Announce downtime to users and perform a full reindex of the Jira Cloud instance is incorrect because Jira Cloud does not require or support that kind of manual full reindex with downtime and the discrepancy is due to how != treats empty fields rather than an indexing error.

When you see counts that do not add up remember that in JQL the != operator does not match empty or missing values so include is EMPTY when you need to capture issues with no value.

The correct answer is Change the system user default preference “Email format” to HTML and click Apply to enforce it for every user.

Change the system user default preference “Email format” to HTML and click Apply to enforce it for every user updates the global preference in the instance administration and applying the change enforces it for existing accounts. This ensures that notification messages are delivered as HTML with clickable links and inline images for all users without requiring each person to update their own settings.

Create a support ticket with the software vendor and request that they change every user to receive HTML email is incorrect because changing user preferences is an administrative action that you can perform within the application and does not require the vendor to edit every account.

Adjust the outgoing notification templates to always wrap messages in HTML is incorrect because templates control message content but they do not override a user preference that forces plain text rendering. If a user preference is set to plain text they may still receive plain text versions.

Send all users a step by step message explaining how to change their own notification format settings is incorrect because it is inefficient and unnecessary when there is a system default that an administrator can set and apply globally.

When many users see the same email formatting issue first check the system default preferences in the admin console and apply a global change before asking users to update their individual settings.

The correct options are reporter = Priya AND (summary ~ “\[urgent\]” OR summary ~ “\[critical\]”) and reporter = Priya AND (summary ~ “urgent” OR summary ~ “critical”).

The clause reporter = Priya AND (summary ~ “urgent” OR summary ~ “critical”) is correct because reporter = Priya limits results to issues Priya reported and the ~ operator performs a text search so the OR expression finds summaries that contain either word.

The variant reporter = Priya AND (summary ~ “\[urgent\]” OR summary ~ “\[critical\]”) is also correct when the summaries include literal square brackets such as [urgent] or [critical]. The backslashes escape the brackets so the search looks for those bracket characters rather than treating them as special syntax.

creator in (Priya) AND (summary ~ “urgent” OR summary ~ “critical”) is incorrect because the query filters by the creator field rather than the reporter field and the question asks for issues Priya reported.

reporter = Priya AND summary ~ (“urgent, critical”) is incorrect because putting both terms inside one quoted string with a comma will be treated as a single phrase search and not as two separate terms to match with OR.

reporter = Priya AND summary in (urgent, critical) is incorrect because the in operator is for list fields and not for free text fields like summary so this syntax will not match summary text.

reporter = Priya AND summary ~ “urgent” OR summary ~ “critical” is incorrect because the lack of parentheses changes the logic so the OR applies to the whole query and it will return issues with critical regardless of reporter. Parentheses are needed to ensure both terms are evaluated in the context of the reporter filter.

Pay attention to field names and operator precedence. Use reporter for who reported an issue and always group mixed AND and OR conditions with parentheses to avoid unintended results.

The correct options are Maya lacks the “Edit issues” project permission and Maya is not included in the other security levels that would allow changing the issue security.

Changing an issue’s security level is an edit to the issue. Even though Maya has the Set issue security, Create issue, and Browse Projects permissions, she still needs the “Edit issues” permission to modify issue fields. Without that permission she cannot change the Security Level field.

Issue security levels control who can be assigned and who can view issues at each level. If Maya is not a member of the target security level then she cannot set that level on the issue even if she has edit permissions and the Set issue security permission. Membership in the relevant security level is therefore required to change an issue to that level.

Maya does not have the “Transition issues” project permission is incorrect because that permission only controls workflow transitions and does not govern editing the Security Level field.

Maya is not the project administrator is incorrect because being a project administrator is not required to change an issue’s security. Individual permissions and security level membership determine the allowed actions.

Maya does not have the “Resolve issues” project permission is incorrect because resolving issues is a specific workflow action and it does not affect the ability to edit the Security Level.

Maya is not listed as the project lead is incorrect because being the project lead does not automatically grant or restrict the specific permissions needed to change an issue security level.

When troubleshooting check both the Edit issues permission and the user’s membership in the target security level. Having Set issue security alone does not let a user assign levels they are not included in.

The correct options are The custom field is set to hide when it has no value so it disappears on issues with empty values and “Project Goal” is configured as a hidden field in the project field configuration.

The custom field is set to hide when it has no value so it disappears on issues with empty values is correct because Jira can be configured to not render fields that have no stored value. When that setting is enabled the field will only appear on issues where someone has entered a value which makes it look like the field is present only on a subset of issues.

“Project Goal” is configured as a hidden field in the project field configuration is correct because project field configurations and screens can hide or show fields per project or per issue type and that can cause the field to be invisible on some issues even though it exists for the project.

The field scope context limits the custom field to specific issue types or projects is incorrect because field contexts control which projects and issue types a field applies to and would prevent the field from appearing entirely outside that context rather than selectively hiding it only when empty.

Issue level security is applied so some issues hide the field from certain users is incorrect because issue level security restricts access to whole issues and not to individual fields within an issue, so it would not selectively hide a field on some issues for the same user.

Maya lacks the Browse Projects permission for that project is incorrect because lacking Browse Projects would prevent Maya from seeing issues in that project at all, and it would not cause the field to appear on some issues and not others for the same user.

When a field appears on only some issues first check the hide when empty setting and then review the project field configuration and field contexts to narrow down the cause.

The correct options are Conditions, Post Functions and Transition Properties.

Conditions control whether a transition is available to a user and when it can be executed. You use Conditions to restrict the Done transition so that only members of the leadership group can see or trigger it and to prevent certain transitions when an issue is already in a particular status.

Post Functions run after a transition completes and they are the mechanism to make automatic changes to the issue. A Post Function on the Pending to Done transition can clear the required field value when the issue moves to Done.

Transition Properties let you adjust the behaviour of the transition and its screen and they can be used to limit or hide specific field options on that transition. You apply Transition Properties when you want to remove or prevent the Approval resolution option from appearing as part of the Done transition.

Status Properties are incorrect because they attach metadata to a status and do not control who sees or can execute a particular transition or perform automatic field updates.

Transition Screen is incorrect because the transition screen only defines which fields are shown for input and it does not by itself enforce who can perform the transition or automatically clear values after the transition.

Validators are incorrect for these requirements because validators only check inputs before a transition completes and they do not perform post-transition updates nor do they control transition visibility to specific user groups.

When mapping requirements to workflow elements think of who can see or run a transition as a job for visibility rules, think of automatic changes as a job for post actions, and think of which field choices appear on a transition as a job for transition properties.

Platform Administrator is correct because that role provides access to the billing and subscription management page in the admin portal.

Platform Administrator is an instance or site level role that includes permissions to view and manage invoices, subscriptions, and account wide billing settings. Users with this role can open the billing and subscription pages and make subscription changes and payment updates as needed.

Both Platform Administrator and Jira Administrator is incorrect because billing access is granted to the Platform Administrator only and not to the Jira Administrator, so naming both is not accurate.

Jira Administrator is incorrect because that role focuses on product and project configuration within Jira and does not include account wide billing or subscription management permissions.

Project Administrator is incorrect because project administrators are limited to individual project settings and they do not have rights to access billing or subscription pages at the platform level.

When you see role based questions check the scope of the role and whether it is account or project level to determine if it includes billing or subscription management.

Project roles cannot be selected as recipients in filter subscriptions is correct.

This is because filter subscriptions accept individual users or groups as recipients and do not allow project roles. Project roles are not addressable recipients so they will not appear in the recipients list even when they exist in the project.

She is not assigned to that project role is incorrect because who is assigned to a role does not change whether the subscription feature exposes roles as a recipient type. The absence is due to the feature not supporting project roles rather than role membership.

She lacks the Manage group filter subscriptions global permission is incorrect because that permission governs who can manage group subscriptions and does not alter which kinds of entities can be selected as recipients. Having or not having that permission would not make project roles selectable.

She does not have the required project permission to view the project is incorrect because missing project view permission affects access to project data but it does not cause project roles to appear in the recipients list. The underlying limitation is that filter subscriptions do not support selecting project roles.

When an option names a specific recipient type check the product documentation to see if the feature supports that entity such as users, groups, or project roles.

All exam questions come from my Jira ACP-120 Udemy course and certificationexam.pro

The correct option is Grant the group “Anyone” the Browse projects project permission.

Granting “Anyone” the Browse projects permission lets Jira consider external email addresses as recipients because those addresses are treated as anonymous users. When the project permits anonymous users to view issues the notification scheme can send outbound emails to addresses that are not Jira users.

Atlassian support must be contacted to activate outbound notifications to external accounts is incorrect because no support intervention is required for this capability. It is controlled by project permissions and notification scheme configuration rather than a manual change by Atlassian support.

Enable a global system setting named Send external notifications is incorrect because there is no such global setting in Jira Cloud. Email delivery to external recipients is governed by permissions and the notification recipients you configure in the scheme.

Configure the project to send outgoing mail from an email address on a verified domain is incorrect because verifying a sending domain is not a prerequisite for sending notifications to external addresses in Jira Cloud. Outgoing mail is handled by Jira Cloud and the key requirement for external recipients is that the project allows anonymous access via the “Anyone” Browse projects permission.

When a question mentions external or non user recipients think about anonymous access and the “Anyone” group. Check the project Browse projects permission first when troubleshooting notification delivery.

The correct option is Saved searches that reference the renamed issue type.

Saved searches that reference the renamed issue type are the most important place to check because saved filters and JQL often use the issue type display name. When the label is changed a query such as issuetype = “Old Name” will no longer match the same issues until the filter is updated, so administrators should review and update shared filters and user saved searches.

Dashboard gadgets that filter by the renamed issue type is not the best single answer because gadgets typically use saved filters or filter identifiers and will display whatever the underlying saved search returns. Fixing the saved search addresses affected gadgets.

Issue type screen schemes that reference the renamed issue type is incorrect because screen schemes map screens to issue type entities rather than to the display label. Renaming the label does not change the scheme mappings.

Global automation rules that refer to the issue type name is not the primary concern in this scenario because many automation rules reference the issue type by its identifier or adapt to label changes. The textual name in saved JQL is where users most often lose results.

Issue type schemes that include the renamed issue type is incorrect because schemes reference the type itself and are not broken by a display name change. The membership of a scheme does not depend on the label.

When a label or name is changed first search for the old name in shared filters and saved searches. Checking saved filters is usually the quickest way to find queries that must be updated.

The correct answers are Upload or replace the account profile photo, Change the managed account email address and Revoke API tokens issued by the account.

An organization administrator can Upload or replace the account profile photo because profile photos are directory profile attributes and administrators have permission to update user profile metadata on behalf of the organization.

An organization administrator can Change the managed account email address because administrators can rename accounts or update primary email addresses and aliases within the corporate directory to keep identities aligned with company policies.

An organization administrator can Revoke API tokens issued by the account because administrators can invalidate OAuth and session tokens to remove third party access or sign a user out of active sessions from the directory or security console.

Modify the account language setting is incorrect because language preferences are typically user-controlled settings rather than directory-managed attributes that an organization administrator changes.

Change the account default time zone is incorrect because the default time zone is usually a personal preference set by the user or by client application settings and not a directory attribute changed by the organization administrator.

Reset the managed account password is incorrect in this context because some managed accounts use external authentication or single sign on where the password is not stored in the corporate directory and cannot be reset by the organization administrator.

When you decide which actions an administrator can perform consider whether the item is a directory attribute or a user preference and whether authentication is managed in the directory or by an external identity provider. Focus on who owns the credential and who controls profile metadata.

The correct option is Release version 1.2.

Releasing the version triggers Jira to ask what should happen to unresolved issues and it gives you the option to move those unresolved issues into the newly created release 2.5 while keeping the 1.2 record intact for use in fields such as Affects Versions. Releasing marks the version as released but does not delete or archive it so it remains available for historical and selection purposes.

Merge release 1.2 into 2.5 is not a standard Jira operation and there is no single merge command that both preserves the original version as selectable and moves unresolved issues in the way the release workflow does.

Archive release 1.2 would hide the version from pickers and make it unavailable for selection in fields like Affects Versions so it does not meet the requirement to keep 1.2 available.

Delete version 1.2 would permanently remove the version from the project and from fields, so it cannot be used if you need 1.2 to remain available in Affects Versions.

When you see a question about moving unresolved issues during a version change remember that releasing a version in Jira presents a built in choice to move unresolved issues to another version while leaving the original version record in place.

A separate new issue will be created is correct because the client sent a fresh, separate email rather than replying to the original message and ticketing systems treat new, standalone messages as new requests.

Many ticketing systems rely on email headers such as Message ID and In Reply To or on threaded reply behavior to associate incoming mail with an existing ticket. When those headers are absent or when the mail is a new message the system cannot match it to the original ticket and so it creates a new issue.

A new subtask will be added to the existing ticket is incorrect because a separate incoming email will not automatically become a subtask unless explicit automation or manual action links it that way.

A new comment will be appended to the current issue is incorrect because appending a comment requires the incoming mail to be recognized as a reply to the ticket thread and that recognition depends on headers or reply routing not on a fresh standalone message.

Nothing will happen since the message content is identical is incorrect because ticket systems do not usually use identical message content to decide whether to ignore or merge messages and identical text will not prevent a new issue from being created.

A new issue will be created and linked to the existing ticket is incorrect because automatic linking of separate issues is not the default behavior. Some platforms can be configured to create links for related tickets but a plain separate email will normally only create a separate issue.

When a question says a user sent a fresh or separate email rather than a reply choose the option that creates a new ticket. Remember that threading depends on email headers and reply routing rather than the message text.

Maya will receive only issues assigned to her that had their resolution cleared.

The JQL Maya will receive only issues assigned to her that had their resolution cleared uses the function currentUser which resolves to the user who executes the query. When Maya created and scheduled the subscription the scheduled job runs as the subscription owner so currentUser resolves to Maya and the filter returns only issues assigned to her whose resolution was cleared.

Because the subscription was sent to the project-leads group both Maya and Leo may receive the email copy but the query results are evaluated as Maya so the list shows Maya’s cleared issues rather than Leo’s personal issues.

Leo will receive unresolved issues that are assigned to him is incorrect because the query uses currentUser and the scheduled subscription runs as Maya. The filter will not return Leo’s assigned issues just because he is in the recipient group.

The JQL is invalid so the filter cannot be saved is incorrect because the JQL syntax is valid. The “CHANGED TO” clause and the Unresolved value are supported so the filter can be created and scheduled.

Leo will receive unresolved issues that are assigned to Maya is incorrect as presented because the question asks which user the filter targets. While Leo may receive a copy of the subscription email the query itself is evaluated as Maya and therefore targets Maya not Leo.

Remember that currentUser() resolves to the user running the query and that scheduled filter subscriptions run as the subscription owner rather than each recipient.

The correct option is Add Maya to the “Administrators” project role.

This change gives Maya the project level Administer Projects permission that is required to update component leads. The Administer Projects permission is currently granted to the Administrators project role so adding Maya to Administrators will let her modify components and change the component lead.

Add Maya to the “Dev Team” project role is incorrect because the Dev Team role does not have the Administer Projects permission and therefore will not allow Maya to change the component lead.

Add Maya to the “atlassian-addons-project-access” project role is incorrect because that role is reserved for application access and does not confer project administrative permissions to human users.

Make Maya the Project lead is incorrect because the project lead setting does not automatically grant the Administer Projects permission and so alone it will not allow changing the component lead.

Add Maya to the “Product Manager” project role is incorrect because the Product Manager role in this scheme does not include the Administer Projects permission and so it will not permit Maya to update the component lead.

Check which permission controls the action in the question and then identify which project role has that permission. That will tell you which role the user needs to be added to.

The correct answers are Add a post function to the ‘Closed’ transition that sets the resolution and Use the bulk change feature with a Transition Issues operation to apply the new resolution.

Add a post function to the ‘Closed’ transition that sets the resolution is correct because a workflow post function sets the resolution at the moment an issue is transitioned into the Closed status and this ensures the resolution is applied consistently for all future transitions into Closed.

Use the bulk change feature with a Transition Issues operation to apply the new resolution is correct because existing issues that are already in the Closed status or that need the resolution set can be transitioned in bulk so the post function runs and the resolution field is populated for each issue.

Create an Automation rule to set the resolution for issues in the ‘Closed’ status is incorrect because automation can change fields in many cases but the reliable way to ensure the resolution is set upon transition is a workflow post function and the exam expects the workflow and bulk transition approach.

Run a bulk Edit operation to set the resolution field is incorrect because a bulk Edit does not run workflow post functions and may not correctly emulate a transition that sets resolution as part of the workflow logic. The bulk transition operation is the appropriate action to trigger the post function.

Request the Edit Issues project permission for the users who will update issues is incorrect because granting permissions does not change workflow behavior or automatically populate resolution for already closed issues. Permissions only control who can perform edits or transitions.

When you need a resolution to be set as part of moving issues into a status think about workflow post functions for future transitions and use the Transition Issues bulk operation to run that logic on existing issues.

The correct option is Features.

In a team-managed Scrum project the estimation method is controlled in the project settings under the Features section. You enable or configure the Estimation feature there and then choose whether to estimate using story points or time.

Board is incorrect because boards manage issue views and workflows for sprints and columns rather than the project level estimation configuration.

Issue types is incorrect because issue types define the kinds of issues and their fields and workflows and they do not set the global estimation method for the project.

Access is incorrect because access controls relate to permissions and who can view or change projects and they do not determine whether estimation uses time or story points.

Details is incorrect because that section holds basic project information and metadata and it does not include the estimation setting.

It is not possible to change the estimation setting for a team-managed Scrum project is incorrect because you can change the setting by opening Project settings and using the Features section to configure estimation.

When you need to change estimation settings open Project settings and then check the Features area for the Estimation toggle and options.

The correct options are Workflows and Field contexts.

You should review Workflows because issue types are mapped to workflows through workflow schemes and removing an issue type can change which workflow applies or leave transitions and status mappings inconsistent. Confirm that the issues you convert to the target type will follow a valid workflow and that no workflow scheme will be left with broken associations when Enhancement is removed.

You should also review Field contexts because custom field contexts can be scoped to specific issue types and projects and deleting an issue type may change which fields appear or orphan context settings. Make sure any contexts that apply only to Enhancement are updated to include Feature request or are migrated appropriately.

Screens is not the primary concern because screens and screen schemes are associated with field configurations and operations on issue types do not typically delete screens. You may still check screens if field contexts or field behaviours change, but screens themselves are not removed by deleting an issue type.

Notification scheme is incorrect because notification schemes apply to events and projects and they do not reference issue types directly in a way that would be broken by deleting an issue type. Converting issues will not remove notifications configured at the project or event level.

Permission scheme is not affected by removing an issue type because permissions are granted at the project level and not scoped to individual issue types. You do not need to change permission schemes when consolidating issue types.

Issue security levels is not a direct blocker because security levels are applied to issues and do not depend on the existence of a particular issue type. You should verify that no automation or filters rely on the old type name, but the security scheme itself will remain intact.

When in doubt, think about which settings are scoped to issue types and which are scoped to projects. Check workflows and field contexts first because they often reference issue types directly.

The correct statement is Linking issues requires a project permission called “Link Issues”.

This is true because creating or removing links between issues is governed by the project permission scheme and users must be granted the Link Issues permission for the particular project to perform linking actions.

Outward link description and inward link description must be different names is incorrect because link types define an outward and an inward description but they do not have to be different text and the system will accept identical or similar descriptions if desired.

Issue linking cannot be turned off from the global administration settings is incorrect because administrators can control linking behavior through permissions and global administration options or by changing the available link types, so it is not true that linking can never be disabled or restricted.

Only site administrators can define new types of issue links in the instance is incorrect because defining link types is a global administration capability and can be done by users with the appropriate Jira administration or system administration rights, not strictly by a site administrator role alone.

When a question mentions creating or modifying content check whether the action is controlled by a project permission or a global permission and choose the option that matches that level.

All exam questions come from my Jira ACP-120 Udemy course and certificationexam.pro

The correct answers are Any user with a Jira license can create and administer a team-managed project, Project administrators can define new roles within a team-managed project, and Team-managed projects allow adding custom quick filters on top of the board filter.

Any user with a Jira license can create and administer a team-managed project is correct because team-managed projects are designed for small autonomous teams and creation and administration are available to licensed users by default unless the site administrator has explicitly restricted project creation. This means the creator becomes the project admin and can manage the project without needing central administration permissions.

Project administrators can define new roles within a team-managed project is correct because team-managed projects provide project-scoped roles and permission controls that project admins can configure directly. The roles and permissions are managed inside the project so admins can adapt them to the team’s needs without changing global settings.

Team-managed projects allow adding custom quick filters on top of the board filter is correct because boards in team-managed projects support quick filters that let the team add simple JQL or field based filters on top of the board filter to focus the view during planning and standups.

A team can run parallel sprints that span several team-managed projects is incorrect because team-managed boards and sprints are scoped to a single project or a single board that is tied to that project. They do not support cross project sprints in the way company managed projects or cross project boards might.

Project settings for a team-managed project can be shared with other projects is incorrect because team-managed projects are intentionally independent. Their configurations are local to the project and cannot be shared or inherited by other projects in the same way that company managed schemes can.

You can make a team-managed project publicly readable to anonymous visitors is incorrect because team-managed projects do not support exposing the project to anonymous public access through project level settings. Public or anonymous access is controlled at the site or global level and is not a standard capability of team-managed project settings.

When a question contrasts project scope think about whether the project is team-managed or company managed. Team-managed projects are self contained and give broad control to the project creator and admins.

The correct answer is The system setting for issue linking was switched off globally.

If the system setting for issue linking is turned off at the system level then users cannot create issue links anywhere in the instance and automation rules that add links will fail because the underlying linking capability is disabled. This is a global override that takes precedence over project permissions and app behaviour so it explains why both team managed and company managed projects are affected at the same time.

A marketplace app or automation script interfered with the linking functionality is unlikely because a third party app or script would rarely block core linking for every project and also block Jira native automation. Apps can cause problems but they do not typically flip the central system setting that controls linking.

The Link issues project permission was removed from every project permission scheme is unlikely because team managed projects do not use shared permission schemes and they would not be impacted by removing that permission from schemes. Also removing that permission from schemes would not usually break automation across both types of projects at once in this way.

All link types were renamed in the instance is incorrect because renaming link types only changes labels and it does not prevent creating links. Automation failing and inability to add any links is not explained by renamed link types.

When you see a widespread problem that affects multiple project types first check the global system settings for that feature before investigating apps or permission schemes.

The correct option is Project permission.

Maya needs the specific project permission that allows issue linking to be granted to her account or group. In Jira this is the Link Issues permission which is assigned in a project’s permission settings so an administrator should add her user or role to the permission that grants link rights in the relevant project or projects.

Issue security scheme is incorrect because issue security controls who can view or access particular issues and not whether a user can create links between issues.

Permission scheme is incorrect as the best answer because the request should be for the specific project permission that permits linking rather than a vague change to the scheme itself.

Issue linking global setting is incorrect because there is no single global toggle that grants users the ability to link issues in standard Jira. Linking is governed by project permissions.

When a user can see issues but cannot take an action check the specific project permissions such as Link Issues before changing visibility or global settings.

The correct options are The subscription owner enabled sending notifications even when the query returns no matches, The JQL currently yields no results at the time the subscription job ran and All of the issues that would match were resolved before the scheduled run.

The subscription owner enabled sending notifications even when the query returns no matches is valid because Jira filter subscriptions include a setting that lets the owner choose to send the email even if the filter returns no issues. When that option is set the scheduled job will send an empty notification rather than skip the email.

The JQL currently yields no results at the time the subscription job ran is valid because subscriptions run on a schedule and they evaluate the query at the run time. A filter that returns results when you run it interactively may return nothing at the scheduled moment and that will produce an empty notification if the subscription still sends mail.

All of the issues that would match were resolved before the scheduled run is valid because your JQL includes resolution is EMPTY so resolved issues stop matching. If the issues were resolved prior to the subscription execution the scheduled evaluation would find no matches and an empty notification can be sent.

The notification schedule is restricted to business hours only is incorrect because Jira subscriptions do not have a built in business hours restriction by default. The schedule is set to specific times and recurrence and that is separate from whether the filter returns results.

The project key must match capitalization exactly in JQL is incorrect because the team can view matching issues in the Issue Navigator, which shows the JQL is functioning. The described symptom is about scheduled runs and results at run time rather than a simple capitalization mismatch.

The recipients lack the Browse Projects permission to view issues is incorrect because recipients who truly lacked Browse Projects would not be able to see the issues in the Issue Navigator. The question states the team can view matching issues so permission absence is not the cause.

When you see an empty subscription email first check whether the subscription is set to send when no results and then check the filter results at the exact scheduled time to see if issues were resolved or the query returned nothing.

The correct answer is Acme Alpha needs a new custom field shown on the view issue screen.

This option is correct because adding a new custom field and making it visible on the view issue screen often requires creating or assigning a screen that contains that field and then mapping that screen via issue type screen schemes. Creating a distinct issue type allows you to attach a specific screen scheme so the new custom field appears only for the intended issues in Acme Alpha.

Acme Alpha must use an entirely different workflow for every issue type is incorrect because you can map different workflows to existing issue types using workflow schemes without creating new issue types for every change.

Acme Alpha requires a unique field configuration scheme applied only to that project is incorrect because field configuration schemes can be created and applied at the project level and you do not need a new issue type simply to use a different field configuration for a project.

Acme Alpha must have a different option set for a select custom field is incorrect because select field options can be scoped with field contexts so you can provide project or issue type specific option sets without creating a new issue type solely for that purpose.

When you evaluate whether to create a new issue type think about whether a different screen, field context, or workflow mapping can solve the need before adding types.