ACP-620 Day 6: Exam examples

Owned by Frank Lapa
Last updated: Nov 09, 2023
9 min read

Index

 

  • Project Creation

  • Board Configuration

  • Managing Projects

  • Automation

  • Reporting

 

1. Questions

1.1 Project Creation

For a team that requires strict control over who can create, transition, and view issues, which project type is most suitable?

  • A) Team-managed project

  • B) Company-managed project

  • C) Project with a shared configuration

  • D) Project using advanced roadmaps

 

B

Company-managed projects offer more granular permission and workflow controls necessary for strict issue visibility and transition control. Options A and C offer less control over permissions, and option D is not relevant to the control over issue transitions.

 

Given the business requirement for a small, autonomous marketing team that needs to manage a continuous flow of tasks without predefined iterations, which project type should be recommended to facilitate a flexible and self-managed approach to their work?

  • A) Team-Managed Scrum project

  • B) Team-Managed Kanban project

  • C) Company-Managed Scrum project

  • D) Company-Managed Kanban project

 

B

The business requirement indicates a need for a continuous flow of work without the structure of iterations, which is a characteristic of the Kanban methodology. A Team-Managed Kanban project is best suited for small, autonomous teams that require flexibility and minimal administrative overhead

 

A startup's development team is looking to adopt Agile methodologies to manage their software development process. They aim to work in fixed-length iterations to regularly deliver increments of their product. Which project type would best support their need for iterative development and allow them to manage their backlog and sprints?

  • A) Team-Managed Scrum project

  • B) Team-Managed Kanban project

  • C) Company-Managed Scrum project

  • D) Company-Managed Kanban project

 

A

The startup is seeking to implement Agile methodologies with an emphasis on fixed-length iterations, which is indicative of the Scrum framework. A Team-Managed Scrum project would provide the necessary tools for backlog and sprint management while enabling the team to self-organize and adapt quickly.

 

An experienced Jira user is planning sprints for multiple teams and wants to implement a cross-project sprint that includes issues from several team-managed projects. What limitation will they encounter with sprints in team-managed projects?

  • A) Sprints cannot be named consistently across multiple team-managed projects, creating confusion in cross-project reporting.

  • B) Team-managed projects do not allow issues to be assigned to more than one active sprint, hindering cross-project sprint planning.

  • C) Cross-project sprints in team-managed projects cannot be closed until all associated projects have completed their work.

  • D) Sprints in team-managed projects can only include issues from a single project and do not support cross-project sprint planning.

 

D

Team-managed projects are isolated and designed to be managed independently. They do not support the creation of sprints that span across multiple projects, as sprints in team-managed projects are confined to the project in which they were created. This presents a challenge for a user trying to plan sprints that encompass issues from several team-managed projects simultaneously.

 

 

1.2 Board Configuration

When managing releases in a JIRA Scrum board, which configuration helps the team understand what is scheduled for the current release?

  • A) Configure a quick filter to show only issues assigned to the current release version.

  • B) Set up a release burndown chart on the dashboard.

  • C) Use version swimlanes to separate issues by the target release.

  • D) Label each card with the version number and sort the backlog accordingly.

 

A

Quick filters provide an efficient way to display only the issues relevant to the current release version without affecting the board's overall layout.

 

How can a Board administrator customize a board to show issues that require immediate attention due to impending deadlines?

  • A) Set a quick filter to highlight issues with due dates within the next 7 days.

  • B) Customize card colors based on due date proximity.

  • C) Implement swimlanes sorted by due date.

  • D) Create an 'Expedite' column for all issues with due dates within a week.

 

B

Customizing card colors based on due date proximity enables teams to visually prioritize work that is nearing its deadline.

 

For a team that needs to manage cross-functional tasks that affect multiple components within a project, how should the JIRA board be configured for optimal visibility?

  • A) Set up a board filter that includes all components and use card layout to display them.

  • B) Use a component-based swimlane configuration.

  • C) Create a multi-board setup with one board per component.

  • D) Implement a tagging system for cross-functional tasks and use quick filters.

 

B

Component-based swimlanes allow for logical grouping of issues, which is beneficial for teams dealing with multiple components.

 

1.3 Managing Projects

