ACP-120 Jira Certification Exam Sample Questions

Lina must remove a managed user account for Carlos from her organization’s cloud tenancy. Which of the following statements are false? (Choose 2)

• ❏ A. Carlos’s account can be restored at any later time if required

• ❏ B. Content created by Carlos will remain and will not be removed

• ❏ C. Other users will still see Carlos’s username after his account has been deleted

• ❏ D. All personal information in Carlos’s managed account will be erased

• ❏ E. Carlos’s deletion can be undone during a 30 day grace period

Maya at Altair Systems is configuring an issue collector for a new project and she plans to include Summary Description Priority Due Date Components Attachments and Environment fields on the form. Which of these fields cannot be added to an issue collector?

• ❏ A. Components

• ❏ B. Description

• ❏ C. Attachments

• ❏ D. Due Date

• ❏ E. Priority

• ❏ F. Environment

• ❏ G. Summary

The custom field “Team Seniority” is shared across all company-managed projects at Solveta and Laura oversees one company-managed project that needs a unique set of choices for that field. Which configuration must she modify?

• ❏ A. Issue layout

• ❏ B. Permission scheme

• ❏ C. Custom field context

• ❏ D. Screen scheme

Return issues assigned to Sam or Maya that were created on or after Monday of the current week?

• ❏ A. assignee = Sam OR assignee = Maya AND created gt; startOfWeek(“Monday”)

• ❏ B. (assignee in (Sam, Maya)) AND created gt;= startOfWeek(“Monday”)

• ❏ C. assignee in (Sam, Maya) AND created gt; startOfWeek(“+1d”)

A few days ago Leah attached two important PDF files to ticket INC-789 that she is handling at Finora Labs and suddenly the attached files disappeared from INC-789 and Leah cannot attach them again, what are two plausible causes? (Choose 2)

• ❏ A. Site attachment storage quota has been exceeded

• ❏ B. Attachments have been disabled across the Jira site

• ❏ C. “Create attachments” project permission was revoked for Leah

• ❏ D. “Browse projects” project permission was revoked for Leah

• ❏ E. “Edit issues” project permission was revoked for Leah

Sophia manages the marketing operations team at HarborBank and she built a saved filter with the JQL Manager in membersOf(“marc-managers”) and project = MARCOM. She then shared the filter with every role in the MARCOM project and added a subscription that sends the filter results to the group “marc-escalate” whose members can view all MARCOM issues. Which issues will the subscription include and send to the “marc-escalate” group?

• ❏ A. Issues in project MARCOM where the group “marc-escalate” is entered in the Manager custom field

• ❏ B. Issues in project MARCOM where the user shown in the Manager custom field is a member of the “marc-managers” group

• ❏ C. Issues in project MARCOM where the group “marc-managers” is stored in the Manager custom field

• ❏ D. Issues in project MARCOM where Sophia is listed as the Manager in the custom field

Marta cannot see the Pending Review transition on the Issue details screen while her teammates can. What are the possible reasons? (Choose 3)

• ❏ A. She lacks Browse issues project permission

• ❏ B. She is missing the Transition issues project permission

• ❏ C. A workflow validator requires changes

• ❏ D. A workflow condition is blocking the transition for her

• ❏ E. She is not a member of the group or project role that has the permission

Ravi needs to set up a Jira project at EmberSoft to consolidate incident tickets and development work coming from the SRE group and he needs to decide which project type and template to use. His requirements include the ability to prioritize tasks each day on a Kanban board and the ability to work in timeboxed cycles with variable length and he needs project administrators to be able to clear the board’s last column on demand. The project must meet these needs immediately after creation without enabling extra features. Which project type and template should he create?

• ❏ A. Company-managed project with Bug tracking template

• ❏ B. Team-managed project with Bug tracking template

• ❏ C. Company-managed project with Kanban template

• ❏ D. Team-managed project with Kanban template

• ❏ E. Company-managed project with Scrum template

