Jira ACP-120 Exam Dump and Braindumps

Maya from Nimbus Solutions must decide whether to assign a Jira group or a project role for a set of users. In which situations is creating a Jira group the appropriate choice? (Choose 4)

• ❏ A. Site administrators will add and remove group members

• ❏ B. A project administrator will be in charge of changing the group membership

• ❏ C. The same users will be active contributors across several projects

• ❏ D. You need to assign permissions that apply across the entire Jira site

• ❏ E. Team members require the “Work On Issues” permission to be assigned via a global group

• ❏ F. Members must be able to perform bulk changes across many issues

When performing bulk edits across multiple projects why does the interface not display controls to enable or disable email notifications?

• ❏ A. Outgoing mail has been disabled at the site level

• ❏ B. They must be a Jira administrator or project administrator for every affected project

• ❏ C. They lack the ‘Make bulk changes’ global permission

Priya can set the Due Date field when she creates an issue but she cannot see that same field on the edit screen in her project. Which project setting does Priya need to change so the Due Date appears on the edit operation?

• ❏ A. Field Configuration

• ❏ B. Screen Scheme

• ❏ C. Issue Security Scheme

• ❏ D. Project Permissions

Diego administers a Jira instance for MapleTech and he changed the priority labels from Blocker PR11, High PR12, Normal PR13, Minor PR14, Trivial PR15 to Critical PR11, Major PR12, Standard PR13, Low PR14, Minimal PR15. What other Jira components might need to be adjusted as a direct result of renaming the priority values?

• ❏ A. Field configurations

• ❏ B. Automation rules

• ❏ C. Dashboards

• ❏ D. Workflow conditions

A website feedback widget enables visitors to file Jira tickets even if they do not have Jira accounts and it supports four trigger styles named Spotlight Inline Side and Custom. Which programming language is required to implement a custom trigger?

• ❏ A. HTML

• ❏ B. JQL

• ❏ C. Javascript

• ❏ D. CSS

• ❏ E. Java

Maya expected to receive an email when her team advanced a ticket to the next status but she did not get one. What is the most likely cause of the missing notification?

• ❏ A. Incoming mail handlers were removed

• ❏ B. A change in the workflow post function

• ❏ C. The global email processor has been disabled

• ❏ D. The default notification email prefix was changed

Marta sent an email to [email protected] which resulted in the creation of issue NV-5 in the company-managed project NV. She expected to receive an automated confirmation from Jira but she did not get any notification. She then forwarded her original message to [email protected] and the forwarded message did not include the issue key NV-5 in the subject. The instance has a single mail server and one mail handler configured with the Create a new issue or add a comment to an existing issue type. What will happen to Marta’s forwarded message?

• ❏ A. A new issue will be created in project NV

• ❏ B. A comment will be appended to the issue “NV-5”

• ❏ C. Both a new issue will be created and a comment will be added to “NV-5”

• ❏ D. The forwarded email will be ignored by Jira

If team-group is configured as the default group for Jira Software which of the following statements is definitely true?

• ❏ A. Jira Service Management users also have Jira Software access

• ❏ B. You cannot delete team-group

• ❏ C. New Jira Software users will also need Jira Work Management to create issues in the SUP project

• ❏ D. You cannot delete confluence-users group

An administrator at Meridian Tech needs to confirm which backup or restore action is not possible from a Jira Cloud site. Which operation is not supported by a Jira Cloud site?

• ❏ A. Download a full site backup and upload it to Google Cloud Storage for long term retention

• ❏ B. Import attachments and other media from a Jira Cloud backup

• ❏ C. Restore a cloud site backup into another Jira Cloud site

• ❏ D. Create a site backup that can be restored to a Jira Server or Data Center instance

• ❏ E. Import issue and project data that originated from a Jira Server backup into the cloud site

A delivery team at Nimbus Systems asked you to create a new Jira project that must meet these conditions immediately after creation without turning on extra features. The project must allow the team to prioritize work daily with a backlog and an Agile board. The project must support working in seven day sprints. The project must permit creating multiple issues at once. Which project type and template should you create?

• ❏ A. Company-managed project using the Kanban template

• ❏ B. Team-managed project using the Kanban template

• ❏ C. Company-managed project using the Scrum template

• ❏ D. Team-managed project on the Scrum template

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

For which situations is applying an Issue Security Level appropriate in a Jira project? (Choose 2)

• ❏ A. Prevent team leads from moving issues to other projects

• ❏ B. Restrict who can view the development panel for an issue

• ❏ C. Limit access so that only team leads can view and update urgent issues

• ❏ D. Hide the entire project from non team leads

• ❏ E. Allow only team leads to view issues that team leads opened

A product team at Maple Apps runs a Jira Cloud site with two company managed projects created from a Kanban template. The select list custom field “Severity” currently has two field contexts. The first context named “Context Core” applies to the CORE project for the Task issue type and offers options S1 S2 and S3 with default S2. The second context named “Context Mobile” applies to the MOBILE project for the Bug issue type and offers options S0 and S1 with default S1. Your lead requests that the “Severity” field provide options S0 S1 S2 and S3 only for the Story issue type within the CORE project. What is the least administratively costly approach to satisfy this requirement?

