ACP-120 logo
Focused certification exam prep
Start practice

ACP-120 Domain 4: General Project Configuration (10-15%) - Complete Study Guide 2026

TL;DR
  • Domain 4 accounts for 10-15% of the ACP-120 exam, meaning roughly 7-11 questions across up to 75 total items.
  • Candidates must distinguish between company-managed and team-managed projects and know exactly what admins can configure in each.
  • Scheme associations - connecting workflows, issue types, screens, and permissions to a project - are a recurring exam focus in Domain 4.
  • Board configuration, including column mapping to workflow statuses, is tested as a practical admin task, not just a concept.

What Domain 4 Covers and Why It Matters

Domain 4 - General Project Configuration - represents 10-15% of the ACP-120 exam, placing it in the mid-tier weight category alongside User Features (Domain 1) and above the smaller domains covering global settings and notifications. While it is not the single largest domain (that distinction belongs to Domain 3: Product and Project Access and Permissions, which commands 30-35%), Domain 4 is deceptively important because its concepts underpin nearly everything else a Jira Cloud administrator does.

When a new project is created in Jira Cloud, an administrator must make a cascade of configuration decisions: What project type is appropriate? Which schemes should be associated? How should the board be configured to reflect the team's workflow? How are components and versions managed? Domain 4 tests whether a candidate can answer all of these questions with the confidence of someone who has actually administered Jira Cloud at scale - not just read about it.

If you want an overview of how Domain 4 sits within the full exam structure, the ACP-120 Exam Domains 2026: Complete Guide to All 8 Content Areas maps out all eight domains with their weights and relative priorities.

Why General Project Configuration Is Tested: Every Jira Cloud project is a container for schemes, boards, and settings. An administrator who cannot correctly configure a project from creation through ongoing maintenance will cause permission gaps, workflow inconsistencies, and board confusion that affect entire teams. The ACP-120 tests this domain because it is where theory meets daily admin reality.

Exam Weight, Question Style, and What to Expect

The ACP-120 exam contains up to 75 questions and runs for 180 minutes. At 10-15% weight, Domain 4 contributes approximately 7 to 11 questions. The format includes multiple-choice, multiple-response, and scenario/configuration-reasoning items - and Domain 4 leans heavily toward the scenario-based format. Rather than asking "What is a project category?", the exam presents a situation: a project manager cannot see a specific board column, or a newly created project is using the wrong workflow. You are expected to identify the root cause and the correct administrative action.

