Jira ACP-620 Exam Dumps and Braindumps | Managing Atlassian Projects in the Cloud

Restrict who can transition issues by referring to a group custom field and Modify the set of “Resolution” values for the project are not supported by a team managed project in Jira Cloud.

Restrict who can transition issues by referring to a group custom field is not available because team managed projects use simplified, project scoped configuration and they do not support workflow conditions that depend on global group custom fields. Limiting transitions by group normally requires a company managed workflow or global custom field plus administrator level configuration which you cannot create inside a team managed project.

Modify the set of “Resolution” values for the project is not available because resolution values are a global Jira configuration that only Jira administrators can change. The resolution list is managed in global administration and cannot be customized per team managed project.

Enable release and milestone tracking is incorrect because team managed projects do support release and milestone tracking through the project releases and roadmap features that teams can enable at the project level.

Create cascading select fields where one dropdown depends on another is incorrect because team managed projects provide configurable custom fields and support dependent dropdown behavior such as cascading selects within the project.

Default a Timestamp field to the current date and time is incorrect because team managed projects support date and time custom fields and you can set default values including the current date and time for those fields at the project level.

Team-managed Kanban project is correct.

Team-managed projects give the team direct control over project settings and permissions so they can decide who can view and edit work and how workflows operate. A Kanban board provides flexible timing because it emphasizes continuous flow and work in progress limits rather than fixed length sprints, which makes the combination of a team-managed project and a Kanban board the best fit for a team that wants control and flexible task timing.

Company-managed Kanban project is incorrect because company-managed projects use centralized administration and shared schemes for permissions and configuration, so the team does not have the same level of independent control over permissions.

Team-managed workflow project is incorrect because it is not the standard name for a project type that explicitly pairs team autonomy with a Kanban board, and the phrase focuses on workflow customization rather than the board type and permission model the question requires.

The correct answers are Assign group membership when members must perform bulk edits across many issues, Use groups to grant global system permissions across the Jira site, Create groups when the same set of users will collaborate across several projects, and Use groups when overall membership should be controlled by a site administrator.

Assign group membership when members must perform bulk edits across many issues is correct because groups let you grant the same permissions to many users at once and simplify bulk operations across projects and issues. Using a group reduces administrative overhead when many people need identical capabilities for wide ranging changes.

Use groups to grant global system permissions across the Jira site is correct because global permissions are managed at the site level and groups provide a single place to assign those permissions so they apply consistently across all projects. This is the appropriate mechanism for site wide capabilities that are not tied to a single project.

Create groups when the same set of users will collaborate across several projects is correct because groups represent a stable collection of users that can be reused in multiple projects. Creating a group avoids repeated assignments and keeps membership consistent across projects.

Use groups when overall membership should be controlled by a site administrator is correct because groups are typically managed by site admins and they allow centralized control of who is inside the group. This is useful when membership decisions must be handled by administrators rather than by individual project leads.

Team members need the ‘Work On Issues’ permission to record time spent is incorrect because the question is about when to use groups rather than about specific permissions. Time tracking depends on the project permission scheme and that permission can be granted via roles or groups as needed so creating a group solely for logging work is not a typical reason to prefer groups.

Allow a project administrator to directly add or remove users from a group is incorrect because project administrators normally cannot manage global groups. Group membership is managed at the site administration level so groups are not the right choice when you want project administrators to control membership directly.

The correct option is status was “Done” and status != Done. This query finds issues that were at some point in the “Done” status and whose current status is not “Done”.

The clause status was “Done” uses the historical operator to match issues that previously had that value. The clause status != Done restricts the results to issues whose current status is different from Done. Together they return issues that were in Done and are now in another status.

status changed from “Done” to “Open” OR “In progress” OR “Pending review” is incorrect because the syntax is incomplete and it only targets specific direct transitions. You would need separate full changed clauses or correct grouping to express those transitions and it still would miss issues that left Done via other intermediate changes.

status in (“Open”,”In progress”,”Pending review”) is incorrect because it only checks the current status and does not require the issue to have been in Done previously.

Archived releases are not selectable in either the “Fix Versions” dropdown or the “Affects Versions” dropdown.