• ❏ A. Create an Automation rule to set or map a hidden field for Story issues in the CORE project to emulate the new severity choices

• ❏ B. Edit the existing Context Core field context to add the Story issue type and include the requested options

• ❏ C. Create a new select list custom field named “Severity CORE” and restrict its field context to the CORE project and the Story issue type

• ❏ D. Add a new field context for the existing “Severity” field scoped to the CORE project and the Story issue type with the requested options

After a release is archived in a Jira Cloud project hosted on example.com, where can that archived release be chosen from the version fields?

• ❏ A. Archived releases can still appear in both the Fix Versions dropdown and the Affects Versions dropdown

• ❏ B. Archived releases are selectable only in the Fix Versions dropdown

• ❏ C. Archived releases are not selectable in either the Fix Versions dropdown or the Affects Versions dropdown

• ❏ D. Archived releases are selectable only in the Affects Versions dropdown

In a private project where the Task issue type is restricted to the Member and Viewer roles, what actions can users with the project role “Viewer” perform on tasks?

• ❏ A. Create tasks

• ❏ B. Add comments to any task

• ❏ C. Change issue security or project roles

After a recent configuration update, several team members at Nimbus Apps cannot move Stories from the Grooming column to the Ready for Implementation column on their Scrum board and no error message appears while those users can move Stories between other columns without trouble. What could explain this behavior? (Choose 2)

• ❏ A. A workflow validator blocks that specific transition

• ❏ B. The status mapped to the Ready for Implementation column was removed from the board

• ❏ C. The Transition Issues project permission was revoked for the affected users

• ❏ D. A workflow post function is interfering with the transition

• ❏ E. A workflow condition prevents users from executing that transition

• ❏ F. The affected users no longer have Jira Software access

Marta, the Staffing lead, created a filter and tried to share it with the project role “Recruiters” in the Jira project “Staffing”. Marta has the Browse Project permission in the “Staffing” project. She was able to create the filter but after choosing the “Staffing” project she could not find the “Recruiters” project role in the sharing drop-down. What is the reason?

• ❏ A. Marta does not have the global Share filters and dashboards permission

• ❏ B. Marta is not a member of the “Recruiters” project role in the “Staffing” project

• ❏ C. Marta must first share the filter with all project roles in the Staffing project and then she will be able to pick the “Recruiters” role

• ❏ D. Jira Cloud does not support sharing filters with project roles

Sana at AtlasSoft wants her Jira instance to reflect the company branding. Which settings under the Look and feel global configuration can she modify to accomplish this? (Choose 3)

• ❏ A. Application background color

• ❏ B. Site favicon

• ❏ C. System default language

• ❏ D. Date and time display format

• ❏ E. Site logo

• ❏ F. Application title text

Lina is auditing a HarborTech company managed project that uses these issue types Story Task Bug Enhancement and Sub-item where Sub-item is the sub task issue type and she notices that Enhancement and Sub-item are rarely used so she wants to remove them from the project issue type scheme What statement is true?

• ❏ A. Jira will automatically map Enhancement and Sub-item issues to the project’s default standard issue type

• ❏ B. She will be required to choose a destination issue type for each Enhancement when removing it from the scheme

• ❏ C. She must first convert any existing Sub-item issues into a standard issue type before she updates the issue type scheme

• ❏ D. She must reassign all existing Enhancement issues to another standard issue type before making changes to the scheme

• ❏ E. If multiple sub task types existed she could remove one and Jira would prompt to move existing sub tasks to the other sub task type

Priya recently started as a delivery lead at NovaApps and she needs permission to manage project versions and project components and to create a new sprint and to update an issue due date? (Choose 4)

• ❏ A. Manage Project Roles

• ❏ B. Schedule Issues

• ❏ C. Manage Components

• ❏ D. Administer Projects

• ❏ E. Edit Issues

• ❏ F. Manage Sprints

Which JQL queries will return resolved issues from the saved filter ‘ACP-125 Practice’? (Choose 3)

• ❏ A. filter = ‘ACP-125 Practice’ AND status = Done

• ❏ B. filter = “ACP-125 Practice” AND resolution is NOT EMPTY

• ❏ C. filter = “ACP-125 Practice” AND resolution is NOT NULL

• ❏ D. filter = ‘ACP-125 Practice’ AND resolution = Done

Which Jira configuration affects whether email notifications are sent to users when issue events occur?

• ❏ A. Permission schemes

• ❏ B. Screens

• ❏ C. Agile boards

• ❏ D. Issue security levels

• ❏ E. Dashboards

Ravi is unable to locate any accounts when he tries to pick a user in the assignee field on the Vertex Systems Jira Cloud instance. Which configuration must be updated so users appear in the user picker?