Ava is the team facilitator and the board administrator for a company managed Kanban board in the project “NOVA”. She notices issues stacking in the rightmost column and wants to release a new version. The project permission scheme shows the project permission “Administer projects” granted to the group atlassian_addons_project_access. The permissions Browse projects Edit issues and Resolve issues are granted to Any logged in user. No project roles are assigned in the “NOVA” project. Which statement is definitely true?

• ❏ A. Being the board administrator is sufficient to release a version from the Kanban board

• ❏ B. She must be assigned as the project lead to perform a release from the Kanban board

• ❏ C. She will be able to release a new version from the Kanban board without additional permissions

• ❏ D. She must have the “Administer projects” project permission to release a new project version from the Kanban board

Which schemes in Jira Cloud are not associated with specific issue types? (Choose 3)

• ❏ A. Workflow schemes

• ❏ B. Notification schemes

• ❏ C. Issue security schemes

• ❏ D. Permission schemes

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

Maya manages two Jira Cloud instances for a regional design agency and she needs to combine them into a single Jira Cloud instance. Which statement about Maya’s requirement is correct?

• ❏ A. Create site backups for both instances and restore them into a new Cloud instance

• ❏ B. You cannot merge two Jira Cloud instances into one using only site backup files

• ❏ C. Create a backup of one instance and restore it over the other instance

• ❏ D. Use the Jira Cloud Migration Assistant or perform a cloud to cloud migration

• ❏ E. Export issues from one instance and import them into the other using CSV

Amelia created a team managed Kanban project named FLX and she set it to limited access. She added users and she accidentally restricted the Story issue type so only the project role Administrator could view it. No other project configuration was changed and after a few days people reported they could not see Stories they created. Amelia then updated the Story issue type restriction and added the project role Viewer. Which statement is true?

• ❏ A. Users who hold the project role ‘Member’ in the FLX project will be able to access all stories

• ❏ B. Users who hold the project role ‘Viewer’ in the FLX project will be able to access all stories

• ❏ C. Users who hold the project role ‘Member’ in the FLX project will be able to access only stories they create after Amelia updated the restriction

• ❏ D. Members assigned the project role ‘Viewer’ in the FLX project will have access only to stories created after Amelia changed the restriction

Which statements accurately describe how issue statuses behave on a team-managed board in a scrumtuous.com project? (Choose 2)

• ❏ A. After you add a status in the workflow you must manually place it on the board or it will not be visible

• ❏ B. Adding a new column with a unique name on the board automatically creates a corresponding status

• ❏ C. Only a Jira global administrator can add new statuses for a team-managed project

• ❏ D. Creating a new status in the project workflow will automatically add a new column to the board

Maya set up a subscription from one of her saved filters in the issue tracker and she received notification emails from that subscription last week but she does not receive any emails from it today. Which of the following would not explain why she stopped receiving the notifications?

• ❏ A. The saved filter yields no results

• ❏ B. Someone removed Maya from a user group

• ❏ C. Project permissions were changed

• ❏ D. All of the listed reasons could cause the problem

• ❏ E. Someone removed Maya from a project role

A product team at Meridian Labs manages a company project and they want an automation so that when a new issue is created and it is linked to a parent epic the new issue receives the parent epic’s due date?

• ❏ A. Trigger When an issue is created Condition Issue type equals Epic Action Edit issue fields “Due Date”

• ❏ B. Trigger When an issue is created and associated to an epic Action Edit issue fields “Due Date”

• ❏ C. Trigger When an issue is created Branch rule For parent epic Action Edit issue fields “Due Date”

• ❏ D. Trigger When an issue is created Condition If an epic exists Action Edit issue fields “Due Date”

When global permissions remain at their default values, which project configuration tasks can a project administrator not perform? (Choose 2)

• ❏ A. Create components

• ❏ B. Show due date on every screen and in all issue layouts

• ❏ C. Create a Kanban board that shows only stories

• ❏ D. Modify issue layout to hide fields when empty

• ❏ E. Grant project lead the Delete issues permission

‘platform-admins’ group members Alex Maya ‘administrators’ group members Alex Leo Which issues are returned by this JQL? creator in membersOf(“platform-admins”) AND creator not in membersOf(“administrators”) OR creator=currentUser()?