If issues in a specific component keep getting assigned to the wrong user, which configuration should an administrator check first?

  • A) Permission Scheme

  • B) Component settings for default assignee

  • C) Workflow post-functions

  • D) Notification Scheme

 

B

If issues are being assigned to the wrong user, the first configuration to check is the component settings for the default assignee, as this controls the auto-assignment of issues.

 

In the Phoenix company-managed project, a Mark moved some of his assigned tasks to “on review” column, since that all those tasks are visible in the board bit can’t be edited anymore, but he still is able to edit tasks in other columns of the board, what can be happening?

  • A) Someone remove Mark Edit issue permission in Phoenix project

  • B) On review column doesn’t have any status mapped

  • C) On review column has a status with a property to restrict edition

  • D) Mark lose his transition issue permissions in Phoenix project

 

C

Someone added jira.issue.editable=false in the status mapped into “On review”

 

You are re-creating an existing company-managed project to streamline its configuration. When re-creating this project, which two of the following considerations regarding standard fields and required permissions should you take into account to avoid loss of data and functionality?
(Choose two)

  • A) Recreating the project may result in the loss of historical data for the 'Components' and 'Versions' fields unless they are manually migrated.

  • B) The 'Project Administrator' permission will be required to modify 'Components' and 'Versions' fields during the project re-creation.

  • C) The 'Administer Projects' global permission is necessary for changing any project-level standard fields, including 'Components' and 'Versions'.

  • D) Standard fields like 'Components' and 'Versions' are automatically included in the new project without the need for manual configuration or migration.

 

A, B

A) When creating a new project, historical data associated with 'Components' and 'Versions' in the original project is not automatically transferred. To preserve this information, it must be migrated manually, ensuring that existing configuration and associated issues retain their component and version data.

B) The 'Project Administrator' permission is specifically needed to manage project settings, including modifying 'Components' and 'Versions'. Users with this permission can configure these fields as part of the project re-creation process.

Options C and D are incorrect as the 'Administer Projects' global permission is broader and might not be necessary for specific field changes, and standard fields like 'Components' and 'Versions' may require manual intervention to ensure they reflect the original project's configuration in the new project setup

 

You are configuring permissions for a company-managed project in Jira called "Project Titan” with the next Permission Scheme:

Permission

Roles

Permission

Roles

Manage Sprints

Administrator, Manager

Administer Projects

Administrator

Create Issues

Developer

Edit Issues

Manager, Developer, Administrator

Browse Projects

Manager, Developer

Team Members and Assigned Roles:

Name

Roles

Name

Roles

Alice

Administrator

Bob

Manager

Charlie

Developer

Dana

Manager, Developer

I. Given the above permission configuration for ‘Project Titan,' which team members can’t edit issues

  • A) Alice

  • B) Bob

  • C) Charlie

  • D) Dana

 

B

Bob has Manager role which allow to edit sprint, and has Manager and Developer which allow to browse issue and also edit issue

 

 

II. Given the above permission configuration for ‘Project Titan,' which team members can edit issues and sprints

  • A) Alice

  • B) Bob

  • C) Charlie

  • D) Dana

 

A

The Administrator role have edit issue permission, but can’t see the issue, so can’t edit

 

 

1.4 Automation

If you want to create a rule that triggers across multiple projects when an issue is created, which automation rule scope should be selected?

  • A) Single Project

  • B) Multi-Project

  • C) Global Rule

  • D) Local Rule

 

B

A Multi-Project rule scope allows a rule to trigger across several projects within Jira.

 

If you want to create a rule that triggers across multiple projects when an issue is created, which automation rule scope should be selected?

  • A) Single Project

  • B) Multi-Project

  • C) Global Rule

  • D) Local Rule

 

B

A Multi-Project rule scope allows a rule to trigger across several projects within Jira.

 

Which feature would you use to trigger an automation rule in Jira when an event occurs in an external system, like a CRM?

  1. A) Webhooks

  2. B) Application Links

  3. C) Remote Issue Links

  4. D) External Gadgets

 

A

Webhooks are used to communicate with external systems, allowing Jira to trigger automation rules based on events from those systems.

 

