Explanation
According to the Wikipedia article on requirements traceability1, tracing a requirement means to follow the life of a requirement in both a forwards and backwards direction, from its origins, through its development and specification, to its subsequent deployment and use, and through periods of ongoing refinement and iteration.
Tracing a requirement helps to ensure that the requirement is linked to a business objective, that it is consistent and aligned with other requirements and deliverables, and that it is verified and validated by the stakeholders.
Tracing a requirement can also help to identify the impact of changes, the source of defects, and the gaps in the requirements.
Option A is incorrect because it does not mention the business requirements, which are the high-level needs and objectives of the organization or the customer. Option C is incorrect because it does not mention the stakeholder and solution requirements, which are the detailed and specific requirements that define the scope and functionality of the solution. Option D is incorrect because it describes tracking a requirement, not tracing a requirement. Tracking a requirement means to monitor the progress and status of a requirement throughout the project lifecycle, not to link it to other related artifacts.