• ❏ A. Issues created by Alex and the current user

• ❏ B. Issues authored by Maya and the currently signed in user

• ❏ C. Issues created only by Maya

• ❏ D. Issues reported by the currently signed in user

• ❏ E. Issues created by Alex Maya and the current user

• ❏ F. Issues where the creator is any member of platform-admins

Marco is growing his localization group across markets that use different languages and he wants to confirm which statements about translation in a company-managed project are incorrect? (Choose 3)

• ❏ A. Users can translate project components

• ❏ B. Users can translate the locked custom field

• ❏ C. Users are unable to translate the Resolution field

• ❏ D. Users can translate issue types

• ❏ E. Users can translate priorities

• ❏ F. Users can translate statuses

Maya at Northbridge Solutions set up a new inbound mail processor and it worked at first but now no customer emails create issues including messages from previous customers. What is causing this behavior? (Choose 3)

• ❏ A. The mailbox credentials expired

• ❏ B. The mail processor was deleted

• ❏ C. An issue type was removed from the mail processor configuration

• ❏ D. The mailbox location was modified and it is now empty

• ❏ E. The default reporter lost the Create Issues project permission

• ❏ F. An issue security level is missing from the project

A site administrator named Lucas plans to remove a Jira group and needs to discover where that group might be referenced across the instance. Where should Lucas look first? (Choose 2)

• ❏ A. Project roles

• ❏ B. System default dashboard

• ❏ C. Saved filters

• ❏ D. Issue type schemes

• ❏ E. Workflow conditions

The correct answers are Carlos’s account can be restored at any later time if required and Other users will still see Carlos’s username after his account has been deleted.

Carlos’s account can be restored at any later time if required is false because managed user deletions are not indefinitely reversible. Restores are generally limited to a defined retention window and after that window the account is permanently removed so it cannot be recovered at any later time.

Other users will still see Carlos’s username after his account has been deleted is false because deleting a managed account removes the user entry from the directory and public listings. Other users will not continue to see the deleted account’s username as an active directory identity.

Content created by Carlos will remain and will not be removed is not a correct choice because that statement is true in this context. Files, emails, and other organizational content are typically retained or can be reassigned rather than being automatically deleted with the user account.

All personal information in Carlos’s managed account will be erased is not a correct choice because that statement is true here. Account deletion processes commonly remove or anonymize personal profile data to meet privacy and compliance requirements.

Carlos’s deletion can be undone during a 30 day grace period is not a correct choice because that statement is true and therefore not one of the false statements. Many directory services implement a soft delete with a limited grace period during which the deletion can be reversed.

Read each statement carefully and watch for absolute phrases like any later time or exact time windows. Compare those phrases to known retention or soft delete windows to decide if a statement is false.

The correct option is Due Date.

Due Date cannot be added to an issue collector because collectors are designed to capture a limited set of basic issue fields from an embedded form and scheduling fields such as a due date are managed in Jira after issue creation or through workflows and permissions rather than through the collector configuration.

Components is incorrect because components can be included or set as defaults in an issue collector and they are part of the basic metadata that collectors support.

Description is incorrect because the whole point of an issue collector is to capture the issue description or details from the reporter via the embedded form.

Attachments is incorrect because collectors can accept file uploads when the collector is configured to allow attachments and the project permits them.

Priority is incorrect because priority can be exposed on the collector so reporters can choose the issue priority during submission.

Environment is incorrect because the environment field can be included to capture information about the user’s environment or system when the issue is reported.

Summary is incorrect because a short summary is a standard required field on collector forms and it is normally included in the embedded form.

When you see a question about issue collectors remember that they are for simple data capture and that scheduling or workflow controlled fields like the due date are commonly not available in the collector form.

Custom field context is correct because it allows different sets of choices for the same custom field to be scoped to specific projects and issue types.

Custom field contexts let an administrator define separate option lists and apply them to particular projects or issue types. Laura can create a context that is limited to her company-managed project so that the shared “Team Seniority” field has a unique set of choices there while other projects keep the original options.

