1 / 9

Managing Jira Cloud Projects ACP-620 Exam Questions

With the Managing Jira Cloud Projects ACP-620 Exam Questions, you will get a feel of the actual exam environment and be able to identify the areas where you need improvement.

Download Presentation

Managing Jira Cloud Projects ACP-620 Exam Questions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Pass Atlassian ACP-620 Exam with Real Questions Atlassian ACP-620 Exam Managing Jira Cloud Projects https://www.passquestion.com/ACP-620.html 35% OFF on All, Including Atlassian ACP-620 Questions and Answers Pass ACP-620 Exam with PassQuestion Atlassian ACP-620 questions and answers in the first attempt. https://www.passquestion.com/ 1 / 9

  2. 1.Which of the following are suitable use-cases to use issue-level security? (Choose two.) A. Only managers can view certain projects. B. Only managers can view and edit high-priority issues. C. Only managers can view the development panel. D. Only managers can view issues created by the manager level. E. Only managers can move issues to other projects. Answer: B,D Explanation: Users can create issue security levels within issue security schemes to let users and their team control who can see particular issues. When users associate an issue security scheme with a project, they can apply its security levels to issues in that project. Subtasks inherit the security level of their parent issue. Note: Users need to be a Jira administrator to configure issue security levels. If users need to move issues, they need Move Issues permission. Browse Projects is the permission to control who can view the project. Users need to use View Development Tools permission to control who can view the development panel. 2.__________ shows user how their team is progressing against the work for an epic. Cumulative flow diagram A. Epic burndown report B. Burndown chart C. Velocity chart D. Control chart Answer: A Explanation: The Epic Burndown report shows you how your team is progressing against the work for an epic. An epic is a large user story that can be broken down into a number of smaller stories. The report will show data based on the estimation statistic that your board is using. 3.Nash can view all issues but he is unable to rank the backlog in the Jira Software board. Which permissions does Nash need to request to get the proper access? (Choose two.) A. Edit issues B. View Development Tools C. Manage sprints D. Schedule issues E. Browse Projects F. Move Issues Answer: A,D Explanation: Since Nash can view the issues in the Jira project, he does not need to request the Browse Projects permission anymore. To rank issues in the backlog section, Nash needs to have both the schedule and edit issues permission. 2 / 9

  3. Ranking backlog here means changing the issue's Due Date. You need both permissions to change the issues' Due Date. Schedule issues grant the ability to view or edit an issue's due date. Edit issues grant the ability to edit issues. Manage sprints, Move Issues, and View Development Tools are not required. View Development Tools to grant users in a software project to view development-related information on the issue, such as commits, reviews, and build information. 4.Which of the following is not the default team-managed project role? Note: - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects A. User B. Viewer C. Member D. Administrator Answer: A Explanation: Team-managed software projects come with three roles by default: - Administrator - Member - Viewer Administrator - Admins can do most things, such as: update settings, add other admins to the project, manage features, customize issue types, and add rules on the board. Admins need product access to Jira Software to get the full benefit of this role. Member - Members are a part of the team. They can create issues, edit them, comment on them, move them into different statuses, and generally collaborate on the project's work. Members need product access to Jira Software to get the full benefit of this role. Viewer - Viewers can search through and view issues in the project, but not much else. You can give any registered user on your Jira site this role without extra product access. 5.Which of the following are true about epic? (Choose two.) A. An epic can have another epic. (Epic Link) B. An epic cannot have its own issue screen. C. An epic cannot convert to a sub-task. D. Users need to enable Kanban Backlog to use Epic in the Kanban Board. E. Users can customize Epic's colour in both Kanban and Scrum projects. F. An epic can have issues that belong to more than one project. Answer: E,F 6.According to the components below, who will be the assignee if a user created a ticket with Java and Database components? Project lead: Razi Project default assignee: Unassigned 3 / 9

  4. A. Nick B. Nina C. Razi D. Unassigned E. Dom Answer: C Explanation: A component default assignee will override the project's overall default assignee. If someone creates an issue with more than one component, and the default assignees for those components are different people, then Jira assigns the issue to the default assignee of the component that is first alphabetically. Since there are no components with component lead, and the component 'Java' default assignee is Project default, which is Unassigned, Jira will use the Project Lead, Razi. 7.Nash's team just completed their first sprint. What can they learn from this chart? (Choose three.) (Assume Remaining Estimate and Time Spent is enabled for this board.) 4 / 9

  5. A. Some of the issues are resolved during non-working days. B. Some of the issues are still unresolved. C. This sprint ends with 0 story points. D. This sprint starts with 20 story points. E. There are issues worth 5 story points resolved on July 13th. F. There are no scope changes in this sprint. Answer: C,E,F Explanation: The grey area indicates non-working days. There were no issues resolved during non-working days since story points did not reduce in the grey area. This chart starts drawing the Guideline and Remaining Values lines at the 18 story points on the y-axis. On July 13th, story points were reduced from 15 to 10. This means that users have closed some issues that are worth 5 story points. Users have closed all issues on July 20th. There are no story points remaining on this date. Story points do not increase during this sprint. Since the Remaining Estimate and Time Spent is enabled for this board, scope change is indicated in the Burndown Chart for the subtask. 8.Which of the following exists in both team-managed and company-managed Kanban Projects sidebar? (Choose four.) Note: - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects. A. Version releases. B. A link connected to Bitbucket or GitHub repositories. C. Integration with Opsgenie for on-call and incident management. 5 / 9

  6. D. An informative page integrated with Confluence. E. Project components. F. A website link shortcut. Answer: A,B,C,E 9.An existing Jira project will be handed over to a new team. Users want to change the project details for an upcoming new project. Which project details can users change from the Details page? (Choose four.) A. Key B. Title C. Avatar D. Project Lead E. Name F. Project Type Answer: A,C,D,E Explanation: In the Jira project 'Details' page, userswwwcanonly.dumpspandachange:.com - Name - Key - URL - Project category - Avatar - Description - Project lead - Default assignee Users cannot change their Jira project type. To change the project type, users need to create a new project and use the 'Bulk Change' tools to move all issues into the new project. 10.A group of developers are working on multiple Jira projects. They can view all Jira projects and have the 'Move Issues' permission in all Jira projects. However, they cannot move issues to some of the Jira projects. What is the possible root cause of this problem? A. They do not have the 'View Issue' permission in some projects. B. They do not have the 'Transition Issue' permission in some projects. C. They do not have the 'Edit Issue' permission in some projects. D. They do not have the 'Create Issue' permission in some projects. Answer: D Explanation: If users are moving issues from project to project, they need to make sure they have the Create Issues permission in the Jira project they want to move it to. 11.In the current sprint, users have 10 issues but their team is only able to complete 5 issues. What will happen to the other 5 issues if they wish to complete the current sprint? (Choose two.) A. Unresolved issues will be removed. 6 / 9

  7. B. Users can move them to the next sprint. C. Users can move them to the other active sprints. D. Unresolved issues will be archived. E. Users can move them to their backlog. Answer: A,D Explanation: After users click the 'Complete sprint' button, they have 2 options; either move the incomplete issues to a new sprint or move them to the backlog. 12.Which of the following are true about team-managed projects? (Choose three.) Note: - Company-managed projects are formerly known as classic projects. - Team-managed projects are formerly known as next-gen projects. A. Team-managed projects only have standard board filters. B. By default, any licensed users can create and maintain team-managed projects. C. Users can create multiple team-managed projects and run a parallel sprint. D. Users can share team-managed projects' settings with other Jira projects. E. Users can allow anonymous access to a team-managed project. F. Users can create a new project role. Answer: A,B,F Explanation: A team-managed project is suitable for teams that want to control their own working processes and practices in a self-contained space. You can mix and match agile features to support your team as you grow in size and complexity. Team-managed projects configurations do not impact other projects. Team-managed projects only have a standard board filter. Users cannot customize the board filter. Sub-filter and quick filter do not exist in team-managed projects. However, there is a feature request here (JSWCLOUD-17446) and Atlassian already starts working on this feature. (Updated on 13 Sept 2021) Users can create a new project role in a team-managed project. 7 / 9

  8. All licensed users can create a team-managed project, even non-admins. If you are a Jira admin and want to restrict this, you need to update the 'Create team-managed projects' global permission. Users cannot allow anonymous access to a team-managed project. If users want to allow anonymous access, Jira administrators need to create a company-managed project for them. 13.As a project manager, Dom is responsible in monitoring all issues that have been assigned to his team are on track and the Time Estimation for each issue is correctly measured. Which of the following is the best report that he can use to ensure Time Estimation and Time Spent by his team on issues are on track? A. Single Level Group By Report B. Pie Chart Report C. Resolution Time Report D. Time Tracking Report E. Average Age Report F. Time Since Issues Report Answer: D Explanation: Time Tracking Report shows the original and current time estimates for issues in the current project. This can help users determine whether work is on track for those issues. - Identify which issues have exceeded the original estimation. - Identify which issues are still on track. - Identify which issues are correctly measured. - Identify accuracy of the overall time estimation. - Identify the current team's progression on issues that they are currently working on. 14.Nash is working on a Finance Jira project. The next week, while still working on the Finance project, he also worked on HR projects. Both projects are using their own unique statuses in their project workflow. Nash has updated the default board filter to the JQL below: project in (HR, Finance) ORDER BY Rank ASC A few issues are missing from the Jira board. What are the best solutions for this issue? (Choose two.) A. Update the quick filter. B. Update the Jira workflow. C. Update the board column. D. Update the board filter. Answer: B,C Explanation: Jira board filter only returns a single project by default. Example: project = Finance ORDER BY Rank ASC If users added more than one project in the JQL, some issues might be missing if each Jira project has different statuses in their project workflow. Therefore, Nash has 2 options: - Standardize all project workflow to use the same statuses. 8 / 9

  9. - Update the board column to include the missing issues. Updating the filter is not the solution here because the issues from the unmapped status will still be hidden. 15.Which of the following are false about the roadmap? (Choose three.) A. Users can choose which epics they want to display on the dashboard. Either Complete or Incomplete. B. Users can change the view setting to customize their roadmap's view. The changes will apply to all users that have access to that project. C. Schedule bars for child issues are currently available for scrum teams only. D. Users can customize epic's color directly from the roadmap. E. Users can change the epic bar timeline to weeks, months, quarters, or yearly. Answer: A,B,E Explanation: View Settings is a collection of settings that allow users to adjust their personal view of the roadmap. The settings only apply to individual users. Users can change their view at any time. Schedule Bars for child issues are currently available for scrum teams only. Epic Display Options allow users to use the dropdown to select which epics to display. The current options are All, Incomplete, or Complete. Users can adjust the color of an epic directly on the roadmap. Simply right-click the epic and choose a fresh color. The epic bar has a default duration according to how users view their timeline. The default durations are weeks, months, or quarters. 9 / 9

More Related