• ❏ A. Issue security scheme

• ❏ B. User directory settings

• ❏ C. Global permission to browse users and groups

• ❏ D. Project permissions

Maya ran three JQL queries against the Bluewave project and she expected the third query to return 110 issues. JQL A of project = “Bluewave” returns 130 issues. JQL B of project = “Bluewave” AND fixVersion = “Release 2.0” returns 20 issues. JQL C of project = “Bluewave” AND fixVersion != ‘Release 2.0’ returns 40 issues. What could explain the discrepancy?

• ❏ A. Maya must reindex Jira to obtain the correct counts

• ❏ B. Change the single quotes around the fixVersion value to double quotes

• ❏ C. Some issues are not visible because Maya does not have Browse Projects permission

• ❏ D. An issue security level has been applied that limits which issues Maya can see

• ❏ E. project = “Bluewave” AND (fixVersion != ‘Release 2.0’ OR fixVersion is EMPTY)

Marisol has just created a new company managed project from a Scrum template and she must update the project configuration to satisfy several constraints. The Summary system field on the Sub task issue type must be prevented from being edited after creation. The Affects Versions system field must be added to the Create and Edit screens for the Task issue type. A new sub task issue type named Infrastructure Sub task must be added to the project and it must keep the default configuration. No other project settings should be changed. The project currently contains the following issue types Epic Standard Issue Type Story Standard Issue Type Task Standard Issue Type Bug Standard Issue Type and Sub task Sub task issue type. How many screen schemes does Marisol need to create?

• ❏ A. 4

• ❏ B. 0

• ❏ C. 2

• ❏ D. 1

• ❏ E. 3

Sana is a release manager at HarborSoft and she needs to make sure that whenever an issue moves between workflow statuses it is reassigned to the correct team member. Which Jira configuration should she use to ensure the assignee is set during the transition?

• ❏ A. Automation rule

• ❏ B. Transition screen

• ❏ C. Post function

• ❏ D. Project component

• ❏ E. Field configuration

The correct choices are Site administrators will add and remove group members, The same users will be active contributors across several projects, You need to assign permissions that apply across the entire Jira site, and Members must be able to perform bulk changes across many issues.

Groups are managed centrally in site administration so they are the right choice when site administrators will add and remove group members. Central management keeps membership consistent and reduces duplicate work across projects.

Using a group makes sense when the same users are active contributors across several projects because you can grant access once and reuse that group in multiple project permission schemes and configurations.

When you need to assign permissions that apply across the entire Jira site a group is appropriate because global permissions and product access are granted at the site level and are typically assigned to groups rather than individual project roles.

Bulk change is controlled by a global permission that affects many issues so granting that capability to a group makes it easier to allow members to perform bulk changes across many issues without managing membership in each project.

A project administrator will be in charge of changing the group membership is incorrect because project administrators cannot manage site groups. If project admins must control membership it is better to use project roles or project level membership options.

Team members require the “Work On Issues” permission to be assigned via a global group is incorrect because the Work On Issues permission is a project permission and it can be assigned via project roles or groups within a permission scheme. It does not have to be assigned only through a global group and using project roles often gives better per project flexibility.

For questions about groups versus project roles think about who manages membership and the scope of permissions. If membership is managed centrally or permissions must apply across the site choose group. If project admins need to control access or membership varies by project choose project role.

The correct answer is that They must be a Jira administrator or project administrator for every affected project.

When performing bulk edits across multiple projects the notification toggles are part of project configuration and the UI will only expose controls if the user has administrative authority for each project. If the user is not a They must be a Jira administrator or project administrator for every affected project the interface hides those controls to prevent unauthorized changes to project notification settings.

Outgoing mail has been disabled at the site level is incorrect because disabling outgoing mail would stop messages from being delivered but it would not explain why the bulk edit interface omits the notification controls. The visibility of those controls is driven by admin privileges rather than the mail engine being enabled or disabled.

They lack the ‘Make bulk changes’ global permission is incorrect because that global permission governs whether a user can initiate bulk operations at all. A lack of that permission would prevent performing bulk edits rather than selectively hiding the email notification toggles. The missing controls indicate a permissions scope tied to project administration instead.

When questions involve actions across multiple projects think about whether the task touches project configuration and then check whether project admin or site admin rights are required. That distinction often points to the correct answer.

The correct option is Screen Scheme.

Screens control which fields are shown on create edit and view operations and a Screen Scheme maps those operations to the specific screens used by the project. If Priya can set the Due Date on the create screen but cannot see it on the edit screen then the edit operation is using a different screen. Changing the project’s Screen Scheme so that the edit operation uses a screen that contains the Due Date field will make the field appear when editing.

Field Configuration is about field behaviors such as whether a field is required hidden or has custom help text and it does not assign fields to the create edit or view operations. Because Priya can set the Due Date when creating issues the field is not hidden so Field Configuration is not the correct setting to change.

Issue Security Scheme controls visibility of entire issues by security level and it does not determine which fields display on an edit screen. That scheme affects who can see an issue not which fields are on a screen.