Issue layout is wrong because it controls how fields are displayed on the issue view and it does not change the selectable options for a custom field.

Permission scheme is wrong because it governs user rights like who can create edit or transition issues and it has no effect on the option sets of a custom field.

Screen scheme is wrong because it assigns which screens appear on create edit and view operations and it does not provide per-project option lists for a custom field.

When a question is about different choice lists for the same field across projects think of custom field contexts first and look for keywords like choices or options in the scenario.

The correct option is (assignee in (Sam, Maya)) AND created gt;= startOfWeek(“Monday”).

This query explicitly groups the two assignees and applies the date filter to the combined set. The use of created gt;= startOfWeek(“Monday”) makes the cutoff inclusive so issues created on Monday of the current week are returned as well as those created afterwards.

assignee = Sam OR assignee = Maya AND created gt; startOfWeek(“Monday”) is incorrect because without parentheses the AND binds more tightly so the expression would return all of Sam’s issues regardless of creation date and it also uses gt; which would exclude issues created exactly at the Monday boundary.

assignee in (Sam, Maya) AND created gt; startOfWeek(“+1d”) is incorrect because startOfWeek(“+1d”) advances the cutoff and the gt; operator excludes the Monday start so issues created on Monday would be omitted.

When you see mixed AND and OR use explicit parentheses and check whether the date comparison should be inclusive ( gt;=) or exclusive ( gt;).

The correct options are “Create attachments” project permission was revoked for Leah and “Edit issues” project permission was revoked for Leah.

“Create attachments” project permission was revoked for Leah is correct because that specific project permission controls whether a user can add files to an issue. If Leah lost that permission she would no longer see the add attachment controls and she would be unable to reattach the PDFs.

“Edit issues” project permission was revoked for Leah is correct because attaching files typically requires the ability to modify the issue. Without edit rights Leah cannot change the issue to add attachments and some attachment actions may be hidden from her.

Site attachment storage quota has been exceeded is unlikely because a storage quota normally prevents new uploads but it does not usually make existing attachments vanish from an issue.

Attachments have been disabled across the Jira site is unlikely because disabling attachments is a global admin action that would affect all users. That is less likely than a project permission change and would require an administrator to toggle the site setting.

“Browse projects” project permission was revoked for Leah is not the best explanation because losing browse permission would block Leah from seeing the project or issue at all rather than only removing her ability to add or manage attachments.

When an issue shows missing attachments first check project permissions such as create attachments and edit issues. If the problem affects all users then check global or site attachment settings and storage limits.

The correct option is Issues in project MARCOM where the user shown in the Manager custom field is a member of the “marc-managers” group.

The saved filter uses the JQL function membersOf(“marc-managers”) together with project = MARCOM so it matches issues in MARCOM where the Manager custom field contains a user who belongs to the marc-managers group. The subscription will evaluate that filter and send the resulting issue list to the marc-escalate group. Because the marc-escalate group can view all MARCOM issues they will receive the matched issues.

Issues in project MARCOM where the group “marc-escalate” is entered in the Manager custom field is incorrect because the filter is checking for users who are members of marc-managers and not for a group value stored in the Manager field. The recipient group being marc-escalate is about who receives the emails and does not change what the JQL returns.

Issues in project MARCOM where the group “marc-managers” is stored in the Manager custom field is incorrect because the Manager custom field is a user picker and does not store groups. The membersOf function tests whether the user in that field belongs to the named group rather than looking for a group value inside the field.

Issues in project MARCOM where Sophia is listed as the Manager in the custom field is incorrect because the filter does not target a specific person. It selects any issue where the Manager field contains a user who is a member of marc-managers, so Sophia would only be included if she herself is in that group.

Read the JQL carefully and focus on whether the query checks a user’s group membership or the literal value stored in a custom field. Also confirm that recipients have permission to view the issues because subscriptions only send issues the recipients can see.

The correct options are She is missing the Transition issues project permission, A workflow condition is blocking the transition for her, and She is not a member of the group or project role that has the permission.