This is because archived releases are hidden from the version pickers so they cannot be chosen when creating or editing issues. Existing issues that already reference an archived version will still display that value but the archived item will not be available as a selectable option for new changes.

Archived releases remain selectable in both the “Fix Versions” dropdown and the “Affects Versions” dropdown is incorrect because archiving removes versions from the picklists and prevents new selections.

Archived releases are selectable only in the “Fix Versions” dropdown and not in the “Affects Versions” dropdown is incorrect because archiving affects visibility in both pickers and does not leave one picker selectable while hiding the other.

Archived releases are selectable only in the “Affects Versions” dropdown and not in the “Fix Versions” dropdown is incorrect for the same reason because archived versions are removed from both dropdowns and are not available for selection in either field.

Single automation listening for Issue Assigned Issue Updated and Issue Transitioned with JQL priority = Critical and Slack action is correct.

This single rule can include multiple triggers for Issue Assigned, Issue Updated and Issue Transitioned and then use a JQL condition to limit execution to priority = Critical. Using one automation with a Slack action posts alerts immediately when any of those events occur and keeps the logic in one place so it is easier to maintain.

Scheduled automation running every five minutes querying priority = Critical and posting to Slack is not ideal because polling introduces delay and extra load. A scheduled rule runs on an interval and it will not alert instantly when an issue is assigned updated or transitioned.

Outgoing webhook on issue events that filters priority = Critical and posts to Slack is less suitable because webhooks require an external endpoint to receive the payload and handle the Slack call. That adds infrastructure and complexity compared with using the built in Slack action in the automation engine.

Three separate automation rules for Issue Assigned Issue Updated and Issue Transitioned with Slack actions is functionally possible but it creates duplicate rules and more maintenance work. Combining the triggers into a single rule with a JQL condition achieves the same behavior with less duplication.

The correct permissions are Remove All Worklogs, Modify All Worklogs, and Log Work on Issues.

Remove All Worklogs is required because Marina must be able to delete worklogs created by other team members across the project and that permission specifically allows deletion of all users worklogs.

Modify All Worklogs is required because updating or correcting time entries for other people requires the ability to edit worklogs created by anyone rather than only the owner.

Log Work on Issues is required because adding or recording time against issues is controlled by the log work permission and Marina needs to create or add worklogs as part of updating entries.

Modify Personal Worklogs is incorrect because it only permits changes to the user’s own worklogs and does not allow editing other people’s worklogs.

Schedule Issues is incorrect because it relates to scheduling fields like start and due dates and it does not grant any capabilities to create, edit, or remove worklogs.

Remove Personal Worklogs is incorrect because it only allows a user to delete their own worklogs and not the worklogs of other team members which Marina needs to remove.

The correct answer is Assignees can attach files to their issues.

When you change a team-managed project from Open to Limited and do not add any users the project access becomes restricted but some issue level privileges for the assigned user remain. In this case the practical effect that applies to assignees is that Assignees can attach files to their issues which lets the person assigned to an issue add attachments even when broader project access is limited.

Reporters can no longer view their issues is incorrect because switching to Limited does not universally remove a reporter’s ability to see an issue in every team-managed configuration and there are issue level exceptions that affect visibility.

Only project members can view issues is incorrect because although Limited restricts general project access there are exceptions for users tied to individual issues such as reporters and assignees and the statement is too absolute for the specific assignee effect asked in the question.

Assignees can change issue rank is incorrect because changing issue rank is governed by board and project permissions and being the assignee does not automatically grant ranking privileges.

The correct answer is Change the board saved filter.

The board membership is defined by its saved filter and that filter uses JQL to select which issues appear on the board. If tasks older than six weeks are being excluded then the saved filter likely contains a date clause that limits results to a recent time window. Editing the board saved filter to remove or adjust that clause will allow all tasks to remain visible regardless of age.

Update quick filters is incorrect because quick filters only apply on top of the board view when a user toggles them. They do not permanently change which issues belong to the board and they will not cause automatic exclusion of issues by age.

Adjust the hide completed issues older than setting is incorrect because that setting only hides completed issues after a configured time period. It does not affect open or active tasks and therefore would not explain general disappearance of tasks older than six weeks.