This scenario-first style means rote memorization of menu paths is insufficient. Candidates must understand why configurations exist, what breaks when they are misconfigured, and how to resolve issues efficiently. The exam is administered through Certiverse (Atlassian's testing platform as of 2026) and is based on the ACP-120 Exam Topics v3, April 2021. The passing score is 63%, and the fee is approximately $249-$250 USD plus applicable tax.

Exam Attribute Detail
Domain 4 Weight 10-15% of total exam score
Estimated Question Count Approximately 7-11 questions (out of up to 75)
Primary Question Style Scenario-based configuration and troubleshooting
Exam Duration 180 minutes
Passing Score 63%
Exam Fee ~$249-$250 USD + applicable tax
Testing Platform Certiverse (2026)

Scrum vs. Kanban vs. Business Projects: Admin Differences

One of the most fundamental distinctions in Domain 4 is understanding the three primary project types available in Jira Cloud and the administrative implications of each. The exam tests this directly because project type determines what configuration options are available, how boards behave, and how much control the administrator retains.

Software Projects: Scrum

Scrum projects in Jira Cloud use sprint-based boards and require administrators to manage sprint permissions, backlog visibility, and velocity reporting. Key admin considerations include:

  • Configuring sprint creation permissions within the project role structure
  • Understanding how the backlog and active sprint boards are generated from issue data
  • Managing column-to-status mapping on the Scrum board
  • Setting estimation methods (story points vs. original time estimate)

Software Projects: Kanban

Kanban projects replace the sprint backlog with a continuous flow board. Admin-specific knowledge includes:

  • Configuring WIP (work-in-progress) limits per column
  • Managing the Kanban backlog toggle and what triggers it
  • Understanding how workflow statuses map to board columns in a continuous delivery model
  • Configuring the Release Hub for Kanban projects

Business (Company-Managed vs. Team-Managed)

Business projects serve non-software teams. The critical admin distinction here is whether the project is company-managed or team-managed:

  • Company-managed projects use globally shared schemes that the Jira admin controls; changes affect all associated projects
  • Team-managed projects store configuration locally within the project itself; project admins have more autonomy, but global scheme changes do not apply
  • The exam frequently asks administrators to identify which project type is appropriate for a given organizational scenario

Core Project Settings Every Candidate Must Know

Beyond project type selection, Domain 4 covers the individual project settings that an administrator configures after a project is created. These settings are accessed via the project's admin panel and include details that directly affect usability, reporting, and security.

Project Details and Categories

Every Jira Cloud project has a name, key, URL, avatar, description, and project category. The project key is particularly important - once issues are created, the key cannot easily be changed without significant disruption. Administrators must understand the implications of project key selection at creation time. Project categories allow grouping of related projects for reporting and filtering, which matters in larger Jira instances.

Project Leads and Default Assignees

The project lead is an administrative setting that affects who receives certain notifications and appears as a point of contact. The default assignee setting - which can be set to the project lead or left unassigned - directly impacts how new issues are assigned when no specific assignee is selected. This is a classic scenario question: "Issues in Project X are being assigned to the project lead unexpectedly. What setting controls this behavior?"

Default Assignee vs. Project Lead: These are related but distinct settings. The project lead is a designated person; the default assignee configuration determines whether new issues automatically route to that person or remain unassigned. Confusing these two is a common mistake on exam scenarios.

Scheme Associations and Project-Level Configuration

Much of what makes a Jira Cloud project behave the way it does comes from schemes - reusable configuration templates that are associated with projects rather than embedded within them. Domain 4 tests whether candidates understand how to associate, reassociate, and troubleshoot scheme configurations at the project level.

The schemes most relevant to Domain 4 include:

  • Issue Type Scheme: Determines which issue types are available within the project. Associating the wrong scheme means teams cannot create the issue types they need.
  • Workflow Scheme: Maps issue types to specific workflows. A project without a correctly associated workflow scheme will use the default workflow, which is rarely appropriate for specialized teams.
  • Permission Scheme: Controls who can perform which actions within the project. This overlaps with Domain 3 but is addressed at the project level in Domain 4.
  • Notification Scheme: Determines who receives email notifications for issue events within the project.
  • Screen Scheme and Issue Type Screen Scheme: Controls which fields appear on issue create, edit, and view screens for each issue type.
  • Field Configuration Scheme: Determines field behavior (required, optional, hidden, rendered) per issue type.

Domain 4 questions often present scenarios where a project has been configured with mismatched schemes. Candidates must trace the configuration chain - from the issue type through the workflow scheme to the screen scheme - to identify where the breakdown occurred. This connects closely to the content covered in Domain 5: Issue Types, Fields and Screens, which is worth studying alongside Domain 4.

Board Configuration Within Projects

Boards in Jira Cloud are not just visual displays - they are filterable, configurable views that administrators must set up correctly for teams to work effectively. Domain 4 includes board configuration as a direct admin responsibility, particularly for company-managed software projects.

Column Mapping and Workflow Statuses

Each column on a Jira board represents one or more workflow statuses. The administrator must map statuses from the project's associated workflow to the appropriate board columns. If a status exists in the workflow but is not mapped to any column, issues in that status will not appear on the board - a common source of team confusion that the exam tests explicitly.

Board Filters and Swimlanes

A board's underlying filter determines which issues appear on it. The board filter is a JQL query, and administrators must understand how modifying this filter changes board visibility. Swimlanes further organize issues on the board - by assignee, epic, priority, or custom JQL - and configuring them is an administrative task covered in this domain.

Quick Filters

Quick filters are board-level JQL shortcuts that allow team members to narrow the board view with a single click. Adding, editing, or removing quick filters is an administrative action tested in Domain 4 scenarios.

Components, Versions, and Project-Level Features

Two project-level features - components and versions - are explicitly part of a Jira Cloud administrator's responsibility and appear in Domain 4 scenarios.

Components

Components are subsections of a project used to group issues into smaller parts. Administrators create and manage components, assign component leads, and set the default assignee behavior for each component (unassigned, component lead, or project lead). A common exam scenario: "When issues are created in the Authentication component, they should automatically be assigned to the security team lead. What configuration achieves this?" The answer lies in component-level default assignee settings.

Versions

Versions (also called releases) allow administrators to track when work is planned for completion or when it has been released. Administrators create, archive, and release versions within a project. Understanding how versions affect the Roadmap view and how released vs. unreleased versions filter reporting is tested at the practical level.

Key Takeaway

Components and versions are project-specific configurations - they do not live in shared schemes. This means changes to components or versions affect only the project where they are made, unlike scheme changes that ripple across all associated projects. Knowing this distinction helps you answer scope-related scenario questions correctly.

How to Approach Domain 4 Questions on Exam Day

Domain 4 questions are scenario-heavy, which means your exam strategy should be analytical rather than recall-based. When you encounter a Domain 4 question, use this mental framework:

  1. Identify the project type first. Company-managed vs. team-managed determines what options exist. If the scenario involves globally shared schemes, it's almost certainly a company-managed project.
  2. Trace the configuration chain. Board issue → check workflow status mapping. Missing field → check screen scheme. Wrong assignee → check default assignee settings at the project or component level.
  3. Eliminate global-scope answers. Domain 4 is about project-level configuration. If an answer choice involves changing a global Jira setting, it may be correct for a different domain but is often a distractor here.
  4. Watch for scheme vs. project-level distinctions. The exam will offer both scheme-level and project-level answers. If the scenario describes a problem affecting only one project, the correct fix is usually at the project level.

For broader test-taking strategy, the ACP-120 Exam Day Tips: 15 Strategies to Maximize Your Score covers time management and question prioritization techniques that apply across all domains.

Practicing with realistic scenario questions before the exam is essential. The ACP-120 practice tests on this site include Domain 4 scenarios that mirror the configuration-reasoning format of the actual Certiverse exam.

Scheduling Domain 4 Into Your Prep Plan

Because Domain 4 is a mid-weight domain (10-15%) with deep connections to both Domain 3 (permissions) and Domain 5 (issue types and screens), it should not be studied in isolation. The most effective approach is to sequence it between those two heavier domains.

Week 1

Domain 3 Foundation (Permissions)

  • Master permission schemes, project roles, and access control - the heaviest domain at 30-35%
  • Understand how permission schemes connect to projects, which sets up Domain 4 scheme association study
Week 2

Domain 4 Deep Dive (General Project Configuration)

  • Study project types (Scrum, Kanban, Business - company-managed vs. team-managed)
  • Practice scheme association scenarios: workflow, screen, field configuration, and notification schemes
  • Configure a real Jira Cloud sandbox: create a project, associate schemes, configure a board, add components and versions
  • Focus on board column mapping - trace statuses from workflow to board column to understand the full chain
Week 3

Domain 5 Transition (Issue Types, Fields, Screens)

  • Move into issue types and screen schemes, which extend the scheme knowledge built in Domain 4
  • Revisit Domain 4 board configuration in context - understand how screen schemes affect what users see when they open an issue from the board

For a full-exam study plan that covers all eight domains with sequencing rationale, see the ACP-120 Study Guide 2026: How to Pass on Your First Attempt. And if you're weighing whether the preparation investment makes sense for your career, the Is the ACP-120 Certification Worth It? Complete ROI Analysis 2026 provides a detailed breakdown of the career and compensation impact.

When you're ready to test your Domain 4 knowledge under realistic exam conditions, the ACP-120 practice exam platform lets you filter by domain so you can target exactly the project configuration scenarios you need to reinforce.

Frequently Asked Questions

How many questions in Domain 4 will appear on the ACP-120 exam?

Domain 4 accounts for 10-15% of the ACP-120 exam, which contains up to 75 questions. That translates to roughly 7-11 questions specifically on general project configuration topics like project types, scheme associations, board setup, and components/versions.

What is the difference between company-managed and team-managed projects for the exam?

Company-managed projects use globally shared schemes controlled by the Jira admin; changes to a scheme affect every project using it. Team-managed projects store configuration locally within the project, giving project admins more independence but removing access to global scheme administration. The exam tests scenarios where choosing the wrong project type creates administrative problems.

Does Domain 4 overlap with Domain 3 on permissions?

Yes, there is intentional overlap. Domain 3 covers the full permission model including permission schemes, project roles, and global access. Domain 4 addresses permission scheme association at the project level - that is, which scheme is connected to which project and what happens when the wrong scheme is applied. Study them sequentially for best results.

Are board configuration questions limited to Domain 4?

Board configuration is primarily tested in Domain 4, but workflow status mapping on boards connects to Domain 6 (Workflows and Automation). If a board column question involves the underlying workflow structure rather than the board admin settings themselves, it may be drawing on Domain 6 knowledge. Understanding both domains ensures you can handle hybrid scenario questions.

How should I practice for Domain 4 configuration-reasoning questions?

The most effective preparation is hands-on work in a Jira Cloud sandbox combined with scenario-based practice questions. Create projects of each type, deliberately misconfigure scheme associations, and troubleshoot the results. Pair this practical experience with domain-specific practice questions - available filtered by domain on the ACP-120 practice test platform - to build the configuration-reasoning skill the exam requires.

Ready to Start Practicing?

Test your Domain 4 knowledge with scenario-based practice questions that mirror the configuration-reasoning format of the actual ACP-120 exam. Filter by domain, track your weak areas, and build the practical confidence you need to hit 63% and earn your Atlassian Certified Professional credential.

Start Free Practice Test

Ready to pass your ACP-120 exam?

Put this into practice with free ACP-120 questions across every exam domain.