She is missing the Transition issues project permission is correct because executing or seeing certain transitions can be controlled by specific project permissions and without that permission the user interface will not present the transition to that user even though others can see it.

A workflow condition is blocking the transition for her is correct because workflow conditions are evaluated for the current user and can hide or prevent a transition from appearing when the condition is not satisfied for that user while it still appears for teammates who meet the condition.

She is not a member of the group or project role that has the permission is correct because project permissions are commonly granted to groups or project roles and if she is not in the allowed group or role she will not receive the permission needed to view or execute the transition.

She lacks Browse issues project permission is incorrect because lacking the browse projects permission would normally prevent the user from opening or viewing the issue details at all rather than only hiding a single transition.

A workflow validator requires changes is incorrect because validators run when a transition is executed and they can stop the transition from completing but they do not typically hide the transition from the issue view before the user attempts it.

When a transition is not visible check transition permissions first then check workflow conditions and finally confirm group or role membership.

Team-managed project with Kanban template is correct because it provides a ready to use Kanban board for daily prioritization and it includes the lightweight board controls that project administrators can use immediately to manage and clear columns while also supporting timeboxed work in flexible cycles without turning on extra features.

The team managed Kanban template gives teams a simple, directly editable board that lets them rank and prioritize work each day on a Kanban board. Project administrators in a team managed project have the in-product controls to configure columns and perform bulk moves or clear the board end column without needing global administration or extra configuration steps. The template is designed to be usable immediately after creation so the SRE and development workflows can start straight away.

Company-managed project with Bug tracking template is wrong because company managed projects use shared schemes and more centralized administration which can require extra configuration and permissions before board and column operations are available to project administrators.

Team-managed project with Bug tracking template is wrong because the bug tracking template does not provide the Kanban workflow and board experience required for daily prioritization on a Kanban board.

Company-managed project with Kanban template is wrong because a company managed Kanban project brings centralized schemes and admin dependencies that can prevent immediate, per project administrator control of board behaviors and clearing the final column without additional setup.

Company-managed project with Scrum template is wrong because the Scrum template focuses on fixed sprint cadence rather than an immediate Kanban style daily prioritization, and the company managed model adds configuration that can delay meeting the requirement right after creation.

When a question emphasizes immediate, per project admin control and simple board prioritization pick a team-managed Kanban project since it gives direct board controls and usable Kanban features without extra configuration.

She must have the “Administer projects” project permission to release a new project version from the Kanban board is the correct statement.

Releasing and managing versions is a project administration task and it is controlled by the project permission “Administer projects”. Without that permission a user cannot create edit or release versions from the project or from the board interface. The scheme shows that “Administer projects” is granted only to the group atlassian_addons_project_access so being a board facilitator does not automatically give the needed project level rights.

Being the board administrator is sufficient to release a version from the Kanban board is incorrect because board administration controls board configuration filters and swimlanes and it does not grant project level version management rights.

She must be assigned as the project lead to perform a release from the Kanban board is incorrect because the project lead role is not required to manage versions and it does not by itself provide the “Administer projects” permission unless the permission scheme explicitly assigns that permission to the lead.

She will be able to release a new version from the Kanban board without additional permissions is incorrect because the permissions Browse projects Edit issues and Resolve issues do not include version management actions. The user needs the “Administer projects” permission to perform a release.

When a task involves creating or releasing versions check which project permission controls that action and verify whether the user is in a group or role that grants Administer projects.

The correct options are Notification schemes, Issue security schemes, and Permission schemes.

Notification schemes control who receives email notifications for project events and they are applied at the project level through a scheme. They are not mapped to individual issue types so they do not depend on which issue type is used.

Issue security schemes define security levels that control who can see particular issues and they are assigned to projects via a scheme. The security levels apply to issues but the scheme itself is not tied to specific issue types.

Permission schemes determine what users can do within a project and they are granted at the project level by applying a scheme. Permissions are not configured per issue type so the permission scheme is not tied to issue types.

Workflow schemes are incorrect because they map workflows to specific issue types. A workflow scheme explicitly assigns a workflow to one or more issue types, so this scheme type is tied to issue types.

