ACP-120學習指南： Jira Cloud Administrator，最快的通過考試方式是選擇我們現在IT行业競爭越來越激烈，通過ATLASSIAN ACP-120認證考試可以有效的帮助你在现在这个竞争激烈的IT行业中稳固和提升自己的地位。在我們VCESoft中你可以獲得關ATLASSIAN ACP-120認證考試的培訓工具。我們VCESoft的IT精英團隊會及時為你提供準確以及詳細的關ATLASSIAN ACP-120認證考試的培訓材料。通過我們VCESoft提供的學習材料以及考試練習題和答案，我們VCESoft能確保你第一次參加ATLASSIAN ACP-120认证考试時挑戰成功，而且不用花費大量時間和精力來準備考試。 最新的 Jira Administrator ACP-120 免費考試真題 (Q40-Q45):問題 #40
Two users have access to the same filter and see the same issues in a company-managed project. One of them can perform a bulk operation to watch issues in the filter, but the other user cannot. What should you investigate?
A. Product access
B. Project roles
C. Project permissions
D. Groups
E. Default user preferences
答案：C
解題說明：
The scenario describes two users who can view the same issues in a filter (indicating they have theBrowse Projectspermission), but only one can perform a bulk operation towatchissues. The ability to watch issues is controlled by theView Issue WatchersandManage Watcher Listpermissions in the project's permission scheme. Therefore, you should investigateproject permissions(Option A).
* Explanation of the Correct Answer (Option A):
* Performing a bulk operation to watch issues requires theManage Watcher Listpermission, which allows users to add themselves or others as watchers to an issue. Since both users can see the issues (via the filter), they likely have theBrowse Projectspermission, but the user who cannot perform the bulk operation may lack theManage Watcher Listpermission.
* Exact Extract from Documentation:
Manage Watcher List permission
TheManage Watcher Listpermission allows users to add or remove watchers from an issue, including via bulk operations. This permission is granted via the project's permission scheme.
Note: To view the watcher list, users also need theView Issue Watcherspermission. Both permissions are required to perform actions like bulk watching issues.
To check permissions:
* Go toProject settings > Permissions.
* Review theManage Watcher ListandView Issue Watcherspermissions to see which users, groups, or roles have them.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: The difference in the users' ability to perform the bulk watch operation is most likely due to a difference in theirManage Watcher Listpermission, which is defined in the project's permission scheme. Investigating project permissions will reveal whether the second user lacks this permission.
* Why Other Options Are Incorrect:
* Product access (Option B):
* Product access determines whether users can use Jira Software. Both users can view the filter and issues, indicating they have product access. Product access does not control specific permissions like managing watchers.
* Extract from Documentation:
Manage product access
Product access grants users the ability to use Jira products. Specific actions, like managing watchers, are controlled by project or global permissions, not product access.
(Source: Atlassian Support Documentation, "Manage product access")
* Groups (Option C):
* Groups may be used in permission schemes to grant permissions, but the root cause is the permission itself, not the group membership. Investigating groups might be a secondary step after checking project permissions, butproject permissionsis the more direct answer.
* Extract from Documentation:
Groups are used in permission schemes to grant permissions to multiple users. To determine why a user lacks a permission, check the permission scheme first, then verify group membership if relevant.
(Source: Atlassian Support Documentation, "Manage groups")
* Default user preferences (Option D):
* Default user preferences (e.g., notification settings) control whether a user receives notifications for watched issues, not their ability to watch issues.The issue is about performing a bulk operation, not receiving notifications.
* Extract from Documentation:
Manage user preferences
Users can manage their notification preferences inPersonal settings > Email notifications. These settings affect notification delivery, not the ability to perform actions like watching issues.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails")
* Project roles (Option E):
* Project roles are used in permission schemes to grant permissions. Like groups, roles are a means to assign permissions, but the issue lies in the permission itself (Manage Watcher List). Investigating project permissions directly addresses the root cause.
* Extract from Documentation:
Project roles are used in permission schemes to grant permissions likeManage Watcher List. Check the permission scheme to identify the root cause of permission differences.
(Source: Atlassian Support Documentation, "Manage project roles")
* Additional Notes:
* Both users can see the filter and issues, so they likely have theBrowse Projectspermission. The difference in their ability to perform the bulk watch operation points to theManage Watcher List permission, which should be checked inProject settings > Permissions.
* If the permission is granted to a group or role, verify the users' membership in those groups or roles as a follow-up step.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage groups
Atlassian Support Documentation:Manage your Jira notification emails
Atlassian Support Documentation:Manage project roles
問題 #41
Two projects share all their schemes. Which two configuration changes would impact both projects?
A. Archiving a version
B. Adding a new field to a screen
C. Removing shortcuts
D. Updating the project category
E. Adding a new component
F. Making the Assignee required
答案：B,F
解題說明：
When two projects in Jira Software Cloud share all their schemes (e.g., issue type scheme, workflow scheme, screen scheme, field configuration scheme, permission scheme, notification scheme), any changes to these shared schemes will impact both projects. The two configuration changes that would affect both projects are adding a new field to a screen(Option A) andmaking the Assignee required(Option C), as these involve modifications to shared schemes.
* Explanation of the Correct Answers:
* Adding a new field to a screen (Option A):
* Screens in Jira are associated with projects through ascreen scheme, which maps screens to issue operations (e.g., Create, Edit, View) for specific issue types. If two projects share the same screen scheme, adding a new field to a screen (e.g., a custom field or system field) will affect all projects using that screen scheme, as the field will appear on the screen for the corresponding operation.
* Exact Extract from Documentation:
Configure screens
Screens define which fields are displayed during issue operations (Create, Edit, View). Screens are associated with issue types via a screen scheme, and multiple projects can share the same screen scheme.
To add a field to a screen:
* Go toSettings > Issues > Screens.
* Select the screen and add the field.Impact: Adding a field to a screen affects all projects using the same screen scheme, as the field will appear for the associated issue types and operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Why This Fits: Since the projects share all schemes, including the screen scheme, adding a field to a screen will impact both projects by altering the issue creation, editing, or viewing experience.
* Making the Assignee required (Option C):
* Making theAssigneefield required involves modifying thefield configurationwithin afield configuration scheme. The field configuration determines whether a field is required, optional, or hidden. If two projects share the same field configuration scheme, making the Assignee field required will affect both projects, as issues in both projects will require an assignee to be set.
* Exact Extract from Documentation:
Configure field settings
Field configurations define the behavior of fields (e.g., required, optional, hidden) for specific issue types. A field configuration scheme maps field configurations to issue types, and multiple projects can share the same scheme.
To make a field required:
* Go toSettings > Issues > Field configurations.
* Select the field configuration and mark the field (e.g., Assignee) asRequired.Impact:
Changes to a field configuration affect all projects using the associated field configuration scheme.(Source: Atlassian Support Documentation, "Configure field settings")
* Why This Fits: Since the projects share the field configuration scheme, making the Assignee required will enforce this rule in both projects, impacting their issue creation and editing processes.
* Why Other Options Are Incorrect:
* Adding a new component (Option B):
* Components are project-specific and configured inProject settings > Components.
Adding a component to one project does not affect another project, even if they share schemes, as components are not part of any shared scheme.
* Extract from Documentation:
Manage components
Components are unique to each project and configured inProject settings > Components. They are not shared via schemes, so changes to components in one project do not affect others.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Removing shortcuts (Option D):
* Shortcuts (project-specific links to external resources) are configured inProject settings > Shortcutsand are unique to each project. Removing shortcuts in one project does not impact another project, regardless of shared schemes.
* Extract from Documentation:
Manage project shortcuts
Shortcuts are project-specific links to external resources, configured inProject settings > Shortcuts. Changes to shortcuts in one project do not affect other projects.
(Source: Atlassian Support Documentation, "Manage project settings")
* Updating the project category (Option E):
* The project category is a project-specific attribute set inProject settings > Details.
Changing the project category for one project does not affect another project, even if they share schemes, as categories are not tied to schemes.
* Extract from Documentation:
Change project details
The project category is set inProject settings > Detailsand is unique to each project. It does not impact schemes or other projects.
(Source: Atlassian Support Documentation, "Manage project settings")
* Archiving a version (Option F):
* Versions are project-specific and managed inProject settings > Releases. Archiving a version in one project does not affect another project, as versions are not part of shared schemes.
* Extract from Documentation:
Manage versions
Versions are project-specific and configured inProject settings > Releases. Archiving a version affects only the project it belongs to, not other projects, even if they share schemes.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Additional Notes:
* Shared schemes ensure consistency across projects, but they also mean that changes to schemes (e.g., screens, field configurations) have a broad impact. Project admins must coordinate with Jira admins to modify schemes, as these changes require system-level permissions.
* Project-specific settings like components, shortcuts, categories, and versions allowfor customization without affecting other projects.
:
Atlassian Support Documentation:Configure screens in Jira Cloud
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Manage project settings
Atlassian Support Documentation:Manage versions in company-managed projects
問題 #42
A project lead wants to conduct historical trend analysis, but she is worried that older issues are being updated in a way that inhibits their comparison. She wants to take a snapshot of the data in her project at regular intervals so she can compare different periods.
Which tool will help meet this need?
A. Backup Jira data
B. JQL Results Snapshot
C. Project Export
D. Issue Filter Export to CSV
答案：D
問題 #43
A company-managed project uses a single workflow for two issue types: Blogs and Ideas. Youreceived several new requirements. To satisfy one of them, you must create a second workflow. Identify that requirement.
A. Blogs should allow reopening after they are closed, but not Ideas.
B. Blogs should be sent to the project lead each Friday, but not Ideas.
C. Blogs should be auto-closed after 3 days, but not Ideas.
D. Blogs should be editable after they are closed, but not Ideas.
答案：A
解題說明：
In a company-managed project, a single workflow can be shared across multiple issue types (e.g., Blogs and Ideas) via aworkflow schemethat maps workflows to issue types. To satisfy a requirement that necessitates a second workflow, the requirement must involve workflow-specific differences that cannot be handled within a single workflow. The requirement thatBlogs should allow reopening after they are closed, but not Ideas (Option D) requires a second workflow, as reopening involves a transition that must be present for Blogs but absent for Ideas.
* Explanation of the Correct Answer (Option D):
* The requirement to allowBlogsto be reopened after being closed, but notIdeas, means the workflow for Blogs must include a transition from theClosedstatus to an open status (e.g.,Openor Reopened), while the workflow for Ideas must not include this transition. In a single workflow, transitions apply to all issue types using that workflow, so it is impossible to have a transition for Blogs but not Ideas. Therefore, a second workflow is needed: one for Blogs (with a reopen transition) and one for Ideas (without a reopen transition). These workflows can be assigned to the respective issue types via the project'sworkflow scheme.
* Exact Extract from Documentation:
Configure workflows in company-managed projects
Workflows define statuses and transitions for issues. A workflow scheme maps workflows to issue types in a project.
To use different workflows for different issue types:
* Create separate workflows (e.g., one for Blogs with a reopen transition, one for Ideas without).
* Go toSettings > Issues > Workflow schemes.
* Edit the project's workflow scheme to assign the appropriate workflow to each issue type (e.g., Blogs to Workflow A, Ideas to Workflow B).Note: A single workflow applies the same transitions to all issue types it governs. To have different transitions (e.g., reopening for Blogs but not Ideas), use separate workflows.(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Why This Fits: The need for a reopen transition for Blogs but not Ideas requires distinct workflows, as a single workflow cannot differentiate transitions by issue type, making Option D the correct answer.
* Why Other Options Are Incorrect:
* Blogs should be auto-closed after 3 days, but not Ideas (Option A):
* Auto-closing issues after 3 days can be achieved using aJira automation rule(e.g., a scheduled rule that transitions Blogs toClosedbased on a time condition). This does not require a workflow change, as the transition toClosedcan exist in a shared workflow, and the automation rule can filter by issue type (Blogs).
* Extract from Documentation:
Use Jira automation to transition issues based on time conditions (e.g., close Blogs after 3 days). Filter by issue type to exclude Ideas. This does not require separate workflows.
(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")
* Blogs should be editable after they are closed, but not Ideas (Option B):
* Editability after closing is controlled by theEdit Issuespermission and workflow properties (e.g., jira.issue.editable). A workflow property can be set on theClosedstatus to allow editing for Blogs but not Ideas, or a separatefield configuration schemecan make fields read-only for Ideas. This can be managed without a second workflow.
* Extract from Documentation:
Use workflow properties (e.g., jira.issue.editable=true) or field configuration schemes to control editability by issue type. Separate workflows are not required.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Blogs should be sent to the project lead each Friday, but not Ideas (Option C):
* Sending issues to the project lead each Friday can be handled with aJira automation rule (e.g., a scheduled rule that sends an email or creates a task for Blogs). This is independent of the workflow, as it involves notifications or actions, not status transitions.
* Extract from Documentation:
Use Jira automation to send notifications or tasks for specific issue types (e.g., Blogs) on a schedule (e.g., every Friday). This does not require workflow changes.
(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")
* Additional Notes:
* Creating a second workflow requiresJira administratorprivileges to modify workflows ( Settings > Issues > Workflows) and update the workflow scheme (Project settings > Workflows).
* The workflow scheme can assign different workflows to Blogs and Ideas, ensuring the reopen transition is only available for Blogs.
* Options A, B, and C can be addressed with automation or other configurations, but Option D fundamentally requires distinct workflows due to the transition difference.
:
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Automate your Jira Cloud instance
問題 #44
Currently, the 'Affects Version/s' field is populated on issues in a particular company-managed project. Now, you want to hide it when viewing issues and to hide its values when viewing filter results. Where would you go to make the change?
A. Screen
B. Issue layout
C. Issue detail view
D. Field configuration
E. Custom field context
答案：B
解題說明：
To hide theAffects Version/sfield when viewing issues and in filter results in a company-managed project, you need to configure theissue layout(Option E). The issue layout determines which fields are displayed or hidden in the issue view and affects how fields appear in filter results.
* Explanation of the Correct Answer (Option E):
* Theissue layoutin a company-managed project controls the visibility and arrangement of fields in the issue view (when viewing an issue) and influences how fields are displayed in filter results (e.
g., in issue navigator or boards). To hide theAffects Version/sfield, you can move it to the Hidden fieldssection in the issue layout. This ensures the field is not shown in the issue view or filter results, even if it contains values.
* Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts define which fields are displayed, hidden, or placed in the context panel when viewing issues.
They also influence field visibility in filter results.
To hide a field:
* Go toProject settings > Issue layout.
* Select the issue type or screen to configure.
* Move the field (e.g., Affects Version/s) to theHidden fieldssection.Note: Hiding a field in the issue layout does not remove it from screens used for Create or Edit operations, but it prevents it from appearing in the issue view and filter results.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Why This Fits: Theissue layoutdirectly controls field visibility in the issue viewand filter results, making it the correct place to hide theAffects Version/sfield, satisfying both requirements.
* Why Other Options Are Incorrect:
* Issue detail view (Option A):
* Theissue detail viewis part of the issue view interface and is not a configuration setting. It is affected by the issue layout but cannot be directly modified to hide fields.
* Extract from Documentation:
The issue detail view displays fields based on the issue layout configuration. To hide fields, configure the issue layout inProject settings > Issue layout.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Field configuration (Option B):
* Field configurationscontrol whether fields are required, optional, or hidden for specific issue types. Hiding a field in a field configuration removes it from all operations (Create, Edit, View), which would preventAffects Version/sfrom being populated at all. The requirement is to hide the field only when viewing and in filter results, not to remove it entirely, so field configuration is not suitable.
* Extract from Documentation:
Hiding a field in a field configuration removes it from all screens and operations. Use issue layouts to hide fields in the issue view and filter results.
(Source: Atlassian Support Documentation, "Configure field settings")
* Custom field context (Option C):
* Custom field contextsdefine the options and default values for a custom field across projects or issue types. TheAffects Version/sfield is a system field, not a custom field, and contexts do not control field visibility in the issue view or filter results.
* Extract from Documentation:
Custom field contexts apply to custom fields and manage options, not visibility. System fields likeAffects Version/sare not affected by contexts.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Screen (Option D):
* Screensdetermine which fields appear during issue operations (Create, Edit, View).
RemovingAffects Version/sfrom a screen would affect Create or Edit operations, not just viewing, and would not specifically hide the field in filter results. The issue layout is the correct place for view-specific changes.
* Extract from Documentation:
Screens control fields for Create, Edit, and View operations. To hide fields in the issue view and filter results, use the issue layout.
(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Additional Notes:
* Configuring the issue layout requiresproject adminprivileges and is done inProject settings > Issue layout.
* HidingAffects Version/sin the issue layout does not remove its values from the database; it only prevents display in the issue view and filter results.
* Ensure the field remains on relevant screens for Create/Edit if it needs to continue being populated.
:
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure screens in Jira Cloud