You are designing a complex automation rule for a company-managed project. The rule needs to trigger a series of actions not only on the parent issue but also on all linked issues of a specific type. The actions must execute only if the linked issues meet certain JQL criteria. Which automation feature should you utilize to efficiently design this rule?

  • A) Global rules with a multi-project scope

  • B) Smart values to dynamically identify and act on linked issues

  • C) Branch rule with JQL condition to specify and act on linked issues

  • D) Custom script runner to manually iterate over linked issues

 

C

C) The branch rule within Jira automation allows you to define a separate branch with its own set of conditions and actions for related issues, such as sub-tasks or linked issues. By using a JQL condition within a branch rule, the automation can be tailored to affect only those linked issues that meet the specified criteria, thus providing the precise control needed for complex automation scenarios.

Options A and B, while useful in their contexts, do not offer the same targeted approach as a branch rule does for linked issues. Option D is an alternative approach but would require custom scripting, which is less efficient and more time-consuming than using the built-in branch rule functionality of Jira automation.

 

1.5 Reporting

Create a JQL query to identify all issues across multiple projects that are assigned to the 'Q4 Release' version but have not yet been resolved or closed. These issues also need to be currently assigned to members of the 'Developers' group. Given the projects are named 'MobileApp', 'WebApp', and 'API', which JQL query would correctly retrieve the required issues?

A) project in (MobileApp, WebApp, API) AND fixVersion = "Q4 Release" AND status not in (Resolved, Closed) AND assignee in membersOf("Developers")

B) project in (MobileApp, WebApp, API) AND fixVersion = "Q4 Release" AND status != (Resolved OR Closed) AND assignee in membersOf(Developers)

C) project in (MobileApp, WebApp, API) AND fixVersion == "Q4 Release" AND NOT status in (Resolved, Closed) AND assignee in membersOf(Developers)

D) project in (MobileApp, WebApp, API) AND fixVersion = 'Q4 Release' AND status not in (Resolved, Closed) AND assignee in membersOf('Developers')

 

A

The correct JQL query must accurately reflect the syntax for searching multiple projects, the version name, status category, and group membership. Option A uses the correct syntax for each of these JQL components. The in operator is correctly used for multiple values (projects and statuses), the fixVersion is compared using a single =, and membersOf is used correctly to refer to a user group. Additionally, the double quotes around "Q4 Release" and "Developers" are correctly used for string values in JQL.

Why not others

  • Option B incorrectly uses parentheses for the status field and omits quotes around the group name.

  • Option C uses == for comparison instead of the correct =, and 'NOT' should not be capitalized.

  • Option D uses single quotes for the 'Q4 Release' version and 'Developers' group which is not the standard syntax in JQL.

 

To facilitate a smooth Agile process, what type of report should be used to review completed work and plan for future sprints?

  • A) Sprint Report

  • B) Burndown Chart

  • C) Velocity Chart

  • D) Epic Report

 

A

The Sprint Report is for inspecting sprint completion, while the other options serve different purposes: Option B for individual issue time tracking, Option C for cross-project dependencies, and Option D for monitoring workload among users.

 

You need to report on the average time taken to resolve issues of a certain type. Which report would provide this insight?

A) Time Tracking Report
B) Average Age Report
C) Resolution Time Report
D) Created vs. Resolved Issues Report

 

C

The Resolution Time Report indicates the average time taken to resolve issues.
Option A, the Control Chart, focuses on cycle time for individual issues.
Option B, the Average Age Report, measures the age of unresolved issues.
Option D, the Workload Pie Chart, displays workload distribution, not resolution time.

1.6 Extra

The "OmegaProject" has Taylor as Project Lead and has the next components:

  • UI: Component Lead → Jamie, default Assignee Component Lead

  • Database: Component Lead → Alex, default Assignee Project Lead

  • Cloud Services: Component Lead → Jordan, default Assignee is unassigned

Question: when a new issue is created and includes all three components ('UI', 'Database', and 'Cloud Services'), to whom will the issue be automatically assigned?

  • A) Unassigned, because multiple component leads are involved.

  • B) Jamie

  • C) Taylor

  • D) Alex

 

B

UI → Default assignee is Component Lead = Jaime

Database → Default assignee is Project Lead = Taylor

Cloud Services → Default assignee is unassigned

Unassigned doesn’t count, so is between Jaime and Taylor, as it has multiple components, will be the firs by alphabetic order, then Jaime

 

2. Additional material