When you read questions about schemes think about whether the scheme applies at the project level or whether it maps directly to issue types. Schemes that control notifications, security visibility, or permissions are usually project level.

You cannot merge two Jira Cloud instances into one using only site backup files.

Jira Cloud site backups are designed for single site restore workflows and a site restore replaces the target site rather than merging with it. Restoring a backup will recreate the backed up site’s data and configuration and it will not combine two separate backup sets into one unified site.

To combine content from two cloud sites you must use targeted migration methods or work with Atlassian support to plan a merge. Common approaches include selective exports and imports or vendor supported cloud to cloud migrations, but those are not achieved by applying multiple site backup files to a single instance.

Create site backups for both instances and restore them into a new Cloud instance is incorrect because you cannot apply two different site backup files into the same target site. Restoring one backup will define the site state and a second restore will overwrite that state rather than merge it.

Create a backup of one instance and restore it over the other instance is incorrect because restoring one backup over another would replace the destination site and destroy the original data on that site instead of combining content.

Use the Jira Cloud Migration Assistant or perform a cloud to cloud migration is incorrect in this question context because the Jira Cloud Migration Assistant is primarily intended for Server or Data Center to Cloud migrations and there is no simple self service tool that automatically merges two independent cloud sites. Cloud to cloud moves often require planning and support from Atlassian.

Export issues from one instance and import them into the other using CSV is incorrect as a complete solution because CSV import only moves selected issue data and it will not preserve many elements such as full history, attachments, user mappings, permissions and some configuration details. CSV can help migrate issues but it does not perform a full site merge.

When you see questions about merging cloud sites remember that site backups are single restore operations. Think about what a restore does and then eliminate answers that imply combining multiple backup files into one site.

Members assigned the project role ‘Viewer’ in the FLX project will have access only to stories created after Amelia changed the restriction.

The issue type visibility restriction that Amelia changed in the team managed project takes effect for issues created or edited after the change. When she added the project role Viewer to the Story restriction, users with that role gained visibility for newly created or updated Story issues going forward. Existing Story issues that were created while the restriction allowed only Administrators remain restricted until those issues are changed.

Users who hold the project role ‘Member’ in the FLX project will be able to access all stories is incorrect because Members were not granted visibility by the change and restrictions do not automatically retroactively open previously restricted issues.

Users who hold the project role ‘Viewer’ in the FLX project will be able to access all stories is incorrect because adding Viewer to the restriction does not give access to Story issues created before the change. Viewers can see Stories created or updated after the restriction was modified.

Users who hold the project role ‘Member’ in the FLX project will be able to access only stories they create after Amelia updated the restriction is incorrect because this scenario did not grant Members any new visibility. Whether a creator can see an issue depends on the active visibility rules when the issue is created and not on who created it if the role is not permitted.

Remember that issue type visibility changes in team managed projects generally apply going forward and do not retroactively change who can view issues that were already created.

Adding a new column with a unique name on the board automatically creates a corresponding status and Creating a new status in the project workflow will automatically add a new column to the board are correct.

Team managed projects keep board columns and workflow statuses synchronized so adding a column on the board will create the matching status automatically and creating a status in the workflow will add a corresponding column. This behavior lets project admins manage the board and workflow from either view and the platform handles the mapping for you.

After you add a status in the workflow you must manually place it on the board or it will not be visible is incorrect because a new status in a team managed project is reflected on the board automatically and you do not need to place it manually.

Only a Jira global administrator can add new statuses for a team-managed project is incorrect because team managed project administrators can add and manage statuses for their project and a global administrator is not required for those project scoped statuses.

When a question contrasts team managed and company managed behavior remember that team managed projects sync board columns and statuses automatically and you should look for answers that state this automatic two way mapping.

The correct answer is All of the listed reasons could cause the problem.

This choice is correct because each of the other options describes a plausible reason why Maya might stop receiving subscription emails. Subscriptions deliver the results of a saved filter to recipients on a schedule and if the filter yields nothing to send or if Maya loses the access that makes her a recipient then the emails can stop.

