Майстерня смаку

Carl Stark Carl Stark

0 Зараховано на курс • 0 Курс Завершено

Біографія

ACP-120최신업데이트버전덤프공부자료인기자격증시험덤프자료

Pass4Test의 제품을 구매하시면 우리는 일년무료업데이트 서비스를 제공함으로 여러분을 인증시험을 패스하게 도와줍니다. 만약 인증시험내용이 변경이 되면 우리는 바로 여러분들에게 알려드립니다.그리고 최신버전이 있다면 바로 여러분들한테 보내드립니다. Pass4Test는 한번에ATLASSIAN ACP-120인증시험을 패스를 보장합니다.

Atlassian ACP-1220 (Jira Cloud Administrator) 인증 시험을 치르려면 Jira Cloud Administration에서 경험이 있어야합니다. 워크 플로, 체계 및 권한을 포함한 Jira Cloud 개념을 잘 이해해야합니다. 또한 이메일 알림 구성 및 백업 관리와 같은 기본 시스템 관리 작업에 익숙해야합니다.

>> ACP-120최신 업데이트버전 덤프공부자료 <<

최신버전 ACP-120최신 업데이트버전 덤프공부자료 덤프자료는 Jira Cloud Administrator 최고의 시험대비자료

ATLASSIAN인증 ACP-120시험을 등록했는데 마땅한 공부자료가 없어 고민중이시라면Pass4Test의ATLASSIAN인증 ACP-120덤프를 추천해드립니다. Pass4Test의ATLASSIAN인증 ACP-120덤프는 거의 모든 시험문제를 커버하고 있어 시험패스율이 100%입니다. Pass4Test제품을 선택하시면 어려운 시험공부도 한결 가벼워집니다.

ACP-120 인증 시험은 Atlassian의 교육 파트너가 진행하는 온라인 감독 시험입니다. 지원자들은 60개의 객관식 문항으로 구성된 90분 동안 시험을 보게 됩니다. 이 시험은 영어로 제공되며 전 세계 어디서든 응시할 수 있습니다.

ATLASSIAN ACP-120 (Jira Cloud Administrator) 시험은 Jira Cloud 환경을 구성하고 관리하며 유지 보수하는 데 필요한 기술과 지식을 검증하는 산업 인정 자격증입니다. 이 시험은 Jira Cloud 인스턴스를 관리하고 조직의 요구에 최적화되도록 보장하는 업무를 맡은 전문가들을 위해 설계되었습니다. 이 자격증으로, 개인은 Jira Cloud 관리에 대한 정통성을 입증하고 프로젝트 관리 분야에서의 진로 전망을 향상시킬 수 있습니다.

최신 Jira Administrator ACP-120 무료샘플문제 (Q65-Q70):

질문 # 65
Which statement is correct regarding Jira Cloud import and export features?

A. Project admins can import their own projects.
B. Org admins can restore overwritten backups.
C. Jira admins can import backup files.
D. Project admins can create site backups.
E. Jira admins can create backup files.

정답：E

