CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Domain knowledge helps BAs understand the business context deeply — enabling them to ask incisive questions, recognize inconsistencies in requirements, identify unstated needs, and communicate credibly with domain experts.

**Why not A:** Making technology architecture decisions falls outside the business analyst's scope and belongs to solution architects or technical leads. Domain knowledge helps BAs understand the business context and stakeholder needs, not dictate technical implementation choices.

**Why not C:** Managing the project schedule is a project manager responsibility, not a primary reason BAs need domain knowledge. While understanding timelines is helpful, domain knowledge specifically enables BAs to elicit accurate requirements, ask informed questions, and communicate effectively with subject matter experts.

**Why not D:** Writing code is a developer activity, not a business analysis function. Domain knowledge empowers BAs to bridge the gap between business needs and technical solutions through requirements, not through hands-on coding.