The saved filter yields no results is not a valid exclusion because if a saved filter returns no issues there is often nothing for the subscription to include and many systems will not send an empty notification email.

Someone removed Maya from a user group is not a valid exclusion because if the subscription targets that group then removing her from the group will remove her from the recipient list and she will no longer get the emails.

Project permissions were changed is not a valid exclusion because changes to project or project browsing permissions can prevent a user from seeing issues or receiving notifications tied to that project, so notifications can stop when permissions are reduced.

Someone removed Maya from a project role is not a valid exclusion because project roles are often used to determine notification recipients and access, and removing her from a role can also stop both visibility and email delivery.

When a question asks which option would not explain a problem check whether each listed cause could independently produce the symptom and pick All of the listed reasons only if every item is plausible.

The correct option is Trigger When an issue is created Condition If an epic exists Action Edit issue fields “Due Date”.

This rule uses the issue created trigger so it runs when a new issue is added. The condition ensures the rule only proceeds when a parent epic exists and the edit issue fields action can copy the epic’s due date into the newly created issue by using automation smart values when setting the Due Date field.

Trigger When an issue is created Condition Issue type equals Epic Action Edit issue fields “Due Date” is incorrect because it only fires when the created issue is an epic. The requirement is to set the due date on a new issue that is linked to an existing epic and not to act only when the created issue itself is an epic.

Trigger When an issue is created and associated to an epic Action Edit issue fields “Due Date” is incorrect because there is no standard single trigger named associated to an epic and because the safe pattern is to trigger on creation and then verify a parent epic exists. Explicitly checking for the epic prevents the rule from running for unrelated issues.

Trigger When an issue is created Branch rule For parent epic Action Edit issue fields “Due Date” is incorrect because branching into the parent epic changes the rule context to the epic. That pattern would target the epic unless you explicitly reference the newly created issue with smart values, so it is not the simplest or most direct way to copy the epic’s due date into the new issue.

When a question asks about copying a parent field on creation look for a trigger plus a condition that confirms the parent and an action that uses smart values. Use an If an epic exists check to avoid running the rule for issues with no parent.

The correct answers are Show due date on every screen and in all issue layouts and Grant project lead the Delete issues permission.

Show due date on every screen and in all issue layouts is not something a project administrator can enforce when global permissions remain at their defaults because modifying screens and global issue layout schemes is handled by Jira administrators. Those configuration areas apply across projects and are controlled at the global administration level rather than by a single project admin.

Grant project lead the Delete issues permission is also not possible for a project administrator when global permissions are unchanged because the Delete Issues right is assigned through permission schemes. Editing permission schemes requires Jira administrator privileges so a project admin cannot grant that permission on their own.

Create components is incorrect because project administrators can create and manage components within their own project from the project settings.

Create a Kanban board that shows only stories is incorrect because boards can be created using a filter such as an issue type filter and a project admin or other user with board creation rights can make a Kanban board that shows only stories.

Modify issue layout to hide fields when empty is incorrect because project administrators can adjust the issue layout for their project and configure field visibility rules such as hiding empty fields within the project settings.

When questions mention global permissions left at default think about actions that require Jira administrator rights. Permission schemes and global screen or layout configurations are common examples of settings you cannot change as a project admin.

The correct answer is Issues authored by Maya and the currently signed in user.

The JQL evaluates as creator in membersOf(“platform-admins”) AND creator not in membersOf(“administrators”) OR creator=currentUser(). AND is evaluated before OR so the first part selects platform-admins members who are not administrators. The platform-admins group contains Alex and Maya and the administrators group contains Alex and Leo. Excluding administrators from platform-admins therefore leaves only Maya and the OR adds any issues created by the signed in user which together yield issues authored by Maya and the current user.

Issues created by Alex and the current user is wrong because Alex is a member of both groups and is excluded by the creator not in membersOf(“administrators”) condition. The first part returns Maya rather than Alex so that option is not correct.

Issues created only by Maya is wrong because the OR creator=currentUser part adds issues created by the signed in user. The query does not limit results to Maya alone.