Project Permissions govern who can perform actions such as creating editing or transitioning issues and they do not control the layout of fields on screens. Since Priya already can create issues changing Project Permissions would not make the Due Date appear on the edit operation.

When a field appears on one operation but not another check the screen and screen scheme mappings first because screens determine which fields are shown per operation.

The correct option is Workflow conditions.

Workflow conditions are the right choice because workflows can include conditions and validators that explicitly check an issue’s priority by its displayed name. When you change the priority labels the logic that matches those names can stop working and you must update the affected workflow conditions or switch them to use priority IDs instead.

Field configurations are not directly affected because the Priority field itself and its screen and context settings remain the same when you rename priority labels.

Automation rules are not automatically broken by a label rename because many automations operate on the underlying priority value or ID rather than the display label. If a rule explicitly referenced the old name then you would update that rule, but that is not a universal direct consequence.

Dashboards do not require a direct change simply because labels were renamed since dashboards display issue data. Some filters or gadgets that match by name might need review, but the dashboard components themselves do not need to be changed as a direct result.

When a question mentions renaming system values think about where the name is used in logic. Check workflows and validators first and prefer using ID references to avoid breakage.

The correct option is Javascript.

The feedback widget runs in the visitor’s browser and a custom trigger must be implemented client side so it can listen for user actions and call the widget API. That interactive behavior is implemented with Javascript, which is why Javascript is required for a custom trigger.

HTML defines the structure of the page and can host the widget markup but it cannot implement the interactive logic needed for a custom trigger, so it is not the correct choice.

JQL is a query language for searching Jira issues and it does not provide client side scripting capabilities, so it cannot be used to implement a trigger.

CSS controls presentation and styling and it cannot execute logic or handle events required to open the widget, so it is not suitable for a custom trigger.

Java runs on the server or in a different runtime than the browser and it is not the language used to implement in page widget triggers, so it is not the required language.

When a feature asks for a custom or client side trigger think about what runs in the browser and choose JavaScript for implementing event handling and calling widget APIs.

A change in the workflow post function is the correct answer.

When a transition includes a post function that sends notifications or fires an event and that post function is removed or modified the notification will not be sent when the issue moves. Workflow post functions are the usual mechanism to trigger email notifications on status changes so altering them is the most likely reason Maya did not receive the expected message.

Incoming mail handlers were removed is not the most likely cause because incoming mail handlers control creating or updating issues from email rather than sending notifications when a workflow transition occurs.

The global email processor has been disabled would affect how incoming or queued mail is processed but it is not the typical cause for a missing transition notification. Outgoing notifications depend on the mail server and notification configuration and a post function change is a more direct explanation when a single transition stops sending emails.

The default notification email prefix was changed would only alter the subject prefix of notification emails and would not prevent the notification from being sent. A prefix change would not explain why Maya received no message at all.

When a notification for a transition is missing check the transition’s post functions and the project notification scheme first. If a post function that triggers the notification was removed then restoring it often fixes the issue.

A comment will be appended to the issue “NV-5”

The mail handler in this instance is configured with the “Create a new issue or add a comment to an existing issue” type and Jira will try to thread incoming mail to existing issues before creating new ones. Jira uses the issue key in the subject or the message headers such as Message-ID and In-Reply-To to match mail to an existing issue. In this scenario forwarding the original message retains the threading headers or references to the original notification and so Jira associates the forwarded mail with the already created issue and adds it as a comment.

Not receiving an automated confirmation does not prevent the mail handler from threading the forwarded mail. The lack of a notification only affects whether Marta received an email back and does not change how the handler links the forwarded message to the existing issue.

A new issue will be created in project NV is wrong because the handler will detect that the message belongs to an existing thread and will append a comment rather than create a duplicate issue.

Both a new issue will be created and a comment will be added to “NV-5” is wrong because the mail handler does not perform both actions for the same incoming message. It either creates a new issue or appends to an existing one when it can match the message to an issue.

The forwarded email will be ignored by Jira is wrong because the handler is active and set to create or comment. The mail would only be ignored if it were malformed, identified as spam, or blocked by other mail server rules, which is not indicated in the scenario.

When answering mail handler questions focus on whether the handler matches by issue key or by message headers and then decide if the mail will be threaded into an existing issue or create a new one.

You cannot delete team-group is correct.

This is correct because when a group is configured as the default group for a product like Jira Software it is used to grant product access to new users and the group cannot be deleted while it is set as that product’s default. You must remove the group from the product’s default group setting before you can delete it.

Jira Service Management users also have Jira Software access is incorrect because configuring a default group for Jira Software only affects access to Jira Software and does not automatically grant access to Jira Service Management. Product default groups apply to the specific product named.

New Jira Software users will also need Jira Work Management to create issues in the SUP project is incorrect because the default group setting for Jira Software does not impose a requirement to have Jira Work Management. Issue creation depends on the product access and project permissions, not on adding an unrelated product.

