Fundamentals and Core Concepts
What this domain tests
Fundamentals questions check whether you understand why business analysis exists and how its building blocks fit together. Expect definitions of the business analyst role, the difference between a need and a solution, stakeholder types, and the vocabulary of requirements (business, stakeholder, solution, and transition requirements). Know the distinction between a problem, an opportunity, and a symptom, and be able to classify inputs as either context or content.
Concepts to master
- Needs versus solutions: a need describes a gap in outcomes; a solution is one way to close it. Traps present a named product as the need.
- Requirement levels: business requirements justify the work; stakeholder requirements describe what people need; solution requirements describe behavior and qualities; transition requirements cover temporary change needs.
- Stakeholder analysis: identify, classify by influence and interest, and plan engagement. Watch for questions that assume all stakeholders share goals.
- The BA's value: reducing rework by eliciting the right problem before designing a fix.
Common traps
Questions often reward the earliest correct action rather than the most impressive one. If a stakeholder demands a specific tool, the disciplined answer investigates the underlying need first. Another trap confuses verification (built correctly) with validation (solves the need).
Rule of thumb
Ask "what outcome is missing?" before "what should we build?" If an answer option names a deliverable before establishing the problem, it is usually wrong.
Worked example: A manager asks for a mobile approval app. The best first step is to clarify which approval delays hurt the business and why, then evaluate options including process changes, not to begin app design.