CABA logo
Focused certification exam prep
Start practice

CABA Exam Domains 2026: Complete Guide to All 8 Content Areas

TL;DR
  • CABA's Common Body of Knowledge was organized into exactly eight domains, from BA principles to performance based contracting.
  • The final exam used 100 objective multiple-choice questions in 75 minutes with a 70% pass mark.
  • Voucher sales ended August 1, 2025, and all exams, including Take2 retakes, ended February 1, 2026.
  • No new CABA exam sittings are available; this guide serves as a reference to the domains that defined the credential.

Overview: The CABA Common Body of Knowledge

The Certified Associate Business Analyst (CABA) credential was built around a Common Body of Knowledge (CBOK) organized into eight distinct domains. Unlike broad, loosely defined competency frameworks, CABA's CBOK was deliberately narrow and practical - it covered the full arc of a business analyst's work, from foundational principles through requirements gathering, testing, and even the niche mechanics of commercial off-the-shelf software procurement. This structure made CABA distinctive among BA-adjacent credentials of its era, and understanding those eight domains is still the fastest way to understand what the certification actually measured.

This guide breaks down each of the eight domains in detail, explains how they mapped to the exam format, and - because the program's history matters for anyone researching it today - clarifies exactly where CABA stands now. If you're building a broader study plan, pair this domain breakdown with our CABA Study Guide 2026 and our one-page CABA cheat sheet for quick review.

Important: CABA's Current Status

Program Retired: PeopleCert retired the DevOps Institute CABA credential. Voucher sales ended August 1, 2025, and all exams - including Take2 retake attempts - ended February 1, 2026. There are no new CABA exam sittings available going forward.

CABA originated with the International Software Certification Board and was administered by QAI Global Institute, with Pearson VUE handling exam scheduling and delivery. The credential sat as the associate-level tier directly below the practitioner-level Certified Software Business Analyst (CSBA), giving candidates a structured path from foundational knowledge into more advanced practice.

Because the program has been formally retired, this article is intended as a reference resource: for professionals who already hold the CABA designation and want to articulate what it covered, for employers evaluating a candidate's resume, and for anyone researching the history of BA competency frameworks. If you're trying to determine whether pursuing this path still makes sense for your career, our analysis on whether CABA certification was worth it and our breakdown of CABA certification cost both dig into that question directly.

Key Takeaway

Treat this domain breakdown as a knowledge reference rather than a registration guide - the exam itself is no longer being administered, but the underlying BA competencies remain relevant to how the role is evaluated in the field.

Domain 1: Business Analyst Principles and Concepts

Business Analyst Principles and Concepts

This foundational domain established the vocabulary and mental models a certified associate needed before touching any technical BA task. It framed the role itself: what a business analyst is responsible for, how that role differs from a project manager or systems analyst, and where it fits inside a software delivery organization.

  • Core definitions of the business analyst role and its boundaries relative to adjacent roles
  • The BA's position across the software development lifecycle
  • Foundational concepts underpinning every other domain in the CBOK
  • Ethical and professional conduct expectations for practicing analysts

Domain 2: Management and Communication Skills

Management and Communication Skills

Because business analysts spend much of their time translating between stakeholders, this domain tested the softer - but heavily examined - skills of managing conversations, expectations, and information flow across a project.

  • Stakeholder identification and communication planning
  • Facilitation techniques for requirements sessions and status reviews
  • Conflict resolution and negotiation in cross-functional teams
  • Reporting and documentation practices that keep management informed

Domain 3: Define, Build, Implement and Improve Work Processes

Define, Build, Implement and Improve Work Processes

This domain covered process-oriented thinking - the ability to map how work actually happens, identify inefficiencies, and design improved workflows. It reflected the CABA program's emphasis on business process work as a core BA competency, not a side skill.

  • Process mapping and current-state versus future-state analysis
  • Techniques for identifying bottlenecks and redundant steps
  • Building and documenting new or revised work processes
  • Continuous improvement approaches applied to business workflows

Domain 4: Business Fundamentals

Business Fundamentals

This domain grounded candidates in general business literacy - the baseline knowledge needed to understand why a project exists commercially before diving into requirements or technical specifics.

  • Core business concepts: organizational structure, strategy, and objectives
  • How business goals translate into project justification
  • Financial and operational basics relevant to BA decision-making
  • Connecting business context to downstream requirements work

Domain 5: Requirements

Requirements

Requirements work sits at the heart of the business analyst profession, and this domain was correspondingly central to the CABA CBOK. It covered the full requirements lifecycle rather than a single technique.

  • Elicitation methods for gathering requirements from stakeholders
  • Documenting, categorizing, and prioritizing requirements
  • Validating requirements against business needs
  • Managing requirements changes throughout a project
Why Requirements Carried Weight: Requirements work touches nearly every other domain - process design, acceptance testing, and even COTS evaluation all depend on requirements being captured correctly first. Candidates who understood this domain thoroughly had an easier time connecting concepts across the rest of the exam.

Domain 6: Software Development Processes, Project and Risk Management

Software Development Processes, Project and Risk Management

This domain placed the BA role inside the broader context of how software gets built and delivered, including the project management and risk considerations that shape a BA's day-to-day work.

  • Familiarity with common software development lifecycle models
  • The BA's touchpoints with project planning and scheduling
  • Identifying and tracking project risks tied to requirements or scope
  • Coordinating with project managers and development teams through delivery

Domain 7: Acceptance Testing

Acceptance Testing