Issues reported by the currently signed in user is wrong because the query also returns issues created by Maya from the first part. The result is not limited to the current user.

Issues created by Alex Maya and the current user is wrong because Alex is excluded by the not in membersOf(“administrators”) condition so Alex will not be returned from the first part. The query therefore does not guarantee Alex is included.

Issues where the creator is any member of platform-admins is wrong because the first part explicitly excludes platform-admins members who are also administrators. That means not every platform-admins member is included and the OR may add the current user who could be outside that set.

When you parse JQL remember that AND has higher precedence than OR and check group membership overlaps to see who is removed by not in membersOf().

Users can translate project components, Users can translate the locked custom field, and Users are unable to translate the Resolution field are correct.

Users can translate project components is correct because components are project scoped and their names and descriptions can be localized within a company managed project when the localization features are used.

Users can translate the locked custom field is correct because custom field option labels and values can be localized even when the field configuration is locked, provided the localization or translation workflow for custom field options is available to the project administrators or translators.

Users are unable to translate the Resolution field is correct because Resolution is a system field with globally managed values and it is not provided as a translatable, project scoped field in company managed project localization workflows.

Users can translate issue types is incorrect because issue types are global scheme entities and they are not translated on a per project basis in company managed projects.

Users can translate priorities is incorrect because priorities are shared global entities and priority names are not localized per company managed project through the normal translation UI.

Users can translate statuses is incorrect because statuses are part of workflow definitions and they are managed globally or by workflow scheme rather than being translatable per project in company managed projects.

When a question mentions company-managed project focus on whether the item is project scoped or a global/system entity because only project scoped entities are typically localized per project.

The correct options are The mail processor was deleted, The mailbox location was modified and it is now empty, and The default reporter lost the Create Issues project permission.

The mail processor was deleted is correct because removing the processor stops the service that converts incoming mail into issues. If the handler no longer exists it will not poll or accept messages and that explains why mail that once created issues now does nothing.

The mailbox location was modified and it is now empty is correct because the processor has nothing to read when the mailbox folder or path is changed or when messages are moved. An empty or wrong mailbox location means no emails are available for conversion into issues even for previously working senders.

The default reporter lost the Create Issues project permission is correct because the mail handler often needs a valid reporter account that can create issues. If the default reporter account no longer has the Create Issues permission the handler may fail to create issues even though emails are being received.

The mailbox credentials expired is unlikely to be the root cause here because expired credentials typically produce visible authentication failures or error logs rather than the wider symptom of previously processed messages simply no longer creating issues when the processor still exists.

An issue type was removed from the mail processor configuration is not the best answer because removing an issue type would affect mappings for certain emails but it would not usually stop the entire processor from creating issues for all messages.

An issue security level is missing from the project is not the primary cause because missing security levels normally affect issue visibility or assignment rather than preventing issue creation across the board. This is less likely than a deleted processor, an empty mailbox, or a permission loss.

When troubleshooting inbound mail first verify the processor exists and the mailbox contains messages and then check that the reporter account has the Create Issues permission to quickly identify the most common failures.

The correct options are Saved filters and Workflow conditions.

A Saved filters entry can explicitly reference a group in its JQL or in its sharing settings and removing the group can break saved searches or change who can view or use the filter. For that reason saved filters are a prime place to look when you plan to remove a group.

Workflow conditions often include checks such as User Is In Group that reference a specific group to allow or block transitions. Removing the group can change workflow behavior or prevent transitions so workflow conditions must be checked.

Project roles can have groups assigned to them so they may be affected when a group is removed. They are not the first place to check for explicit group references because saved filters and workflow conditions tend to contain direct references that will immediately break functionality.

System default dashboard typically does not contain direct group references. Dashboards may include gadgets that rely on filters, so checking filters is more effective than checking the default dashboard first.

Issue type schemes define which issue types apply to projects and do not reference user groups, so removing a group will not affect issue type schemes.

When removing a group start by searching saved filters and workflow conditions because they often contain explicit group references that will break searches and transitions if the group is deleted.