설명：
Jira Cloud's import and export features allow administrators to back up, restore, or migrate data. The correct statement is thatJira admins can create backup files(Option A), as this is a supported function for Jira administrators.
* Explanation of the Correct Answer (Option A):
* Jira administrators have the ability to create backup files for a Jira Cloud site, which include issues, configurations, users, and media (e.g., attachments). These backups can be used for restoration or migration purposes.
* Exact Extract from Documentation:
Create a backup for Jira Cloud
Jira administrators can create backup files that include issues, configurations, users, and media.
To create a backup:
* Go toSettings > System > Backup manager.
* SelectCreate backup for cloud.
* Download the backup file when ready.Note: Requires Jira administrator permissions.
Backup files can be used for restoration or migration.(Source: Atlassian Support Documentation, "Back up Jira Cloud data")
* Why This Fits: The ability to create backup files is explicitly granted to Jira admins, making Option A the correct statement.
* Why Other Options Are Incorrect:
* Org admins can restore overwritten backups (Option B):
* Organization admins manage Atlassian organization settings (e.g., billing, user access) but do not have direct access to Jira-specific backup restoration. Restoring backups, including overwritten ones, is handled byJira administratorsorsupport requeststo Atlassian.
Overwritten backups cannot typically be restored without Atlassian intervention.
* Extract from Documentation:
Organization admins manage organization-level settings. Restoring backups, including overwritten ones, requires Jira administrator permissions or Atlassian support.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Project admins can import their own projects (Option C):
* Project admins can manage project settings (e.g., permissions, issue types) but do not have permissions to import projects or data, as this is a system-level action reserved forJira administrators.
* Extract from Documentation:
Importing projects or data requires Jira administrator permissions. Project admins cannot perform imports.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Project admins can create site backups (Option D):
* Creating site backups is a system-level action restricted toJira administrators. Project admins lack the permissions to create backups for the entire site or their projects.
* Extract from Documentation:
Only Jira administrators can create site backups inSettings > System > Backup manager. Project admins do not have this capability.
(Source: Atlassian Support Documentation, "Back up Jira Cloud data")
* Jira admins can import backup files (Option E):
* While Jira admins can initiate the import process for backup files, the actual import of full site backups typically requiresAtlassian supportor is performed through specific tools (e.
g.,Import Jira Cloudfeature). Partial imports (e.g., CSV, Trello) are supported, but full backup imports are not a standard Jira admin action without additional steps. This makes the statement less definitively correct compared to Option A.
* Extract from Documentation:
Importing full site backups often requires Atlassian support. Jira admins can import partial data (e.g., CSV, JSON) but not full backups directly.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Additional Notes:
* Creating a backup is a straightforward action for Jira admins inSettings > System > Backup manager.
* The backup process requiresJira administratorprivileges, not project admin or organization admin roles.
* Full backup imports or restoration of overwritten backups typically involve Atlassian support, limiting the scope of Jira admin actions.
:
Atlassian Support Documentation:Back up Jira Cloud data
Atlassian Support Documentation:Restore your Jira Cloud site from a backup Atlassian Support Documentation:Import data to Jira Cloud Atlassian Support Documentation:Manage your Atlassian organization

질문 # 66
Your business owners have told you to use roles as much as possible in Jira because it allows them to do things that groups cannot do.
When considering this, you need to be aware of those actions in Jira that require the use of groups rather than roles.
Identify two actions in Jira that require the use of groups. (Choose two.)

A. granting permissions to teams coming from Active Directory
B. controlling who can perform Bulk Change in a project
C. granting system administrative rights
D. granting Project Administration rights
E. allowing users to use transitions in all the workflows
F. defining Issue Security levels

정답：D,F

설명：
Reference: https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html

질문 # 67
You need to make changes to the time tracking feature in Jira. What configuration can be controlled globally across all projects?

A. The ability to log work on issues for specific groups
B. The requirement of an original estimate when creating issues
C. The default tracking time unit, unless users explicitly specify one
D. The availability of time tracking fields on standard versus sub-task issue types
E. The ability to edit or delete their own or other users' worklogs for specific users

정답：C

