ECBA Exam Flashcards

Q: How many questions are on the ECBA exam and how much time do I get?

The ECBA exam has 50 multiple-choice questions (situation-based and standard) to be completed in 75 minutes, delivered as an online remote proctored exam through PSI. There is no negative marking, so a wrong answer scores the same as a blank one.

Q: Do I need work experience or professional development hours to sit the ECBA exam?

No. IIBA removed the standalone professional development eligibility gate and application fee for ECBA. The only requirements are agreeing to the Code of Ethical Conduct and Professional Standards and the Certification and Recertification Terms and Conditions, and reading the ECBA Handbook.

Q: What is the ECBA exam pass rate and passing score?

IIBA does not publish a pass rate or a numeric passing score for the ECBA, or for any of its certification exams. Candidates receive an immediate pass/fail result on screen, followed by qualitative, domain-level performance feedback rather than a scaled score.

Q: How much does the ECBA cost, and what if I fail?

The standard fee is $395 (includes first-year IIBA membership) or $250 for a non-member, exam-only option. A rewrite (retake) costs $95 for members or $250 for non-members. IIBA does not impose a mandatory waiting period between attempts, but you must wait for IIBA to receive and post your result (up to 48 hours) before scheduling a rewrite.

Q: What are the nine domains on the ECBA Exam Blueprint V1.1?

Understanding Business Analysis (20%), Mindset for Effective Business Analysis (14%), and Implementing Business Analysis (6%) come from The Business Analysis Standard. Change, Need, Solution, Stakeholder, Value, and Context (10% each) come from the BABOK Guide and apply the BACCM.

Q: How does the ECBA differ from the CCBA and CBAP?

ECBA is IIBA's entry-level Certificate with no experience requirement and no expiration or CDU obligation. CCBA (mid-level) requires 3,750 hours of BA work experience, and CBAP (senior-level) requires 7,500 hours; both are Professional Certifications requiring 60 CDUs every 3 years to maintain.

Question 1

Change (BACCM Core Concept)

Accepted Answer

The act of transformation in response to a need (BABOK v3). Change never occurs in isolation -- it is always undertaken to address a specific Need and takes place within, and is constrained by, a Context.

Question 2

Need (BACCM Core Concept)

Accepted Answer

A problem or opportunity to be addressed (BABOK v3). Need is neutral -- it does not presuppose any particular Solution; jumping to a solution before the need is understood is a common business analysis failure.

Question 3

Solution (BACCM Core Concept)

Accepted Answer

A specific way of satisfying one or more needs in a context (BABOK v3). A solution that ignores its Context will fail to deliver the Value stakeholders expect.

Question 4

Stakeholder (BACCM Core Concept)

Accepted Answer

A group or individual with a relationship to the change, the need, or the solution (BABOK v3). Stakeholders determine what has Value, and that determination is always relative to a particular Context.

Question 5

Value (BACCM Core Concept)

Accepted Answer

The worth, importance, or usefulness of something to a stakeholder within a context (BABOK v3). Value is never absolute -- it is judged by a specific stakeholder from within specific circumstances.

Question 6

Context (BACCM Core Concept)

Accepted Answer

The circumstances that influence, are influenced by, and provide understanding of the change (BABOK v3). A shift in the understanding of any one BACCM concept requires the BA to reevaluate the other five.

Question 7

Definition of Business Analysis (BABOK v3)

Accepted Answer

"The practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders." A BA enables change -- sponsors and delivery teams own and execute it, and the work is anchored to value, not just documentation.

Question 8

The Five BABOK Perspectives

Accepted Answer

Agile, Business Intelligence, Information Technology, Business Architecture, and Business Process Management. Each is a lens on the same core BA work (elicitation, analysis, solution evaluation) -- not a separate methodology.

Question 9

Business Analysis Mindset -- Six Focus Areas

Accepted Answer

Per the Business Analysis Standard, an empowering mindset is built around: achieving organizational outcomes, discovering value, adopting principles, deciding on approach, developing foundational competencies, and using foundational techniques. It is built through deliberate practice, not innate talent.

Question 10

BA Principles: See the Whole & Avoid Waste

Accepted Answer

See the Whole = analyze needs in the big-picture context and ask why a change is necessary before acting on a narrow request. Avoid Waste = identify which activities add value and remove those that don't. Two of the Business Analysis Standard's seven core principles.

Question 11

Five Foundational Competencies

Accepted Answer

Adaptability, Facilitation, Leadership and Influencing, Problem Solving, and Systems Thinking -- identified by the Business Analysis Standard as essential across all BA work. The BABOK Guide expands these into 29 underlying competencies (Chapter 9).

Question 12

Predictive vs. Adaptive BA Approach

Accepted Answer

Predictive (plan-driven/waterfall): requirements defined in detail up front, formally baselined, changed only through a controlled change process -- suits stable, regulated needs. Adaptive (Agile/Scrum/Kanban): requirements captured at a high level and progressively elaborated in iterations -- suits evolving, uncertain needs.

