ACP-620 Day 1: Project Creation Quiz

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

Questions

Medium level

  1. When configuring a company-managed project for a development team that prefers to work with feature branches, what type of project template would be most appropriate?

    • A) Scrum software development

    • B) Kanban software development

    • C) Software project with a Git integration feature

    • D) Basic software development

 

  1. A project manager wants to create a new project with unique workflows and permissions that can be replicated for future projects. Which feature should they use?

    • A) Create a new team-managed project

    • B) Clone an existing company-managed project

    • C) Create a new company-managed project with shared configurations

    • D) Use an existing project as a template

 

  1. When setting up a new project, which two features can be directly configured from the project sidebar in a company-managed project?

    • A) Issue types and workflows

    • B) Project roles and permissions

    • C) Project details and description

    • D) Board settings and filters

 

  1. Single Choice

    • 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

 

  1. In a company-managed project, which three issue type configurations can be defined to meet specific business requirements?

    • A) Issue type names

    • B) Issue type schemes

    • C) Default issue type for the project

    • D) Issue type screen schemes

    • E) Issue type field configurations

 

  1. If a business requires a project to collaborate on content creation with external partners using articles and blog posts as issue types, what type of project should you configure?

    • A) Company-managed project with a custom issue type scheme

    • B) Team-managed project with limited issue types

    • C) Service management project for external partner interaction

    • D) Project using default business project template

 

Advanced level

  1. When creating a company-managed project, which two project elements are important to configure for a team that handles a high volume of issues with varying security requirements?

    • A) Issue security schemes

    • B) Component leads

    • C) Custom field contexts

    • D) Permission schemes

 

  1. In a company-managed project, where would you configure the project's email address for receiving tickets from customers?

    • A) Project settings > Customer notifications

    • B) Project settings > Email requests

    • C) Project settings > Issue collectors

    • D) Jira settings > System > Incoming mail

 

  1. What is the best practice for creating a project designed to track a variety of tasks such as bugs, customer feedback, and operational work for a non-technical team?

    • A) Use a team-managed project for simplicity and quick setup

    • B) Use a company-managed project with a general business project template

    • C) Create a company-managed project with custom issue types and workflows

    • D) Choose a service management template to handle diverse tasks

 

  1. Which project setup would you recommend for an organization that wants to use Jira to manage its hiring process, including tracking candidates, interviews, and feedback?

  • A) Team-managed project with customized workflows for each recruitment stage

  • B) Company-managed project using a business template with custom issue types like 'Candidate' and 'Interview'

  • C) Service management project for handling internal service requests

  • D) A standard company-managed project with default settings

  1. As part of configuring a company-managed project for a team that works with sensitive data, which two configurations would you prioritize to ensure proper access control and confidentiality? (Choose 2)

  • A) Setting up a detailed notification scheme

  • B) Configuring issue security levels

  • C) Applying a permission scheme that restricts issue visibility

  • D) Customizing the issue collector for secure data submission

 

  1. A large enterpriseis adopting Jira for cross-functional teams that must collaborate on complex products. The teams have different workflows but need to share some common configurations. What is the most efficient way to handle this in Jira?
    - A) Create individual team-managed projects for autonomy
    - B) Set up a company-managed project with a shared configuration scheme
    - C) Develop a new project type with a unique scheme for each team
    - D) Use a service management project to handle cross-functional requirements

 

Solutions

 

Question

Answer

Reason

Question

Answer

Reason

1

C

The Git integration feature is specific to software development projects and supports feature branch workflows. Options A and B are general software development templates that may not include Git features, while option D provides basic functionality without focusing on version control integration.

2

C

Creating a new company-managed project with shared configurations allows for unique workflows and permissions while enabling the replication of this setup for future projects. Option A does not offer shared configurations, option B does not allow for unique workflows and permissions, and option D does not support the replication of settings.

3

B, C

The project sidebar in a company-managed project directly allows modification of project roles and permissions, as well as project details and descriptions. Options A and D (issue types and workflows, board settings, and filters) are configured in different sections of the project settings.

4

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.

5

B, D

Issue type schemes allow for the definition of issue type names and default issue types, as well as the association of screen schemes. Options A and C (workflow associations and field configurations) are part of workflow schemes and field configuration schemes, respectively.

6

A

Company-managed projects allow for the creation of custom issue types and more complex configurations needed for collaborative content creation. Options B and D offer less customization for issue types, and option C is geared towards service management rather than content collaboration.

7

A, D

Issue security schemes and permission schemes are critical for managing access to a high volume of issues with different security requirements. Option B (component leads) is less crucial in this context, and option C (custom field contexts) relates more to the display of fields than to security or permissions.

8

B

Email requests are configured in the Project settings under Email requests in company-managed projects, which allows for the setup of an email address for ticket creation. Options A and C are incorrect because they pertain to customer notifications and issue collectors, respectively. Option D is a system-wide setting and not specific to individual projects.

9

C

A company-managed project with custom issue types and workflows allows for the flexibility needed to track a variety of tasks for a non-technical team. Option A may be too simple, option B does not provide the required customization, and option D is geared towards service teams.

10

B

For managing a hiring process, a company-managed project with a business template allows for custom issue types like 'Candidate' and 'Interview' and can be tailored to the hiring workflow stages. Option A is less suited for non-technical workflows, option C is for service requests, and option D does not offer the necessary customization.

11

B, C

Issue security levels and a permission scheme that restricts issue visibility are crucial for ensuring data confidentiality in a project handling sensitive information. Option A focuses on notifications, which does not impact access control, and option D pertains to data submission rather than access control or confidentiality.

12

B

A company-managed project with a shared configuration scheme allows for the standardization of certain elements while granting the flexibility needed for different workflows across teams. Option A does not provide the necessary shared configurations, option C is not as efficient for scaling, and option D is typically used for external customer services, not internal cross-functional collaboration.

 

 

Â