You cannot delete confluence-users group is incorrect because being the default group for Jira Software does not make a Confluence group undeletable. A group is only protected from deletion if it is currently assigned as a default for a product or if other system rules explicitly protect it.

When you see default group in a question check which product it applies to and then consider product scope and deletion rules. A group set as a product default usually must be removed from that default setting before it can be deleted.

The correct option is Create a site backup that can be restored to a Jira Server or Data Center instance.

That operation is not supported because Jira Cloud backup exports are produced for the cloud environment and they are not compatible with on premises Server or Data Center restore processes. Cloud backups omit or transform some system and app data and the resulting package cannot be directly restored into an on premises instance.

Also note that Jira Server has been deprecated by Atlassian and Server deployments are becoming less common, so questions about restoring cloud backups to Server are less frequent on newer exams.

Download a full site backup and upload it to Google Cloud Storage for long term retention is incorrect because administrators can create and download a site backup and then store that file in external object storage such as Google Cloud Storage for long term retention.

Import attachments and other media from a Jira Cloud backup is incorrect because backups can include attachments and media and the import process can restore them when the backup was created with attachments included and size limits are met.

Restore a cloud site backup into another Jira Cloud site is incorrect because cloud site imports or restores into another cloud site are supported by the cloud administration tools, subject to compatibility and size limits and subject to the target site being prepared for the import.

Import issue and project data that originated from a Jira Server backup into the cloud site is incorrect because migrations from Server or Data Center into Jira Cloud are supported using the Jira Cloud Migration Assistant or other import tools to bring issues and project data into Cloud.

When you see backup and restore questions focus on direction of migration and format compatibility. Remember that cloud exports are not simply interchangeable with on premises Server or Data Center restores.

Team-managed project on the Scrum template is correct.

The Team-managed project on the Scrum template provides a backlog and an Agile board immediately after creation and it includes Scrum features so you can configure and run seven day sprints right away without enabling extra project features.

The Team-managed project on the Scrum template also supports quick creation of multiple issues from the backlog and the standard create flow so the team can add batches of work without additional setup. Team-managed projects are designed for team autonomy and minimal administrative configuration.

Company-managed project using the Kanban template is incorrect because the Kanban template does not provide sprint planning or sprint execution and it lacks the sprint-based backlog workflow needed for seven day sprints.

Team-managed project using the Kanban template is incorrect because Kanban is not a sprint based template and it therefore will not meet the requirement to run seven day sprints with a sprint backlog.

Company-managed project using the Scrum template is incorrect because company-managed projects often require more administrative configuration and permissions to get the same team-level, out of the box experience that the team-managed Scrum template provides.

When a question asks for Scrum features that must work immediately with minimal configuration choose a team-managed Scrum project because it is built for team autonomy and quick setup.

The correct answers are: Allow only team leads to view issues that team leads opened and Limit access so that only team leads can view and update urgent issues.

Issue security levels restrict visibility and permissions for individual issues so they are appropriate when you need to limit who can see or update particular issues without changing access for the whole project. This makes issue security well suited to cases where only team leads should view or update specific issues marked urgent or issues opened by team leads.

Prevent team leads from moving issues to other projects is incorrect because moving issues is governed by project and global permissions rather than by issue security levels. Issue security does not stop the Move operation.

Restrict who can view the development panel for an issue is incorrect because the development panel is controlled by application access and integration permissions with developer tools and not by issue security levels. You would adjust app access or integration settings to change that panel visibility.

Hide the entire project from non team leads is incorrect because issue security operates at the issue level and cannot hide an entire project. Project visibility and access are managed through project permissions and project settings.

Focus on whether the requirement applies to individual issues or to the whole project because issue security is for per issue visibility while project permissions control broader access.

Create a new select list custom field named “Severity CORE” and restrict its field context to the CORE project and the Story issue type is the correct choice.

Creating a separate select list field scoped only to CORE Story lets you show exactly the options S0 S1 S2 and S3 without changing any existing contexts or defaults that the current Severity field provides for CORE Tasks and MOBILE Bugs. It isolates the change so you can add the new field to Story screens quickly and avoid any downstream impact on reports filters or automation that reference the original field.

Create an Automation rule to set or map a hidden field for Story issues in the CORE project to emulate the new severity choices is not a good approach because automation adds ongoing maintenance and it does not give users a native select list to interact with. The user experience and filtering will be more complex and it increases operational overhead.

Edit the existing Context Core field context to add the Story issue type and include the requested options is undesirable because changing that context would alter the options and default values that currently apply to Tasks in CORE. That would risk disrupting existing work and require coordination and testing across teams.

Add a new field context for the existing “Severity” field scoped to the CORE project and the Story issue type with the requested options might seem possible but it still changes the global field configuration and can create management complexity for a field that is already used in other projects and issue types. Creating a dedicated field is the safer and lower effort choice for a narrow, project specific requirement.