설명：
Thetime trackingfeature in Jira Cloud allows logging work, tracking estimates, and managing time-related settings. The configuration that can be controlled globally across all projects isthe default tracking time unit, unless users explicitly specify one(Option C), as this is set in the global time tracking settings.
* Explanation of the Correct Answer (Option C):
* Thedefault tracking time unit(e.g., hours, days) is configured globally in Jira Cloud's time tracking settings and applies to all projects unless users specify a different unit when logging time or setting estimates. This setting determines how time is displayed and entered by default across the system.
* Exact Extract from Documentation:
Configure time tracking in Jira Cloud
Global time tracking settings apply to all projects and include:
* Default time unit: Sets the default unit for time tracking (e.g., hours, days).To configure:
* Go toSettings > Issues > Time tracking.
* Set theDefault unit for time tracking(e.g., Hour).Impact: The default unit is used across all projects unless users explicitly specify another unit (e.g., 2d for days).Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Configure time tracking in Jira Cloud")
* Why This Fits: Thedefault tracking time unitis a global setting that applies to all projects, making Option C the correct answer.
* Why Other Options Are Incorrect:
* The ability to log work on issues for specific groups (Option A):
* The ability to log work is controlled by theWork On Issuespermission in each project's permission scheme, not globally. Permissions are project-specific, even if projects share a scheme, and cannot be set globally for specific groups across all projects.
* Extract from Documentation:
TheWork On Issuespermission is set in project permission schemes, not globally.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* The ability to edit or delete their own or other users' worklogs for specific users (Option B):
* Permissions to edit or delete worklogs (e.g.,Edit Own Worklogs,Edit All Worklogs, Delete Own Worklogs,Delete All Worklogs) are also set in project permission schemes, not globally. These are project-specific settings.
* Extract from Documentation:
Worklog permissions (Edit Own Worklogs,Delete All Worklogs) are configured in project permission schemes, not globally.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* The availability of time tracking fields on standard versus sub-task issue types (Option D):
* The availability of time tracking fields (e.g., Original Estimate, Remaining Estimate) is controlled byfield configurationsorscreens, which are project-specific or issue type- specific. There is no global setting to differentiate timetracking fields between standard and sub-task issue types.
* Extract from Documentation:
Time tracking fields are managed by field configurations and screens, not global settings. Their availability depends on project or issue type configurations.
(Source: Atlassian Support Documentation, "Configure field settings")
* The requirement of an original estimate when creating issues (Option E):
* Requiring anOriginal Estimateis controlled byfield configurations(making the field required) orworkflow validators(enforcing a value during transitions). These are project- specific or issue type-specific, not global settings.
* Extract from Documentation:
Requiring fields likeOriginal Estimateis set in field configurations or workflow validators, not globally.
(Source: Atlassian Support Documentation, "Configure field settings")
* Additional Notes:
* Configuring global time tracking settings requiresJira administratorprivileges and is done in Settings > Issues > Time tracking.
* Other global time tracking settings include the format (e.g., hours per day, days per week) and whether time tracking is enabled.
* Project-specific settings (e.g., permissions, field requirements) override global defaults for specific use cases.
:
Atlassian Support Documentation:Configure time tracking in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Configure field settings

질문 # 68
George is the project lead of several projects. Now, he needs to create projects but should not have Jira administrator privileges. What does George need?

A. Global permission
B. Product role
C. Project permission
D. Project role
E. Product access

정답：A

설명：
To create projects in Jira Software Cloud without having full Jira administrator privileges, George needs a specificglobal permission, namely theCreate Projectspermission. This permission allows users to create new projects without granting them broader administrative access.
* Explanation of the Correct Answer (Option D):
* TheCreate Projectsglobal permission enables a user to create new projects in Jira. This permission is distinct from Jira administrator privileges, which include managing global settings like schemes, users, and workflows. By granting George this permission, he can create projects while maintaining a limited scope of authority.
* Exact Extract from Documentation:
Global permissions
Global permissions control access to system-wide actions in Jira. TheCreate Projectspermissionallows users to create new projects without requiring full Jira administrator privileges.
To grant this permission:
* Go toSettings > System > Global permissions.
* Add a user, group, or role to theCreate Projectspermission.Note: Users with this permission can create projects but cannot modify global configurations like schemes or user management unless they have additional permissions.(Source: Atlassian Support Documentation, "Manage global permissions")
* Why This Fits: TheCreate Projectsglobal permission directly addresses the requirement for George to create projects without needing Jira administrator privileges, making Option D the correct choice.
* Why Other Options Are Incorrect:
* Project role (Option A):
* Project roles (e.g., Administrator, Developer) are used within a project's permission scheme to grant project-specific permissions, such asAdminister ProjectsorBrowse Projects. They do not control the ability to create new projects, which is a system-level action.
* Extract from Documentation:
Project roles are used in permission schemes to grant permissions within a specific project. They do not apply to global actions like creating projects.
(Source: Atlassian Support Documentation, "Manage project roles")
* Product access (Option B):
* Product access determines whether a user can use Jira Software or other Atlassian products.
While George needs product access to use Jira, this does not grant the specific ability to create projects.
* Extract from Documentation:
Product access allows users to log in and use Jira products. Specific actions, like creating projects, require global or project permissions.
(Source: Atlassian Support Documentation, "Manage product access")
* Project permission (Option C):
* Project permissions (e.g.,Administer Projects,Browse Projects) are defined in a project's permission scheme and apply to actions within a specific project. Creating a project is a global action, not tied to any existing project's permission scheme.
* Extract from Documentation:
Project permissions control actions within a project, such as editing issues or managing components. Global permissions control system-wide actions like creating projects.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Product role (Option E):
* Product roles (e.g., Jira Software User, Jira Service Management Agent) define access to specific Atlassian products but do not grant permissions for actions like creating projects.
This is not relevant to the requirement.
* Extract from Documentation:
Product roles determine access to Atlassian products and are not related to specific permissions like creating projects.
(Source: Atlassian Support Documentation, "Manage product roles")
* Additional Notes:
* TheCreate Projectspermission can be granted to George via a group or directly to his user account inSettings > System > Global permissions.
* As a project lead, George likely already has project-level permissions (e.g.,Administer Projects for his projects), but these do not extend to creating new projects.
:
Atlassian Support Documentation:Manage global permissions
Atlassian Support Documentation:Manage project roles
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage project permissions
Atlassian Support Documentation:Manage product roles

