“"The practice exams helped me connect Agile concepts with real business analysis activities. I felt much more confident handling scenario-based questions after a few practice sessions."”
Olivia Bennett
Business Analyst
The IIBA-AAC is a 120-minute, 85-question exam delivered online through a remote proctor, and every question is written as a scenario rather than a straight definition-recall prompt. You're typically dropped into a short situation — a product owner disagreeing with a stakeholder over backlog order, a delivery team struggling to translate a roadmap item into a usable increment — and asked what an agile analyst would do next, or which principle the situation violates. The Certification of Competency in Business Analysis (CCBA®) is another IIBA certification for business analysis professionals seeking to demonstrate their skills and knowledge.
This format catches people who studied the Agile Extension to the BABOK® Guide the way they'd study a reference manual: memorizing definitions instead of internalizing how the seven agile analysis principles and the Business Analysis Core Concept Model (BACCM) actually get applied when a stakeholder is impatient and requirements are still shifting. IIBA doesn't publish an official passing score for the AAC; you get a pass/fail result on screen the moment you finish, and third-party estimates of the cut score vary — so the safest approach is to aim well above "just enough" rather than target a specific number that isn't officially confirmed.
The exam is organized around four Knowledge Areas from the Agile Extension to the BABOK Guide, version 2. Weightings below are IIBA's published Exam Blueprint; question counts are approximate, since IIBA rounds internally.
Domain | Weight | Approx. Questions (of 85) |
|---|---|---|
Agile Mindset | 30% | ~26 |
Strategy Horizon | 10% | ~9 |
Initiative Horizon | 25% | ~21 |
Delivery Horizon | 35% | ~30 |
Delivery Horizon carries the single largest share, which surprises candidates who assume the "mindset" domain — since it's listed first and sounds foundational — dominates the exam. In practice, more than a third of your questions will sit at the level of sprints, iterations, and the day-to-day analysis work inside a delivery team.
A few areas trip up otherwise well-prepared candidates:
Strategy Horizon, despite its low weight. At only 10% of the exam, people skim it — but its questions tend to be conceptually dense, covering how agile analysis connects to organizational strategy and portfolio-level decisions, a level most candidates' day-to-day experience doesn't touch.
The difference between "Follows" and "Enables" proficiency levels. The Agile Extension defines competencies at different depths per horizon, and several exam questions hinge on knowing which depth applies where — not just what the technique is.
BACCM applied to agile contexts specifically. Candidates who know BACCM from traditional business analysis exams often misapply it under agile framing, especially around "value" and "context" when priorities shift mid-iteration.
Distinguishing agile analysis from generic Scrum knowledge. The AAC is not a Scrum credential. Candidates with strong Scrum Master or product owner backgrounds sometimes answer from Scrum-framework instinct rather than from the Agile Extension's own vocabulary, and lose points on questions that expect the latter.
Because every AAC question is scenario-based, drilling isolated facts (three horizons, seven principles, 24 techniques) gets you only partway. The more useful discipline is reading each practice question's scenario twice before looking at the answer choices — once for the situation, once for what's actually being asked — since AAC scenarios often bury the question in the second half of a paragraph.
After each practice attempt, sort your misses by domain rather than by topic. If most of your errors cluster in Delivery Horizon, that's also where a wrong answer costs you the most exam weight, so it's the highest-leverage place to revisit the Agile Extension's descriptions of iteration-level analysis work. Repeating full-length attempts under a 120-minute clock also matters here specifically: at roughly 85 seconds per question, candidates who've only practiced untimed tend to run out of time on the longer Strategy and Initiative Horizon scenarios, which read longer than Agile Mindset questions.
Preparing primarily from generic Agile or Scrum resources instead of the Agile Extension to the BABOK Guide v2, which uses its own terminology the exam expects verbatim in spirit if not in wording
Underweighting Strategy Horizon study time to match its 10% share, then getting scenarios that require deeper conceptual reasoning than that percentage suggests
Treating the exam as recall-based and rushing through scenarios without identifying which principle or technique the situation is actually testing
Not practicing under the 120-minute constraint, leading to rushed answers on the exam's back half
Skipping the review of wrong answers on practice attempts, so the same conceptual gap (often around BACCM or proficiency-level distinctions) resurfaces on the actual exam
If you're new to agile business analysis: Budget four to six weeks. Spend the first two weeks building genuine familiarity with the Agile Extension's three horizons and BACCM before touching full-length practice attempts — jumping into scenario questions without that foundation tends to produce frustration rather than learning.
If you have two to three years of agile-context analysis work (IIBA's recommended experience level): Two to three weeks is usually enough. Your instincts will carry you through most scenarios; the value of practice attempts here is mainly in catching Agile Extension-specific terminology that differs from how your organization phrases the same concepts.
If you're retaking the exam: One to two weeks, concentrated entirely on your weak domains from the prior attempt. Don't restart from the beginning — retake candidates who re-review everything equally often repeat the same domain-specific mistakes because they never isolated what actually went wrong.
Last updated on Sep, 30 2026