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

RCA helps BAs ensure they're solving the real problem, not symptoms. Techniques like 5-Whys and fishbone diagrams trace problems to their root causes, preventing solutions that fix surface manifestations while the underlying issue remains.

**Why not A:** Identifying the original author of each requirement is a traceability or documentation management task, not root cause analysis. RCA focuses on uncovering the fundamental reasons behind a business problem, not on attributing authorship of requirements.

**Why not C:** Analyzing the organizational root structure for resource planning describes organizational design or resource management activities. Root cause analysis is a problem-solving technique that investigates why a business problem exists, not how an organization is structured for staffing purposes.

**Why not D:** Finding which developer introduced a bug is a code-level debugging activity, not business analysis root cause analysis. While developer-focused RCA exists in software engineering, the BA context of RCA focuses on understanding the underlying business problems that drive project requirements.