질문 # 69
A custom field was just added to Jira and made available to all issue types and all projects. You want to use the field in your company-managed project. Identify one configuration you must modify.

A. Screen
B. Field configuration
C. Issue layout
D. Custom field context

정답：A

설명：
To use a newly added custom field in a company-managed project, you must ensure it appears on the appropriate screens (e.g., Create, Edit, View) for the project's issue types. The configuration that must be modified is thescreen(Option B), as the field needs to be added to the screen(s) used by the project.
* Explanation of the Correct Answer (Option B):
* The custom field is already available to all issue types and projects, meaning itscontextis configured globally. To make the field usable in your company-managed project, it must be added to thescreenassociated with the project's issue types (via thescreen scheme). Screens determine which fields are displayed during issue operations (Create, Edit, View), and adding the custom field to the relevant screen ensures users can interact with it.
* Exact Extract from Documentation:
Add a custom field to a screen
To use a custom field in a project, it must be added to the screens used for Create, Edit, or View operations.
To add a field:
* Go toSettings > Issues > Screens.
* Select the screen associated with the project's issue types.
* Add the custom field to the screen.Note: Ensure the screen is part of the project's screen scheme (Project settings > Screens). If the field is not on the screen, it will not appear during issue operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Why This Fits: Adding the custom field to the project's screen is a necessary configuration to make it usable, as it ensures the field is visible and editable, meeting the requirement to use the field in the project.
* Why Other Options Are Incorrect:
* Field configuration (Option A):
* Field configurationscontrol whether a field is required, optional, or hidden. While you might later adjust the field's behavior (e.g., make it required), the field is already available and does not require field configuration changes to be used initially. Adding it to a screen is the primary step.
* Extract from Documentation:
Field configurations manage field behavior (e.g., required, hidden). Adding a field to a screen is required before configuring its behavior.
(Source: Atlassian Support Documentation, "Configure field settings")
* Custom field context (Option C):
* The custom field'scontextis already configured to include all issue types and projects, so no changes are needed here. Contexts define the projects and issue types a field applies to, and this is already set correctly.
* Extract from Documentation:
Custom field contexts define where a field is available. If a field is already available to all projects and issue types, no context changes are needed.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Issue layout (Option D):
* Theissue layoutcontrols which fields are displayed or hidden in the issue view and filter results. While you might later adjust the issue layout to show the field in the issue view, the initial step to use the field is adding it to the screen for Create/Edit operations. The screen configuration is more fundamental.
* Extract from Documentation:
Issue layouts control field visibility in the issue view. Fields must first be added to screens for Create/Edit operations before appearing in the issue layout.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Additional Notes:
* Steps to configure:
* Identify the screen(s) used by the project's issue types inProject settings > Screens.
* Go toSettings > Issues > Screens, select the relevant screen, and add the custom field.
* Configuring screens requiresJira administratorprivileges.
* After adding the field to the screen, you may also configure theissue layoutorfield configuration for additional control, but the screen is the first required step.
:
Atlassian Support Documentation:Configure screens in Jira Cloud
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure issue layouts in Jira Cloud

질문 # 70
......

ACP-120최신버전덤프: https://www.pass4test.net/ACP-120.html