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

BAs contribute to risk management by identifying requirements risks (incomplete requirements, stakeholder conflicts, changing business conditions) and providing domain knowledge about business process risks. They collaborate with PMs on holistic risk management.

**Why not A:** Limiting BA risk contributions to technical/system risks ignores the broader domain knowledge BAs bring to the table. In practice, many of the most damaging project risks are requirements-related — unclear scope, conflicting stakeholder needs, and unstated assumptions — areas where BAs have the deepest expertise.

**Why not B:** BAs do not own or manage all project risks; that accountability sits with the project manager. Saying BAs "manage all project risks" conflates BA and PM responsibilities and overstates the BA role in a way that would undermine proper risk ownership on a project.

**Why not D:** Asserting that BAs play no part in risk management contradicts both PMI and IIBA guidance. BAs actively surface requirements-related risks such as ambiguous requirements, stakeholder conflict, and scope creep, and they provide domain expertise that informs the broader risk register.