Graded Mock Test for IIBA-ECBA Certification :Business Analysis: Preparation Exam for ECBA Certification (IBM Business Analyst Professional Certificate) Answers 2025
Question 1
Primary purpose of requirements analysis and design?
❌ Validate solutions against business objectives
❌ Manage stakeholder engagement
✅ Define requirements and designs that meet stakeholder needs
❌ Measure project performance
Explanation:
This phase focuses on clearly defining what is needed and how it should be designed.
Question 2
Which task ensures alignment with stakeholder needs?
❌ Define solution scope
❌ Verify requirements
✅ Validate requirements
❌ Plan requirements management
Explanation:
Validation ensures requirements meet stakeholder expectations.
Question 3
What factors should be considered when validating requirements?
❌ Minimizing stakeholder involvement
❌ Preferences of the project manager
❌ Alignment with business goals
✅ Ensuring requirements are usable and high-quality
Explanation:
Validation checks quality, usability, and fitness for purpose.
Question 4
What does traceability enable?
❌ Reducing validation
❌ Monitoring satisfaction
✅ Connecting requirements to objectives and solutions
❌ Prioritizing designs
Explanation:
Traceability links requirements → solutions → objectives.
Question 5
Characteristic of well-defined requirements?
❌ Focus on as-is only
✅ Complete and concise
❌ Open-ended
❌ Minimize feedback
Explanation:
Good requirements are clear, complete, and concise.
Question 6
Benefit of workshops in requirements modeling?
❌ Reduce documentation
❌ Replace interviews
✅ Enable collaboration among stakeholders
❌ Eliminate conflicts
Explanation:
Workshops encourage shared understanding and collaboration.
Question 7
Multiple languages under budget constraints – which characteristic?
❌ Completeness
✅ Feasibility
❌ Atomicity
❌ Unambiguousness
Explanation:
Feasibility checks if a requirement is realistic within constraints.
Question 8
Breaking tasks into hierarchy – which technique?
❌ Activity flow modeling
❌ Data modeling
✅ Functional decomposition
❌ Prototyping
Explanation:
Functional decomposition breaks work into smaller functions/tasks.
Question 9
Which improvement opportunity streamlines workflows?
✅ Increasing efficiencies
❌ Reducing costs
❌ Identifying capabilities
❌ Improving access
Explanation:
Workflow optimization focuses on efficiency gains.
Question 10
Comparing custom vs off-the-shelf solutions is called?
❌ Stakeholder analysis
❌ Requirements modeling
❌ Functional decomposition
✅ Evaluating solution approaches
Question 11
Best example of requirements validation?
✅ Stakeholder reviews to confirm alignment
❌ Writing without review
❌ Technical-only approval
❌ Ignoring conflicts
Question 12
Documenting reasoning behind solution choice uses which model?
❌ Capability
✅ Rationale
❌ Activity flow
❌ Data & information
Question 13
Best technique to choose between two tools?
✅ Decision analysis
❌ Workshops
❌ Document needs
❌ System interdependencies
Question 14
Focus of data modeling?
❌ Workflows
❌ Risks
❌ Stakeholders
✅ Representing data structures and relationships
Question 15
Best prioritization technique?
❌ Root cause analysis
❌ Risk analysis
❌ Stakeholder mapping
✅ MoSCoW
Question 16
How does stakeholder mapping help?
✅ Identifies and categorizes stakeholders
❌ Analyze workflows
❌ Develop tests
❌ Track deliverables
Question 17
Visualizing process flow – which technique?
❌ Root cause analysis
❌ Benchmarking
❌ Brainstorming
✅ Process modeling
Question 18
Purpose of SWOT analysis?
❌ Monitor risks
❌ Metrics
❌ Collaboration
✅ Identify strengths, weaknesses, opportunities, threats
Question 19
Primary goal of balanced scorecard?
❌ Prototypes
❌ Workflows
❌ Risk analysis
✅ Align business activities to strategy
Question 20
What is a use case?
❌ System risks
❌ Business performance
❌ Stakeholder maps
✅ Interactions between users and a system
Question 21
Traceability linking business → solution requirements?
❌ Satisfy
✅ Derive
❌ Necessity
❌ Validate
Question 22
Primary goal of maintaining requirements?
✅ Ensure accuracy, consistency, reusability
❌ Support testing only
❌ Define acceptance
❌ Identify priorities
Question 23
Resolving conflicts & gaining consensus demonstrates which core concept?
❌ Value
✅ Stakeholder
❌ Change
❌ Context
Question 24
High cost but long-term value – which factor matters most?
❌ Penalty
❌ Risk
❌ Cost
✅ Benefit
Question 25
Best way to resolve requirement disagreement?
❌ Approve least controversial
✅ Facilitate discussions to find common ground
❌ Delay approval
❌ Sponsor-only decision
Question 26
First factor to assess for change request?
❌ Traceability
❌ Approval
✅ Impact on schedule and other requirements
❌ Time sensitivity
Question 27
Primary purpose of change management?
❌ Ensure consensus
✅ Evaluate value, impact, feasibility
❌ Update repository
❌ Maintain traceability
Question 28
Tool to show requirement links to tests & objectives?
❌ Stakeholder register
❌ Requirements repository
✅ Traceability matrix
❌ Prioritization framework
Question 29
Low current benefit but future value – best approach?
❌ Defer automatically
❌ Focus only on now
✅ Balance current needs with long-term goals
❌ Reject
Question 30
Linking features to requirements demonstrates which core concept?
❌ Solution
❌ Stakeholder
✅ Value
❌ Context
Question 31
System upgrade due to peak load issues represents which core concept?
❌ Change
❌ Solution
✅ Need
❌ Value
Question 32
Functional + non-functional requirements represent which concept?
❌ Value
❌ Context
❌ Need
✅ Solution
Question 33
Mapping preferences, trends, goals focuses on which concept?
❌ Stakeholder
✅ Context
❌ Change
❌ Need
Question 34
How is BABOK organized?
❌ Job descriptions
❌ PM phases
❌ Industry methods
✅ Knowledge areas, techniques, competencies
Question 35
Who is a business analyst?
✅ A professional who elicits, analyzes, and communicates requirements to enable business change
❌ Project manager
❌ Technical designer
❌ Stakeholder
Question 36
Documentation difference: predictive vs adaptive?
❌ Both ignore docs
❌ Predictive excludes reviews
❌ Adaptive forbids docs
✅ Predictive uses baselined docs; adaptive updates continuously
Question 37
Primary objective of BA governance?
✅ Define decision-making processes for BA work
❌ Reduce change control
❌ Force agreement
❌ Manage budgets
Question 38
Critical component of change control?
❌ Avoid formal procedures
❌ Minimize involvement
❌ Auto-approve changes
✅ Document changes and their impacts
Question 39
Interviewing stakeholders – which step?
❌ Conduct elicitation
✅ Prepare for elicitation
❌ Manage collaboration
❌ Confirm results
Question 40
Ambiguities found after workshop – next step?
❌ Communicate info
✅ Confirm elicitation results
❌ Prepare
❌ Conduct elicitation
Question 41
Best elicitation for dispersed stakeholders?
✅ Surveys and questionnaires
❌ Workshops
❌ Observations
❌ Document analysis
Question 42
Group discussion after feature suggestions – which elicitation?
❌ Document analysis
❌ Research
❌ Experiment
✅ Collaborative elicitation
Question 43
Quick summary after brainstorming – best format?
❌ Formal documentation
❌ Document analysis
✅ Informal communication
❌ Interactive presentation
Question 44
Stakeholder disengaged during workshop – what to do?
❌ Conduct elicitation
✅ Manage stakeholder collaboration
❌ Communicate info
❌ Confirm results
Question 45
Analyzing test data for feasibility – which elicitation?
✅ Experiment elicitation
❌ Survey
❌ Research
❌ Collaborative
Question 46
Summarizing focus group & interview results is which activity?
❌ Communicate info
❌ Prepare elicitation
✅ Confirm elicitation results
❌ Conduct elicitation
Question 47
Stakeholders feel misrepresented – what should you do?
❌ Conduct elicitation
❌ Communicate info
✅ Confirm elicitation results
❌ Manage collaboration
Question 48
Formality of documents in predictive frameworks?
❌ Only approvals
❌ Avoid documents
✅ Highly formal documentation required
❌ Iterative updates
Question 49
BACCM concept including market, regulations, culture?
❌ Stakeholder
❌ Need
❌ Solution
✅ Context
Question 50
Key attribute in selecting BA approach?
❌ Strict templates
❌ Limited participation
✅ Adaptability to varying project complexities
❌ Technical-only focus
🧾 Summary Table (Condensed)
| Area | Key Correct Themes |
|---|---|
| Requirements | Validation, traceability, feasibility |
| Modeling | Functional decomposition, process & data modeling |
| Prioritization | MoSCoW, value vs cost |
| BACCM | Need, Solution, Context, Value, Stakeholder |
| Elicitation | Prepare → Conduct → Confirm |
| Governance & Change | Impact analysis, documentation |
| BABOK | Knowledge areas & competencies |