ATLASSIAN ACP-120最新試験 & ACP-120関連受験参考書

我々の提供するATLASSIANのACP-120試験の資料のどのバーションでも各自のメリットを持っています。PDF版はパソコンでもスマホでも利用でき、どこでも読めます。ネットがあれば、オンライン版はどの電子商品でも使用できます。ソフト版は真実のATLASSIANのACP-120試験の環境を模倣して、あなたにATLASSIANのACP-120試験の本当の感覚を感じさせることができ、いくつかのパソコンでも利用できます。

ATLASSIAN ACP-120：Jira Cloud Administrator Examは、自宅またはオフィスからオンラインで受験できる監視された試験です。試験は複数選択問題から構成され、合格点は65％です。試験費用は350米ドルで、認定は2年間有効です。

ATLASSIAN ACP-120（Jira Cloud Administrator）認定試験は、Jira Cloudの管理と運用に責任を持つプロフェッショナル向けに設計された業界標準の認定です。この認定は、プロジェクト、チーム、ワークフローを管理するためのツールやソフトウェア製品を提供する、主要なソフトウェア開発会社であるATLASSIANが提供しています。

>> ATLASSIAN ACP-120最新試験 <<

ACP-120関連受験参考書、ACP-120テストトレーニング

ACP-120学習教材は、試験にすばやく合格し、希望する証明書を取得するのに役立ちます。その後、あなたは良い仕事を得るためにもう一つのチップを持っています。 ACP-120学習教材を使用すると、より高い出発点に立って、ACP-120試験に他の人よりも一歩早く合格し、他の人よりも早くチャンスを活用できます。このペースの速い社会では、あなたの時間はとても貴重です。 1人の力だけに頼る場合、あなたが優位に立つことは困難です。 ACP-120の学習に関する質問は、最も満足のいくアシスタントになります。

ATLASSIANのACP-120（Jira Cloud Administrator）試験は、Jira Cloudの管理におけるスキルと知識を検証したいプロフェッショナル向けに設計されています。Jiraは、さまざまな業界の組織でプロジェクトを計画、追跡、管理するために使用される人気のあるプロジェクト管理ツールです。Jira Cloudの管理者として、組織のニーズに合わせてJiraを設定およびカスタマイズし、ユーザーと権限を管理し、システムのスムーズな機能を確保する責任があります。

ATLASSIAN Jira Cloud Administrator 認定 ACP-120 試験問題 (Q40-Q45):

質問 # 40
Requirements for field behavior in a company-managed project are shown:
Issue Type
Attribute (custom field)
Epic
Hidden
Story
Optional
Bug
Required
What do you need to configure to meet the requirements?

A. Field configurations
B. Screens
C. Custom field contexts
D. Screen schemes

正解：A