This domain addressed the BA's role in verifying that delivered software actually satisfies the requirements defined earlier - closing the loop between what was asked for and what was built.

  • Designing acceptance criteria tied directly to documented requirements
  • Distinguishing acceptance testing from other testing types (unit, system, integration)
  • Coordinating user acceptance testing sessions with business stakeholders
  • Sign-off processes and how testing outcomes feed back into requirements management

Domain 8: Commercial Off-the-Shelf Software and Performance Based Contracting

COTS and Performance Based Contracting

The most specialized of the eight domains, this section addressed scenarios where an organization buys rather than builds software - and the contracting structures used to hold vendors accountable for performance outcomes.

  • Evaluating commercial off-the-shelf (COTS) software against business requirements
  • Build-versus-buy analysis for software acquisition decisions
  • Performance based contracting principles and vendor accountability structures
  • Integrating purchased software into existing business processes

How the Domains Mapped to the Exam Format

The final legacy CABA exam specification used 100 objective multiple-choice questions delivered in a 75-minute window, with a 70% pass mark required to earn the credential. Questions were drawn across all eight domains of the CBOK, meaning candidates couldn't specialize in a handful of favorite topics - every domain from Business Analyst Principles and Concepts through COTS and Performance Based Contracting was represented in the question pool.

Because the format was purely objective (no scenario-based simulations or performance tasks), success depended heavily on precise recall of terminology and concepts across all eight areas rather than applied problem-solving under simulated work conditions. For a deeper look at exactly what scoring 70% required in practice, see our breakdown of the CABA passing score, and for a candid assessment of how challenging that bar actually was, read how hard the CABA exam really was.

DomainCore Focus Area
1. BA Principles and ConceptsFoundational role definitions and BA fundamentals
2. Management and Communication SkillsStakeholder facilitation and reporting
3. Define/Build/Implement/Improve Work ProcessesProcess mapping and workflow improvement
4. Business FundamentalsGeneral business and organizational literacy
5. RequirementsElicitation, documentation, validation, change control
6. Software Development Processes, PM and RiskSDLC context, project coordination, risk tracking
7. Acceptance TestingVerifying delivered software against requirements
8. COTS and Performance Based ContractingSoftware procurement and vendor performance contracts

Who Valued the CABA Credential

CABA was positioned as an entry point for professionals moving into business analysis roles within software-focused organizations - particularly environments where BAs worked closely with development teams, tested delivered functionality against requirements, and occasionally evaluated purchased software rather than custom builds. Because the CBOK explicitly included COTS evaluation and performance based contracting, it also had relevance for analysts working in procurement-heavy environments, including government and public-sector contracting contexts where vendor accountability language matters.

The associate-to-practitioner structure - CABA sitting below the Certified Software Business Analyst (CSBA) - meant it was commonly viewed as a stepping stone credential rather than a terminal one, useful for demonstrating baseline competency before advancing further. For a broader picture of the roles this kind of credential connected to, see our overview of CABA jobs and our detailed look at CABA salary data.

Associate vs. Practitioner: CABA measured foundational, objective knowledge across eight domains. The practitioner-level CSBA sat above it, reflecting a deeper, more applied level of business analysis competency.

Domain-by-Domain Study Sequencing

For anyone reviewing this material - whether preparing historically, studying for a related role, or brushing up on BA fundamentals - sequencing matters more than cramming. Because Requirements (Domain 5) touches nearly every other domain, it makes sense to study it early so the concepts reinforce the material that follows.

Week 1

Foundations

  • Domain 1: Business Analyst Principles and Concepts
  • Domain 4: Business Fundamentals
Week 2

Core Skills

  • Domain 2: Management and Communication Skills
  • Domain 5: Requirements
Week 3

Process and Delivery

  • Domain 3: Define, Build, Implement and Improve Work Processes
  • Domain 6: Software Development Processes, Project and Risk Management
Week 4

Specialized Topics and Review

  • Domain 7: Acceptance Testing
  • Domain 8: COTS and Performance Based Contracting
  • Full-domain review using practice questions

Regardless of which domain you're reviewing, running timed practice questions on our practice test platform is the most reliable way to check whether you can recall terminology under exam-like time pressure - especially given the compressed 75-minute window the real exam used. Combine that with the structured walkthrough in our CABA study guide for a complete review plan.

Key Takeaway

Study Requirements (Domain 5) early - it reinforces concepts used in Acceptance Testing, Work Processes, and even COTS evaluation, making the remaining domains easier to absorb.

Frequently Asked Questions

How many domains did the CABA exam cover?

The CABA Common Body of Knowledge was organized into eight domains, ranging from Business Analyst Principles and Concepts to Commercial Off-the-Shelf Software and Performance Based Contracting.

Can I still register for the CABA exam?

No. Voucher sales ended August 1, 2025, and all exams, including Take2 retakes, ended February 1, 2026. There are no new CABA exam sittings available.

How was the CABA exam structured?

The final legacy exam specification used 100 objective multiple-choice questions delivered in 75 minutes, with a required 70% pass mark, drawn across all eight CBOK domains.

Which domain was the most heavily emphasized?

Requirements (Domain 5) was central to the CBOK because it connects directly to process work, acceptance testing, and other domains, though all eight domains were represented in the question pool.

Who administered the CABA exam before it was retired?

The program originated with the International Software Certification Board and was administered by QAI Global Institute, with Pearson VUE used for exam scheduling, before PeopleCert retired the credential.

For more context on the credential's structure, eligibility, and how it compared to related paths, explore our guides on CABA requirements, CABA exam dates and testing windows, and what CABA stands for. You can also test your recall of these eight domains right now using practice questions modeled on the legacy CABA format.

Ready to pass your CABA exam?

Put this into practice with free CABA questions across every exam domain.