Modify the board sub filter is incorrect because the sub filter is an additional restriction applied after the main saved filter and it is used for special exclusions. The primary set of issues is still controlled by the saved filter so the saved filter is the place to change to ensure all tasks remain on the board.

The correct statement is A board can have multiple administrators.

This is true because boards in Jira assign administration rights through the board settings and you can grant that administrator role to more than one user so multiple people can configure and manage the same board.

A Jira project can have multiple project leads is incorrect. A Jira project has a single project lead field, although you can assign many users to project roles or to project administrator permissions, the designated project lead itself is singular.

A saved filter can be owned by multiple users is incorrect. A saved filter has one owner who created or was assigned the filter, and filters are shared with users, groups, projects, or made public rather than having multiple owners.

The correct option is Adjust project permission scheme.

Adjust project permission scheme is correct because Jira grants edit and transition rights through a project permission scheme and the Edit Issues permission is controlled at that level. Maria can edit issues assigned to her because the current permission scheme likely grants those rights to the assignee role or a specific project role. Updating the project permission scheme or adding Maria to the appropriate project role or group will give her edit access to the other issues.

Modify global permissions is incorrect because global permissions control site wide administrative abilities and not the ability to edit individual issues in a specific project. Changing global permissions will not grant issue level Edit Issues rights for just this project.

Change issue security level is incorrect because issue security schemes control who can see or view an issue and not who can edit it. Altering the issue security level may affect visibility but it does not grant Edit Issues permission.

Contact Atlassian support is incorrect because this is a configuration task for a project admin or Jira administrator rather than a support case. Atlassian support will not change your project permission scheme for you as part of normal troubleshooting.

The correct answers are Subscription and Filters.

Filters are saved searches that define which issues match criteria such as blocker issues for a team. You create a filter that returns the blocker issues and then use the subscription feature to deliver that list on a regular cadence.

Subscription is the feature that sends scheduled emails of filter results. A subscription takes the results of a saved filter and sends a consolidated email on a schedule such as weekly to the chosen recipients.

Automation can run scheduled rules and perform actions that include sending notifications about specific issues, but it is not the standard, built in mechanism for sending a consolidated, recurring email of a filter result to a group.

Notifications are event driven and they notify users about changes to individual issues. They do not produce a weekly consolidated list of filter results as a subscription does.

The correct options are Merge versions and Delete version.

Using Merge versions Maya can move all issues from the old version into the target version and consolidate the two versions so the issues end up assigned to the desired release. This operation is intended to combine the contents of one version into another while removing the source version.

Using Delete version Maya can remove the unwanted version and choose where existing issues should be reassigned during the deletion process. The delete workflow offers the option to move issues to an existing version such as the target version before the source version is removed.

Release version is incorrect because that action only marks a version as released and does not move issues into another version or remove the version.

Archive version is incorrect because archiving hides the version to reduce clutter but does not reassign issues or merge them into another version.

Unrelease version is incorrect because it only changes the released status of a version and does not transfer issues to a different version.

Swimlanes is correct because it groups issues into horizontal lanes so you can separate work by project while still displaying all issues on the board.

Swimlanes create persistent lanes that can be configured by the Project field or by JQL so each lane represents a project and all lanes remain visible together. This makes it easy to compare and track work across multiple projects without excluding issues from the board.

Quick Filters are temporary filters used to narrow which issues are shown on the board. They do not create persistent grouped lanes and they may hide issues rather than grouping them while keeping everything visible.

Board Filter is a board level JQL that determines which issues appear on the board at all. It can exclude issues from the board and it does not organize visible issues into lanes by project.

The correct option is Modify the board sub-filter. Using the board sub-filter lets Maya update the board specific JQL so that issues resolved more than two days ago are excluded automatically from the company managed Kanban board.

The board sub-filter is applied in addition to the board filter and runs dynamically so no manual cleanup is needed. Maya can add a simple JQL condition that shows unresolved issues and resolved issues within the last two days. A common example is resolutiondate >= -2d OR resolution is EMPTY which will keep recent resolved items on the board and hide items resolved earlier than two days.

Adjust the board filter is incorrect because changing the main board filter affects the global set of issues returned by the board and can have wider impact. The main filter is not the lightweight way to hide only older resolved items on a board without affecting other uses of the filter.