When you need different choices for a single project and issue type prefer creating a separate custom field to isolate the change and minimize impact on existing contexts and defaults. Use a new field when the existing field is shared across projects.

The correct answer is Archived releases are not selectable in either the Fix Versions dropdown or the Affects Versions dropdown.

When you archive a version in Jira Cloud it is removed from the issue version pickers and cannot be chosen when creating or editing issues. That means Archived releases are not selectable in either the Fix Versions dropdown or the Affects Versions dropdown. Archived versions remain listed on the Releases page for historical reference and you can unarchive them if you need them back in the pickers.

Archived releases can still appear in both the Fix Versions dropdown and the Affects Versions dropdown is incorrect because archiving hides the version from those pickers and prevents selection.

Archived releases are selectable only in the Fix Versions dropdown is incorrect because archiving removes the version from both Fix Versions and Affects Versions and it is not selectable in either field.

Archived releases are selectable only in the Affects Versions dropdown is incorrect because archiving removes the version from both pickers and it cannot be selected in Affects Versions.

Remember that archiving hides versions from the issue version pickers but keeps them on the Releases page so check Releases if you need to unarchive a version.

Add comments to any task is correct. Viewers can see tasks when the Task issue type is restricted to Member and Viewer and they are able to add comments on those tasks.

The restriction of the Task issue type to Member and Viewer limits who can view and access the issues in the private project. Once a Viewer has access to a task they can perform actions that the permission scheme allows for their role, and adding comments is a common nonadministrative action granted to Viewer roles in many permission schemes.

Create tasks is wrong because creating an issue requires the project permission to create issues and that permission is not typically granted to the Viewer role.

Change issue security or project roles is wrong because changing issue security levels and modifying project roles are administrative actions that require project administrator privileges or specific administrative permissions, which Viewers do not have.

When a question mentions role restrictions and issue types focus on which permissions are needed for each action. View and comment are usually separate from create or admin actions so rule out answers that require administrative privileges.

The status mapped to the Ready for Implementation column was removed from the board and A workflow condition prevents users from executing that transition are correct.

The status mapped to the Ready for Implementation column was removed from the board explains the behavior because boards display issues based on the statuses that are mapped to columns. If the status that a transition would set is no longer mapped to any column then that board move will not be available even though other transitions continue to work, and the board UI may not show an explicit error.

A workflow condition prevents users from executing that transition also fits because workflow conditions restrict which users, groups, or roles can see or perform a given transition. When a condition blocks a user the transition option is hidden for them and they cannot move the issue, which matches the symptom of only some users being unable to move Stories and no error appearing.

A workflow validator blocks that specific transition is unlikely because validators run when the transition is executed and they normally surface a validation error if required data is missing. The scenario states that no error message appears.

The Transition Issues project permission was revoked for the affected users is unlikely because removing that permission would prevent the users from transitioning any issues in the project. The users can move issues between other columns so they still have transition privileges.

A workflow post function is interfering with the transition is unlikely because post functions run after a transition completes and they do not typically prevent the transition from being offered on the board. A post function failure would not usually cause the transition to be hidden without an error.

The affected users no longer have Jira Software access is unlikely because users without product access cannot use boards to move issues at all. The fact that these users can move Stories between other columns shows they still have Jira Software access.

When a board move silently fails check the board’s status mappings first and then review workflow conditions for that transition. That sequence will quickly reveal whether the column lost its status or whether the transition is hidden for some users.

The correct answer is Marta is not a member of the “Recruiters” project role in the “Staffing” project.

When you share a filter to a project role, Jira only lists project roles that you are a member of in the selected project. If you are not a member of a given role it will not appear in the sharing drop down. Marta can create the filter because she has the necessary project permissions, but she must also belong to the target project role to share the filter directly with that role.

Marta does not have the global Share filters and dashboards permission is incorrect because a complete lack of the global share permission would prevent initiating or completing the share at all. The scenario describes being able to create the filter and open sharing options, so the missing entry is more likely due to role membership.

Marta must first share the filter with all project roles in the Staffing project and then she will be able to pick the “Recruiters” role is incorrect because Jira does not require or support a cascading share step like that. The sharing dialog simply lists roles you belong to and you do not need to share with other roles first.

Jira Cloud does not support sharing filters with project roles is incorrect because Jira Cloud does support sharing filters with project roles. Project roles are a standard sharing target when you have the appropriate membership and permissions.

When a role is missing from the sharing drop down first check your project role membership in the target project and then check your global sharing permission if sharing is disabled.

Site favicon, Date and time display format, and Site logo are the correct options.

The global Look and feel configuration in Jira is intended to control visible branding elements so administrators can upload a custom Site logo and set a Site favicon to match the company identity. The settings also include display preferences such as the Date and time display format so that timestamps and dates appear consistently for users.

The Site logo appears in the product header and the Site favicon appears in browser tabs and bookmarks which makes them primary branding items. The Date and time display format affects how dates and times are shown across issues and activity feeds and helps keep the user experience consistent.