Question 13

BA Roles and Reporting Structures

Accepted Answer

BA work is performed under many job titles (business systems analyst, business architect, product owner, data analyst), not only "Business Analyst." A BA may report through a centralized center of excellence, a decentralized/embedded structure, or a matrixed structure; influence comes from facilitation skill and analytical credibility, not positional authority.

Question 14

Requirement vs. Design

Accepted Answer

A requirement is a usable representation of a need -- it describes what is required, without prescribing how it will be delivered. A design is a usable representation of a solution -- it describes how the need will be met once options are evaluated and a direction is chosen.

Question 15

Business Requirements

Accepted Answer

Goals, objectives, and outcomes explaining why a change is being initiated -- the broadest, least detailed category in the requirements classification schema. Example: "Reduce customer onboarding time by 30% within one year."

Question 16

Stakeholder Requirements

Accepted Answer

The needs of a specific stakeholder or group that must be met to achieve the business requirements. They bridge business requirements and solution requirements, answering "what does this stakeholder need?"

Question 17

Solution Requirements -- Functional

Accepted Answer

The capabilities and behaviors a solution must have -- answers "what must the solution do?" Example: "The system shall auto-populate the application form from the existing customer record."

Question 18

Solution Requirements -- Non-Functional

Accepted Answer

The quality-of-service conditions a solution must satisfy: performance, security, usability, availability, and capacity -- answers "how well must the solution do it?" Example: "The form shall auto-populate within 2 seconds of customer lookup."

Question 19

Transition Requirements

Accepted Answer

Capabilities needed only to move from the current state to the future state, such as data conversion or parallel-run procedures. Unlike the other three categories, transition requirements are temporary and are retired once the transition is complete.

Question 20

Contextual Factors Influencing Change

Accepted Answer

Three categories: organizational (structure, culture, processes, policies), environmental (regulatory requirements, market conditions, competitor actions, technology trends), and stakeholder (readiness for change, resistance or support, prior change experience).

Question 21

Impact Analysis

Accepted Answer

Identifies which requirements, designs, processes, systems, and stakeholders are affected by a proposed or actual change, using requirements traceability. Each change is evaluated by weighing benefit against cost, urgency, and risk before a disposition of approve, reject, or defer.

Question 22

Nine Characteristics of Good Requirements

Accepted Answer

BABOK v3: atomic, complete, consistent, concise, feasible, unambiguous, testable, prioritized, and understandable.

Question 23

Atomic Requirement

Accepted Answer

A requirement that expresses a single, self-contained need rather than bundling multiple needs into one statement -- one of BABOK's nine characteristics of a good requirement.

Question 24

Elicitation -- Definition and Activities

Accepted Answer

BABOK v3: the process of drawing out, exploring, and identifying information relevant to a change from stakeholders or other sources. Three activities: Prepare for Elicitation, Conduct Elicitation Activity, and Confirm Elicitation Results.

Question 25

Interviews and Observation

Accepted Answer

Interviews are structured (fixed question list) or unstructured (open-ended), depending on how well the topic is already understood. Observation (job shadowing) is active (the BA asks questions during the task) or passive (the BA only watches and records).

Question 26

Requirements Verification

Accepted Answer

Ensures a requirement or design is well-formed, at the right level of abstraction, and meets quality standards (BABOK v3). Verification asks: was the requirement written correctly?

Question 27

Requirements Validation

Accepted Answer

Ensures a requirement or design delivers business value and aligns to business goals and objectives (BABOK v3). Validation asks: was the correct requirement identified? A requirement can pass verification yet still fail validation if it no longer supports a business objective.

Question 28

Acceptance Criteria vs. Evaluation Criteria

Accepted Answer

Acceptance criteria describe the minimum set of requirements a solution must meet to be acceptable to key stakeholders. Evaluation criteria support a broader comparative assessment of a solution, or competing options, against a set of standards.

Question 29

Feasibility Assessment

Accepted Answer

Comparing solution options covers three factors: technical (can it be built with available technology/skills), operational (can the organization run it day to day), and economic (is it cost-effective). Risk Analysis and Management is the named BABOK technique used alongside feasibility to weigh implementation, operational, adoption, technology, and financial risk.

Question 30

RACI Matrix

Accepted Answer

Responsible (does the work) and Consulted (two-way input gathered before a decision) can involve multiple stakeholders. Exactly one stakeholder is ever Accountable for a given activity. Informed means the stakeholder is only notified after the fact.

Question 31

Four Communication Skills

Accepted Answer

BABOK v3 identifies four underlying communication skills: verbal, non-verbal, written, and listening. Active listening includes restating what a stakeholder said in the analyst's own words and watching for non-verbal cues that may signal unspoken disagreement.

Question 32

Outcome vs. Output

Accepted Answer