解説：
To meet the requirements for theAttributecustom field's behavior (hidden for Epics, optional for Stories, required for Bugs) in a company-managed project, you need to configurefield configurations(Option A).
Field configurations define whether a field is required, optional, or hidden for specific issue types.
* Explanation of the Correct Answer (Option A):
* Field configurationscontrol the behavior of fields (e.g., required, optional, hidden) for different issue types in a company-managed project. To meet the requirements:
* ForEpics, set theAttributefield toHidden.
* ForStories, set theAttributefield toOptional(not required).
* ForBugs, set theAttributefield toRequired.
* This is achieved by creating multiple field configurations (one for each issue type's behavior) and associating them with afield configuration schemethat maps configurations to issue types.
* Exact Extract from Documentation:
Configure field settings
Field configurations define whether fields are required, optional, or hidden for specific issue types. A field configuration scheme maps field configurations to issue types in a project.
To configure:
* Go toSettings > Issues > Field configurations.
* Create or edit field configurations (e.g., one for Epics, Stories, Bugs).
* For each configuration:
* Mark a field asRequiredto enforce a value.
* Mark a field asHiddento remove it from screens.
* Leave a field asOptional(default) if not required.
* Create a field configuration scheme (Settings > Issues > Field configuration schemes) and map configurations to issue types.
* Assign the scheme to the project inProject settings > Fields.Example: Hide a field for Epics, make it optional for Stories, and required for Bugs.(Source: Atlassian Support Documentation, "Configure field settings")
* Why This Fits:Field configurationsallow you to set theAttributefield as hidden, optional, or required for different issue types, directly meeting the requirements.
* Why Other Options Are Incorrect:
* Screens (Option B):
* Screens define which fields appear during issue operations (e.g., Create, Edit, View). While hiding a field on a screen for Epics could make it appear hidden, screens are not issue type- specific unless combined with ascreen scheme. Screens also cannot enforcerequiredor optionalbehavior, which is handled by field configurations.
* Extract from Documentation:
Screens control which fields are displayed but do not manage required or optional behavior. Use field configurations for field behavior.
(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Custom field contexts (Option C):
* Custom field contexts define the options and default values for a custom field across projects or issue types. They do not control whether a field is hidden, optional, or required, which is managed by field configurations.
* Extract from Documentation:
Custom field contexts set options and defaults for fields, not their visibility or required status. Use field configurations for behavior.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Screen schemes (Option D):
* Screen schemes map screens to issue operations (e.g., Create, Edit) for issue types. They control which fields appear on screens but do not manage whether fields are required or optional, which is handled by field configurations.
* Extract from Documentation:
Screen schemes assign screens to issue types but do not control field behavior like required or hidden. Use field configurations for this.
(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")
* Additional Notes:
* Steps to configure:
* Create three field configurations inSettings > Issues > Field configurations:
* Epic: SetAttributetoHidden.
* Story: SetAttributetoOptional.
* Bug: SetAttributetoRequired.
* Create a field configuration scheme inSettings > Issues > Field configuration schemes and map each configuration to the respective issue type (Epic, Story, Bug).
* Assign the scheme to the project inProject settings > Fields.
* Configuring field configurations requiresJira administratorprivileges.
* Ensure theAttributecustom field is included on the relevant screens (except for Epics, where it is hidden) to avoid conflicts.
:
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Configure screens in Jira Cloud
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure screen schemes in Jira Cloud

質問 # 41
You are configuring an issue type screen in a team-managed project. Which statement is true?

A. You can reuse a custom field from another team-managed project.
B. You can add any field type to the Description fields section.
C. You can add any field type to the Context fields section.
D. You can edit the name of any field on the screen.
E. You can reorder custom fields within all sections of the screen.

正解：E

解説：
In a team-managed project, theissue type screen(configured inProject settings > Issue types) determines which fields are displayed for an issue type and how they are organized (e.g., in sections like Description or Context fields). The true statement is thatyou can reorder custom fields within all sections of the screen (Option E), as team-managed projects allow flexible reordering of fields within their designated sections.
* Explanation of the Correct Answer (Option E):
* In team-managed projects, the issue type screen is configured per issue type, and fields (including custom fields) are organized into sections (e.g., Description fields, Context fields). Users with appropriate permissions (e.g., project admins) can reorder custom fields within any section of the screen to customize the layout, ensuring fields appear in the desired order for creation, editing, or viewing.
* Exact Extract from Documentation:
Configure issue types in team-managed projects
Each issue type in a team-managed project has its own screen configuration, defining which fields are displayed and their order.
To reorder fields:
* Go toProject settings > Issue types.
* Select the issue type and edit its screen.
* Drag and drop fields (including custom fields) within sections (e.g., Description fields, Context fields) to reorder them.Note: Custom fields can be reordered within any section of the screen, but some system fields have fixed positions.(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
* Why This Fits: The ability to reorder custom fields within all sections of the issue type screen is a standard feature in team-managed projects, making Option E the true statement.
* Why Other Options Are Incorrect:
* You can edit the name of any field on the screen (Option A):
* In team-managed projects, you cannot edit the name of fields directly on the screen configuration. Custom field names are set when the field is created (Project settings > Project fields), and system field names (e.g., Summary, Description) are fixed. The screen configuration only allows adding, removing, or reordering fields, not renaming them.
* Extract from Documentation:
Field names are set inProject settings > Project fieldsfor custom fields or are fixed for system fields. Screen configurations do not allow renaming fields.
(Source: Atlassian Support Documentation, "Manage fields in team-managed projects")
* You can reuse a custom field from another team-managed project (Option B):
* Custom fields in team-managed projects are project-specific and cannot be reused across projects, unlike company-managed projects where global custom fields are shared. To use a similar field, you must create a new custom field in the project.
* Extract from Documentation:
Custom fields in team-managed projects are unique to the project and cannot be reused from other team- managed projects.
(Source: Atlassian Support Documentation, "Manage fields in team-managed projects")
* You can add any field type to the Context fields section (Option C):
* TheContext fieldssection (right panel in the issue view) has restrictions on which field types can be added. System fields likeSummary,Description, and certain others are fixed in the main section and cannot be moved to the Context fields section. Only eligible fields (e.g., custom fields, Labels, Components) can be added to this section.
* Extract from Documentation:
TheContext fieldssection is limited to certain field types (e.g., custom fields, Labels). Core fields like Summary and Description cannot be moved to Context fields.
(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
* You can add any field type to the Description fields section (Option D):
* TheDescription fieldssection (main section below the Summary) also has restrictions.
Fields likeSummary,Issue Type, andStatusare fixed in their positions, and not all field types can be added to the Description fields section. Only certain fields (e.g., Description, custom text fields) are eligible.
* Extract from Documentation:
TheDescription fieldssection is for fields like Description or custom text fields. Some system fields have fixed positions and cannot be moved.
(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
* Additional Notes:
* Configuring issue type screens requiresproject adminprivileges in a team-managed project ( Project settings > Issue types).
* Reordering fields enhances usability by prioritizing important fields in each section.
* System fields may have limited reordering options compared to custom fields.
:
Atlassian Support Documentation:Configure issue types in team-managed projects Atlassian Support Documentation:Manage fields in team-managed projects

質問 # 42

What is being transitioned in the last component of the rule?

A. A single story
B. An epic
C. The trigger issue
D. One or more sub-tasks
E. Multiple stories

正解：C

解説：
The automation rule in the SCRUM project triggers when an issue is transitioned, checks if an Epic exists, and includes a Related issues condition that evaluates whether Stories (or other issues in this Epic) exist. The question asks what is being transitioned in the last component of the rule. Based on the rule structure, the last component is the Related issues condition, which does not perform a transition- it only checks a condition. However, interpreting the question in the context of the entire rule, the trigger issue (Option D) is the issue being transitioned in the initial When: Issue transitioned component, and subsequent components (like conditions) do not introduce new transitions unless explicitly stated (e.g., via an action).
* Explanation of the Correct Answer (Option D):
* The rule structure is:
* When: Issue transitioned: This is the trigger, meaning the rule runs when an issue (the trigger issue) is transitioned to a new status in the workflow.
* If: Epic exists: This condition checks if the trigger issue is associated with an Epic (e.
g., it's an Epic itself or a Story linked to an Epic).
* Related issues condition: Stories (or other issues in this Epic): This condition checks if there are Stories (or other issues) related to the Epic associated with the trigger issue.
* The last component shown is the Related issues condition, which does not perform a transition-it only evaluates whether Stories exist in the Epic. However, the question likely intends to ask about the issue being transitioned in the overall rule context. The When:
Issue transitioned trigger indicates that the trigger issue is the one undergoing the transition that initiates the rule.
* Since the rule does not yet include an action (e.g., transitioning related issues), the only issue being transitioned in the rule's execution is the trigger issue-the issue that was transitioned to activate the rule.
* Exact Extract from Documentation:
Jira automation components
Automation rules act on the trigger issue by default, which is the issue that activates the rule (e.g., the issue transitioned for an Issue Transitioned trigger).
* Conditions like Related issues condition check for related issues (e.g., Stories in an Epic) but do not transition issues unless an action is specified.
* Actions like Transition issue apply to the trigger issue or related issues if specified (e.
g., via a branch).Note: Without a branch or action, the rule does not transition additional issues beyond the trigger.(Source: Atlassian Support Documentation,
"Automate your Jira Cloud instance")
* Why This Fits: The trigger issue is the issue being transitioned in the When: Issue transitioned component, and the Related issues condition does not introduce a new transition. Thus, the trigger issue (Option D) is the issue being transitioned in the rule's context.
* Why Other Options Are Incorrect:
* A single story (Option A):
* The Related issues condition checks for Stories in the Epic but does nottransition them-it only evaluates their existence. The rule does not yet include an action to transition a single Story, and the trigger issue (being transitioned) is not specified as a Story (it could be an Epic or another issue type).
* Extract from Documentation:
The Related issues condition evaluates related issues but does not transition them unless an action (e.g., Transition issue) is specified.
(Source: Atlassian Support Documentation, "Jira automation conditions")
* Multiple stories (Option B):
* Similar to Option A, the rule does not transition multiple Stories. The Related issues condition only checks for Stories in the Epic, and no action is shown to transition them. The trigger issue is the one being transitioned.
* Extract from Documentation:
Transitioning multiple issues requires a branch (e.g., For Stories) and a Transition issue action, which is not present in the rule.
(Source: Atlassian Support Documentation, "Jira automation actions")
* An epic (Option C):
* The If: Epic exists condition checks for an Epic, but the trigger issue (being transitioned) could be any issue type (e.g., an Epic, Story, or Task). The rule does not specify that the trigger issue is an Epic, so this is not definite.
* Extract from Documentation:
The Issue Transitioned trigger applies to any issue type, not specifically Epics, unless filtered by a condition (e.g., Issue Type = Epic).
(Source: Atlassian Support Documentation, "Jira automation triggers")
* One or more sub-tasks (Option E):
* The rule does not mention Sub-tasks; the Related issues condition focuses on Stories in the Epic. There is no branch or action to transition Sub-tasks, and the trigger issue is the one being transitioned.
* Extract from Documentation:
To transition Sub-tasks, use a branch like For Sub-tasks with a Transition issue action, which is not present in the rule.
(Source: Atlassian Support Documentation, "Jira automation actions")
* Additional Notes:
* The rule is incomplete as shown, lacking an action (e.g., transitioning Stories or the Epic).
The question likely assumes the focus is on the trigger issue being transitioned in the When component.
* If the rule were to include an action (e.g., Transition Stories to Done), the answer might involve Stories, but the current rule stops at the condition.
* The rule is configured in Project settings > Automation and requires project admin privileges for project-level rules.
References:
Atlassian Support Documentation:Automate your Jira Cloud instance
Atlassian Support Documentation:Jira automation triggers
Atlassian Support Documentation:Jira automation conditions
Atlassian Support Documentation:Jira automation actions

質問 # 43
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. Project Export
B. JQL Results Snapshot
C. Issue Filter Export to CSV
D. Backup Jira data

正解：C

質問 # 44
You have two issue types in your HR project: Hire and Fire.
Which two requirements can be met through changes only to field configurations? (Choose two.)

A. For the Fire issue type, the Description field should have a default value of "Termination".
B. For the Fire issue type, the default value for the Priority field should be Blocker.
C. For the Hire issue type, the field description for the Due Date field should read "First day of work".
D. For both issue types, the Assignee field should be hidden when creating but not when viewing an issue.
E. For both issue types, the Employee Name custom field must be required upon creation and must never be blank.
F. For both issue types, the Resolution should be set once the issues are being resolved.

正解：D、F

質問 # 45
......

ACP-120関連受験参考書: https://www.passtest.jp/ATLASSIAN/ACP-120-shiken.html

Ian Shaw Ian Shaw

Biography

ATLASSIAN ACP-120最新試験 & ACP-120関連受験参考書

ACP-120関連受験参考書、ACP-120テストトレーニング

ATLASSIAN Jira Cloud Administrator 認定 ACP-120 試験問題 (Q40-Q45):

Quick Links

Resources

Support