Application background color is incorrect because the standard Look and feel screen does not provide a global background color setting in Jira administration. Branding is handled through logo, favicon and related display options instead.

System default language is incorrect because language and locale are managed under general system or user settings rather than the Look and feel configuration.

Application title text is incorrect because changing the product title or metadata is not part of the Look and feel page in standard Jira administration and is handled elsewhere depending on the deployment.

When you see a question about Look and feel think about elements users see immediately such as the logo, the favicon, and how dates are displayed rather than internal system defaults.

The correct option is She must first convert any existing Sub-item issues into a standard issue type before she updates the issue type scheme.

This is correct because Jira does not allow you to remove a sub-task issue type from a project’s issue type scheme while issues of that sub-task type still exist in the project. You must convert or delete those sub-task issues so they become standard issues before the scheme can be updated. Converting the existing She must first convert any existing Sub-item issues into a standard issue type before she updates the issue type scheme entries removes the dependency that prevents removal of the sub-task type.

Jira will automatically map Enhancement and Sub-item issues to the project’s default standard issue type is incorrect because Jira will not silently remap issues when you remove an issue type. Automatic remapping does not occur and the system requires an explicit conversion or mapping action when relevant.

She will be required to choose a destination issue type for each Enhancement when removing it from the scheme is incorrect because Jira does not require selecting a destination for each individual issue. When removing a standard issue type that has existing issues you are prompted to map that issue type to another type at the scheme level, not to choose a destination for every single issue one by one.

She must reassign all existing Enhancement issues to another standard issue type before making changes to the scheme is incorrect because you do not have to manually reassign every Enhancement issue beforehand. When you remove a standard issue type from a scheme and there are existing issues, Jira prompts you to choose a replacement issue type for that issue type across the project so manual reassignment is not required.

If multiple sub task types existed she could remove one and Jira would prompt to move existing sub tasks to the other sub task type is incorrect because Jira will not prompt to migrate existing sub-tasks to another sub-task type. Sub-task types cannot be automatically remapped that way and you must convert or handle those sub-tasks before removing the sub-task type.

When a question mentions removing an issue type that still has issues, think about whether Jira requires conversion or mapping at the type level and not per issue. Remember that sub-task types often need conversion to standard issues before they can be removed.

The correct answers are: Administer Projects, Manage Sprints, Edit Issues and Schedule Issues.

The Administer Projects permission grants project administrators the ability to configure project settings and to create and edit project versions and components, and that is why it is required to manage versions and components.

The Manage Sprints permission specifically allows creating and managing sprints, so it is required to create a new sprint and to control sprint lifecycle actions in the project.

Both Edit Issues and Schedule Issues are needed for updating issue dates and related fields. The Edit Issues permission allows changing issue content and fields in general, and the Schedule Issues permission covers modifications to scheduling fields such as start dates and due dates in boards and planning views.

Manage Project Roles is incorrect because that permission only controls role membership and role assignment and it does not grant rights to manage versions components sprints or edit issue scheduling fields.

Manage Components is incorrect in this scenario because component management is covered by the project administration role provided by Administer Projects, so it is not separately required when that permission is granted.

When mapping tasks to permissions identify whether the action affects project configuration or individual issues and then pick the permission that matches the scope. Pay attention to project administration versus issue and sprint permissions.

filter = “ACP-125 Practice” AND resolution is NOT EMPTY, filter = “ACP-125 Practice” AND resolution is NOT NULL and filter = ‘ACP-125 Practice’ AND resolution = Done are correct.

Both filter = “ACP-125 Practice” AND resolution is NOT EMPTY and filter = “ACP-125 Practice” AND resolution is NOT NULL return issues where the resolution field has a value. These forms are equivalent for the purpose of finding resolved issues because they check that the resolution is set rather than empty.

The expression filter = ‘ACP-125 Practice’ AND resolution = Done is also correct when Done is a resolution value in your Jira instance. This query matches issues whose resolution field exactly equals the value Done and so it returns resolved issues that use that resolution.

filter = ‘ACP-125 Practice’ AND status = Done is incorrect. The status field reflects workflow state and not the resolution field. A status named Done does not always guarantee that the resolution field is set and therefore it is not a reliable way to find resolved issues.

When you need resolved issues focus on the resolution field rather than status. Use resolution is not empty to find any resolved issues or use resolution = value when you need a specific resolution.

The correct option is Issue security levels.

Issue security levels determine which users or groups can view a specific issue. If a user is not allowed to view an issue because of its security level they will not receive email notifications for events on that issue. Notification delivery requires both being listed as a recipient and having permission to see the issue so security levels can effectively prevent emails from being sent to some users.

Permission schemes define what actions users can perform and whether they can browse issues and while they affect who can do what they do not directly configure which events trigger emails or which recipients get notified. Sending notifications is governed by notification schemes and by visibility rules.

Screens control which fields are shown when creating editing or viewing issues and they do not affect who receives email notifications for issue events.

