A business analyst (BA) has been given a defect during user acceptance testing. After analyzing the defect, the BA determines it is a change in the requirement. What does the BA need to do to assess…

Closing the defect as 'working as designed' is incorrect because the BA has already determined it represents a genuine requirement change, not a misunderstanding of existing behavior.

Evaluating risk analysis and management information is a step that may follow impact analysis but does not itself assess what the requirement change affects across the solution.

Root cause analysis is used to identify why a defect occurred, not to assess the scope and impact of an identified requirement change.

Impact analysis using traceability allows the BA to trace the changed requirement to all associated design elements, test cases, and other requirements to determine the full scope of the change. Traceability matrices link requirements to their dependencies, so the BA can systematically assess downstream and upstream effects. This structured approach ensures the change is evaluated properly before being submitted through change control.