An output is the tangible or intangible artifact a change produces (e.g., a new report). An outcome is the end benefit realized because of that output (e.g., faster decisions). Tracking progress focuses on outcomes, not just outputs.

Question 33

Potential Value vs. Realized Value

Accepted Answer

Potential value is the value expected or projected before a solution is implemented. Realized (actual) value is what the solution genuinely delivers, confirmed only after it is in use. A KPI is a metric explicitly tied to a solution's success against a business objective; leading indicators predict future performance, lagging indicators confirm outcomes after they occur.

Question 34

Constraint vs. Dependency

Accepted Answer

A constraint is an internal restriction imposed by the organization or team that limits the solution options available. A dependency is a relationship in which one element relies on the completion or existence of another (BABOK v3).

Question 35

Knowledge Area: Business Analysis Planning and Monitoring

Accepted Answer

Describes how a business analyst determines which activities are necessary to perform business analysis on a given initiative, including the BA approach, stakeholder engagement, governance, and how BA performance itself is monitored and improved.

Question 36

Knowledge Area: Elicitation and Collaboration

Accepted Answer

Describes how a business analyst prepares for and conducts elicitation activities, confirms the results, and collaborates with stakeholders to communicate information throughout an initiative.

Question 37

Knowledge Area: Requirements Life Cycle Management

Accepted Answer

Describes how a business analyst manages and maintains requirements and design information from inception to retirement, including tracing, maintaining, prioritizing, and approving requirements, and managing changes to them.

Question 38

Knowledge Area: Strategy Analysis

Accepted Answer

Describes how a business analyst analyzes the current state of an enterprise, defines a desired future state, assesses risks, and defines a change strategy to move from the current state to the future state.

Question 39

Knowledge Area: Requirements Analysis and Design Definition

Accepted Answer

Describes how a business analyst structures, organizes, specifies, and models requirements and designs, verifies and validates information, and identifies solution options that meet business needs.

Question 40

Knowledge Area: Solution Evaluation

Accepted Answer

Describes how a business analyst assesses the performance of, and value delivered by, a solution in use, and recommends actions to increase the value the solution delivers.

Question 41

Technique: Brainstorming

Accepted Answer

Generates a large volume of creative ideas from a group by deferring judgment during idea generation; ideas are evaluated only after generation is complete.

Question 42

Technique: Interviews

Accepted Answer

Elicits information one-on-one or in small groups; best suited to a few knowledgeable stakeholders or sensitive topics. Structured interviews use a fixed question list; unstructured interviews are open-ended exploration.

Question 43

Technique: Workshops

Accepted Answer

Brings diverse stakeholders together in a facilitated session to reach group consensus on requirements quickly.

Question 44

Technique: Document Analysis

Accepted Answer

Reviews existing business or technical documentation (policies, procedures, system documentation) to establish the as-is state without requiring additional stakeholder time.

Question 45

Technique: MoSCoW Prioritization

Accepted Answer

Sorts requirements into four categories: Must have (non-negotiable), Should have, Could have, and Won't have this time. "Won't have" means deferred from the current scope, not permanently rejected.

Question 46

Technique: User Stories

Accepted Answer

Captures a requirement briefly from the perspective of the person who wants the capability, typically in an "As a... I want... so that..." format, paired with acceptance criteria to drive iterative delivery.

Question 47

Technique: SWOT Analysis

Accepted Answer

Organizes internal Strengths and Weaknesses and external Opportunities and Threats to support strategic decision-making.

Question 48

Technique: Root Cause Analysis

Accepted Answer

Distinguishes a problem's underlying cause from its visible symptoms, often using the 5 Whys or a fishbone (Ishikawa) diagram. It looks backward at a known problem, while Risk Analysis and Management looks forward at potential future uncertainty.

Question 49

29 Underlying Competencies -- Six Categories

Accepted Answer

BABOK Chapter 9 groups 29 underlying competencies into six categories: Analytical Thinking & Problem Solving (7), Behavioural Characteristics (5), Business Knowledge (5), Communication Skills (4), Interaction Skills (5), and Tools and Technology (3). All 29 are considered testable on the ECBA.

Question 50

Facilitation vs. Leadership and Influencing

Accepted Answer

Facilitation means guiding a group neutrally toward its own outcome. Leadership and Influencing means actively persuading stakeholders toward a specific direction. Both are Interaction Skills competencies (BABOK Chapter 9) but differ in whether the BA steers the outcome.

Free ECBA Exam Flashcards

Filter by Topic

Jump to Card

About These ECBA Flashcards

Topics Covered

Frequently Asked Questions

ECBA Entry Certificate in Business Analysis

Explore More IIBA Certifications

CBAP Certified Business Analysis Professional

IIBA CBDA Certification in Business Data Analytics

CCBA Certification of Capability in Business Analysis

IIBA AAC Agile Analysis Certification

IIBA CCA Certificate in Cybersecurity Analysis

IIBA CPOA Certificate in Product Ownership Analysis

More From This Family