Use the Hide completed issues older than setting is incorrect because that option is not the standard, low maintenance control for company managed Kanban boards and may apply only to specific views or team managed boards. It is not the general board level JQL control that reliably filters resolved issues by age on company managed boards.

Create a board automation rule to transition resolved issues off the board is incorrect because automation would require additional rules management and can change issue statuses or flows. That approach adds ongoing maintenance and possible side effects, while the board sub-filter accomplishes the requirement through JQL without changing issue history or workflow.

The correct answer is Cumulative flow diagram.

A Cumulative flow diagram displays the number of issues in each workflow state as stacked bands over time and it makes it easy to see how work in progress changes and where issues accumulate during a period such as three weeks.

Control chart is incorrect because it shows cycle time and process variability rather than counts of issues in each workflow state. It helps analyze how long work items take to complete and not the distribution of work across states.

Burndown chart is incorrect because it tracks remaining work or scope over time for a sprint and it plots work left rather than the count of issues by state. It does not show state bands or stacking by workflow stage.

Velocity chart is incorrect because it shows the amount of work completed per iteration such as story points per sprint and it summarizes throughput rather than showing counts of issues in each workflow state over time.

The correct option is Site administrator.

Site administrator can add and manage users across the organization and grant access to company applications and billing features. This role controls site level user management and billing settings which matches Alyssa’s duties to add a new Jira account and manage billing access.

Jira Software user is incorrect because this role only provides regular product access for using Jira Software and it does not include permissions to manage other users or billing.

Jira administrator is incorrect because that role focuses on product configuration and global settings within Jira rather than organization wide user and billing management. A Jira administrator may manage schemes and permissions but they do not necessarily control billing or product access across the entire site.

Project administrator is incorrect because it grants permissions only at the project level. Project admins can change project settings and manage project roles but they cannot add users across the site or manage billing.

Swimlanes is correct.

Swimlanes divide a Jira board into horizontal lanes so you can place a specific group of issues in a top lane and have other issues appear in lanes below. You can configure swimlanes by JQL queries, by assignee, by epic or by other criteria so platform tickets can be shown in their own lane above the rest.

Quick Filters are wrong because they apply temporary filters to the board to hide or show issues on demand and they do not create persistent horizontal lanes.

Issue Detail View is wrong because it only shows the fields and history for a selected issue in a side panel or dialog and it does not change the board layout or group issues into rows.

Board Filter is wrong because it defines which issues are included on the board using JQL and it restricts the issue set rather than arranging included issues into horizontal lanes.

Workflow post functions and Automation rule are correct.

Workflow post functions run during a workflow transition and they can update issue fields as part of that transition. If a post function on the transition into the QA status was configured to assign the issue to Priya then every issue that moves into QA will be reassigned automatically.

Automation rule can trigger on events such as a status change and then perform actions like assigning an issue. A rule scoped to the project or to the instance that watches for the QA status and assigns Priya will produce the observed behavior.

Components usually control component leads and can influence assignment at creation when the component lead is chosen. They do not by themselves reassign issues when the status changes to QA unless combined with an automation or workflow step.

Project default assignee is a fallback for newly created issues or for unassigned issues. It does not trigger reassignment on a status transition by itself.

Global automation rule is misleading as listed here. Global automation rules do exist but the general category of Automation rule is the relevant cause and the specific phrasing in this option is not the intended answer.

Workflow validators run checks before a transition to decide if the transition is allowed. Validators do not change issue fields or assign users so they cannot cause the reassignment on their own.

The correct options are Issue Type Scheme, Workflow Scheme, and Screen Scheme.

The Issue Type Scheme is provisioned per company managed project so the project can define its own set and ordering of issue types without changing other projects.

The Workflow Scheme is created for the project to allow project specific workflows and transitions so teams can customize process states without impacting other projects.

The Screen Scheme is also provisioned uniquely so the project can control which screens appear on create view edit and transition screens for its issue types.

The Notification Scheme is incorrect because notification schemes are typically shared and reused across projects rather than being automatically created as unique for each company managed project.

The Field Configuration Scheme is incorrect because field configuration schemes are commonly applied to multiple projects and are not necessarily provisioned uniquely per company managed project.