Agile boards determine how issues are displayed and managed within boards and sprints and they do not change notification behavior for issue events.

Dashboards are composed of gadgets and provide a presentation view for users and they do not control the delivery of notification emails.

When a question asks who receives emails focus on settings that change who can see the issue or who is on the recipient list. Settings that affect visibility often influence whether notifications are delivered.

Global permission to browse users and groups is correct because the user picker only returns accounts that the person performing the pick is allowed to view and that visibility is granted by this global permission.

The setting that controls whether a user can see and select other accounts is the Global permission to browse users and groups and site administrators grant it on the global permissions screen. Without that permission the picker will not return matches even when accounts exist in the directory.

Issue security scheme is incorrect because issue security controls who can view specific issues and it does not determine whether accounts appear in the user picker.

User directory settings is incorrect because directory settings manage where accounts come from and how they are synced and they do not by themselves grant the right to browse users across the site.

Project permissions is incorrect because project permissions control actions within a project and they do not enable or disable the global ability to browse users and groups for the user picker.

When the user picker returns no accounts first verify the account doing the pick has the Browse users and groups global permission and then check directory sync and membership if needed.

The correct option is project = “Bluewave” AND (fixVersion != ‘Release 2.0’ OR fixVersion is EMPTY).

The discrepancy is explained by how JQL treats the != operator. The project query returns 130 issues and 20 issues have fixVersion = ‘Release 2.0’. The query using fixVersion != ‘Release 2.0’ returned 40 issues because that test excludes issues where fixVersion is empty. The missing issues are those with no fixVersion set and they account for the difference.

By adding OR fixVersion is EMPTY you explicitly include the issues that have no fixVersion so the counts add up to the full 130.

Maya must reindex Jira to obtain the correct counts is incorrect because reindexing would not change the semantics of the != operator or whether empty values are returned. The numbers here match JQL behavior rather than an indexing fault.

Change the single quotes around the fixVersion value to double quotes is incorrect because JQL accepts either single or double quotes for string literals and the quotes do not affect whether empty values are excluded by !=.

Some issues are not visible because Maya does not have Browse Projects permission is incorrect because Maya can run project = “Bluewave” and see 130 issues in that result. A missing browse permission would reduce visibility across queries and would not produce the specific pattern caused by empty fixVersion values.

An issue security level has been applied that limits which issues Maya can see is incorrect because an issue security level would restrict visibility across queries in a way that would not explain why fixVersion != ‘Release 2.0’ returns 40 while fixVersion = ‘Release 2.0’ returns 20. The pattern here is explained by empty fixVersion fields rather than security settings.

When you see a JQL using != remember that it excludes empty values so include an is EMPTY clause when you need to count issues with no value set.

The correct answer is 2.

Marisol needs to create two separate screen schemes because there are two distinct per-issue-type differences in create and edit screens that must not affect other issue types. One screen scheme is required for the Task issue type so that the Create and Edit screens include the Affects Versions field for Task only. The second screen scheme is required for the existing Sub task issue type so that the Create screen keeps Summary while the Edit screen omits Summary to prevent post-creation edits. Mapping these two screen schemes to only the targeted issue types preserves the default configuration for the new Infrastructure Sub task and for all other issue types.

4 is incorrect because four screen schemes would be more than needed given only two distinct screen mapping differences are required.

0 is incorrect because at least one new screen scheme is required for Task and one is required for the Sub task so doing nothing would not meet the requirements.

1 is incorrect because a single screen scheme cannot implement two different sets of create and edit field configurations for two different issue types without impacting other types.

3 is incorrect because three screen schemes would be unnecessary since only two unique screen mappings are needed to satisfy the task for Task and for the existing Sub task.

When a question asks about screen schemes count how many distinct create or edit screen configurations must be applied only to specific issue types. Create one screen scheme for each unique mapping so you do not alter defaults for other types. Count the differences per issue type rather than per field.

The correct option is Post function.

Post function runs as part of a workflow transition and executes automatically when an issue moves between statuses. You can add a post function to set or change the Assignee field during the transition so the issue is reassigned as the transition completes. This is the standard Jira workflow mechanism to make programmatic changes tied to a specific transition.

Automation rule is incorrect because automation executes separate rules that are not configured inside the workflow transition itself. Automation can change assignees based on events but it is not the built in transition step used to ensure the assignee is set at the moment the workflow transition runs.

Transition screen is incorrect because a transition screen only collects input from the user during a transition and does not by itself set values automatically. A screen can allow the user to set the Assignee but it will not programmatically reassign the issue unless combined with a post function or user input.

Project component is incorrect because components are a way to group work and optionally designate component leads but they do not control reassignment during specific workflow transitions. Components do not act as transition actions.

Field configuration is incorrect because field configurations control field behavior such as required or hidden status and validation rules. They do not perform actions that set or change field values during a transition.

When a question mentions something that must happen automatically during a workflow transition think of post functions first because they execute as part of the transition. Use automation when the change should occur outside of the workflow step or across multiple projects.