ECBA Practice Test
Free ECBA (Entry Certificate in Business Analysis) practice questions in English, Chinese, and Spanish — the core concept model, elicitation and requirements, stakeholders, value, context, and the techniques the blueprint names.
Choose a domain
Study resources
Links open Amazon search results. As an Amazon Associate, Quibank earns from qualifying purchases.
Practice questions based on the IIBA ECBA Exam Blueprint, The Business Analysis Standard and the BABOK Guide. ECBA, IIBA and BABOK are marks of the International Institute of Business Analysis; this site is not affiliated with or endorsed by IIBA. The exam was restructured around nine domains, so older preparation material organised by the previous knowledge areas is out of date — study the current blueprint on IIBA's site. IIBA publishes no passing score, so the threshold used here is our own practice target, not an official one.
About the IIBA ECBA exam
The Entry Certificate in Business Analysis is IIBA's foundational credential, and the unusual thing about it is the door: there is no experience requirement, no degree requirement and no prior certification to earn first. You create an account, buy the exam and sit it. That makes it the realistic first step for a coordinator, tester, support analyst or career changer who keeps being handed analysis work without the title. The exam was rebuilt around nine domains drawn from The Business Analysis Standard and the BABOK Guide, and it is written as situations rather than definitions: you are shown a moment in a piece of work and asked what a foundational practitioner does next. Every question here appears in English, Chinese and Spanish with the reasoning explained.
How to study for the ECBA
Start by getting the structure right, because this is where most preparation goes wrong. The exam is organised into nine domains. Three are foundational and come from The Business Analysis Standard: what business analysis is and how it creates value, the mindset and principles a practitioner works from, and how business analysis gets implemented — who performs it, how predictive and adaptive approaches differ, and the distinction between requirements and designs. The remaining six take the core concepts one at a time and test them as practical work. The foundational three carry the heavier weighting, which surprises people who expect a techniques exam; understanding what the practice is for is worth more marks than memorising any list.
Then learn the core concept model until it is a reflex rather than a list you can recite. Change, need, solution, stakeholder, value and context are not six topics to be revised separately; they are six lenses you hold over the same situation at once. The most reliable way to practise is to take any scenario — from this bank, from your own work — and ask the six questions in order: what is changing, what need is behind it, what is being proposed, who is affected, what value is expected, and what constraints surround it. Questions that look hard usually become easy the moment you notice which of the six the person in the scenario has skipped.
Learn the named techniques for what they are for, not for how to run them. The blueprint names a specific set — brainstorming, document analysis, interviews, workshops, process and data modelling, root cause analysis, business rules analysis, SWOT, user stories, backlog management and the rest — and at this level you are asked to recognise which one suits a situation and what its limitations are, not to facilitate one. So study each as a short answer to three questions: what does it produce, when would you reach for it, and when would it mislead you. That framing also protects you from the commonest trap in this part of the exam, which is a technique that would genuinely work but is the wrong choice because of who is available, how much time there is, or how much is already written down.
Finally, practise reading questions at the right altitude. This is a foundational certificate, and a great many of its questions turn on knowing the limits of the role: you gather and document, you check alignment and flag conflicts, you contribute evidence to a recommendation — and someone else decides. An answer that has a junior practitioner resolving a dispute between two departments, approving a design or choosing between solution options on their own authority is usually wrong for that reason alone, however sensible it sounds. Pair that habit with the requirements-and-designs distinction, which is tested more often than its size suggests, and you will have covered the two things this exam most reliably rewards.
FAQ
Do I need work experience or a degree to sit the ECBA?
No. The ECBA has no experience requirement, no education requirement and no professional development hour requirement, and it does not sit behind another certification. IIBA's own candidate roadmap goes straight from creating an account to purchasing the exam to scheduling it — there is no application to be reviewed or approved first, which is what sets it apart from most credentials at this level. That also means the work of qualifying is entirely study rather than paperwork. Terms are set by IIBA and can change, so confirm the current ones before you pay.
Is the ECBA still organised around the six BABOK knowledge areas?
No, and this is the single most common way people study the wrong thing. The exam is now built on nine domains: three foundational ones drawn from The Business Analysis Standard, and six that take the Business Analysis Core Concept Model — Change, Need, Solution, Stakeholder, Value and Context — and test each as practical work. A great deal of older preparation material, including material still ranking well in search, is organised by the earlier knowledge-area structure. It is not useless, because the underlying content overlaps heavily, but the proportions and the framing are wrong. Read the current blueprint on IIBA's own site before trusting any study plan.
ECBA or CAPM — which one should I take first?
They answer different questions about a piece of work. The CAPM is a project management credential: it is about running the work — how it is sequenced, scheduled, resourced and governed. The ECBA is about deciding whether the right thing is being built at all — understanding the need, the stakeholders, the value and the context, and then validating that the solution actually delivers. They overlap around requirements and stakeholders, and a lot of people eventually hold both. Choose by what your next role asks of you: if you are being handed delivery and coordination, start with the project credential; if you are the person expected to work out what is actually needed, start here.
What is the BACCM, and why does the exam keep returning to it?
The Business Analysis Core Concept Model names six things that are present in every piece of analysis work — a change, a need, a solution, stakeholders, value and a context — and its point is that none of them can be understood alone. Change what the solution is and the value changes; misjudge the context and the need you captured stops making sense. The exam uses it as a completeness check, which is why so many questions describe someone who has considered most of the six and quietly neglected one. If you learn to read a scenario by asking which of the six is missing, a large share of the exam becomes the same question wearing different clothes.
Do I have to be a business analyst for this to be worth it?
No, and the certificate's own material is explicit that business analysis is frequently performed by people whose job title says something else — product owners, testers, support and operations staff, subject matter experts, project coordinators. Several domains are written around exactly that situation: recognising that analysis work is being done, knowing which parts a foundational practitioner decides and which parts get escalated, and choosing an approach that fits the context rather than a preference. If your work already involves working out what people need and writing it down so someone can build it, this is a description of what you are doing.