Clearing a parent issue from the board also clears its subtasks regardless of each subtask’s status and You can create multiple issues at once by pasting several lines into the create box on the board are correct.

The first correct behavior means that on team-managed boards the board action that clears or removes a parent issue will also clear its subtasks on the board view even if those subtasks are in different statuses. This is a board level behavior in team-managed projects and it applies regardless of each subtask’s individual status.

The second correct behavior refers to the board create box which accepts multiple lines of text and creates one issue per line. This allows quick bulk creation directly from the board by pasting several lines into the create box and submitting them.

The issue navigator cannot be turned on or used in team-managed projects is incorrect because you can use the global issue search and issue navigator to find and filter issues from team-managed projects. The issue navigator remains available in Jira Cloud even though some project settings differ between project types.

You can set a project wide default issue security level in a team-managed project is incorrect because issue security schemes and project wide default security levels are features of company managed projects. Team-managed projects do not support configuring issue security at the project scheme level.

In a scrum template team-managed project you can create issues directly from any board column even when sprints are active is incorrect because when sprints are active the board behavior for creating and placing new issues is restricted. New issues typically need to be added in ways that align with the active sprint workflow and you cannot freely create them into any column while the sprint is running.

The correct option is Board sub filter.

Board sub filter is an additional JQL that runs on top of the main board filter so it will remove matching issues from the Kanban board. This setting is applied at the board level and is used to permanently exclude certain issues from appearing on the board.

Quick filter is incorrect because quick filters are user facing toggles that temporarily narrow the visible issues on a board. They do not permanently prevent issues from appearing and they are intended for ad hoc views rather than board level exclusion.

Issue level security is incorrect because issue level security controls who can see an issue based on security schemes and permissions. It is not a board configuration that excludes issues by JQL so it does not serve as the board setting asked about.

Columns is incorrect because columns only map statuses to columns and determine where issues appear once they are on the board. Columns do not exclude issues that match the board filter from appearing on the board.

Project roles is the correct option for Maya to add to the project permission scheme.

Project roles provide a per project, role based way to grant permissions that maps responsibilities to people or groups. You can assign users or groups to a role and then give that role the appropriate permissions in the permission scheme which makes it simple to change who can perform actions as the team changes.

Individual users is incorrect because granting permissions directly to single users does not scale and forces administrators to update permissions for each person when membership changes. Permission schemes are meant to use roles or groups rather than binding permissions to individual accounts.

Groups is incorrect because groups are global and do not provide the same per project mapping of responsibilities. Groups can be used but Project roles are preferable when you need flexible, per project assignment of who can perform actions.

The correct option is Board sub-filter.

Board sub-filter lets you add a JQL clause that automatically limits which issues appear on the Kanban board while the board continues to use its main filter for reports. This means the board view can show only issues with the finance component and the Cumulative Flow Diagram and other reports remain based on the main board filter and are not changed by the sub-filter.

Board Filter is incorrect because changing the main board filter to only include the finance component would affect both the board and the reports. The main filter is what reports like the Cumulative Flow Diagram use to compute their results.

Quick Filters is incorrect because quick filters are user toggles that you must apply manually and they do not automatically change the default board view for all users. Quick filters also do not alter the underlying filter that reports use.

Issue Detail View is incorrect because it only displays information about a selected issue and does not filter which issues appear on the board or change report results.

The correct answer is Control chart.

A Control chart visualizes cycle time and lead time and shows the distribution of how long issues take to move through the workflow. It is designed to show how long a single issue or a group of issues has been sitting in a given status and to highlight variation and outliers that indicate delays.

The Velocity chart reports completed work per sprint and helps with forecasting future sprint capacity. It does not measure how long issues sit in a particular status.

The Issue age report shows how long issues have been open or unresolved since creation or since they entered a board. It does not provide the per-status time distribution and cycle time detail that a control chart provides.

The Cumulative flow diagram shows the count of issues in each status over time to reveal bottlenecks and workflow stability. It does not display the time each issue spends in a given status or the distribution of those times.

The Burndown chart tracks remaining work in a sprint or release and is focused on scope and progress rather than the amount of time issues spend in specific statuses.