According to the PMI Guide to Business Analysis, a requirements traceability matrix is a tool that helps to ensure that the requirements are aligned with the business needs and objectives, and that they are verified and validated throughout the project life cycle. A requirements traceability matrix can also help to identify gaps, redundancies, and inconsistencies in the requirements. If the requirements matrix did not adequately track back to client requirements, it could result in a product that does not meet the client's expectations or specifications, even if it passes the test plan. Therefore, it is important to establish and maintain a clear and accurate traceability of requirements from their source to their implementation and verification. References:
PMI Guide to Business Analysis, page 179-180.

Team peer review is a technique that is used to identify ambiguous or unverifiable requirements. Team peer review is a technique that involves having a group of peers or experts examine and evaluate the requirements for quality, completeness, correctness, clarity, consistency, and testability. Team peer review can help to identify any ambiguous or unverifiable requirements that may cause confusion, misunderstanding, or errors in the project. Team peer review can also provide feedback and suggestions for improvement or resolution of any issues or defects in the requirements. Fishbone analysis is not a technique that is used to identify ambiguous or unverifiable requirements. Fishbone analysis is a technique that is used to identify the root causes of a problem or an effect by analyzing its contributing factors and their relationships. Fishbone analysis can help to understand why a problem exists or why an effect occurs, but it does not directly examine or evaluate the quality of the requirements. Resource checklist is not a technique that is used to identify ambiguous or unverifiable requirements. Resource checklist is a tool that is used to identify and document the resources needed to perform business analysis activities, such as people, tools, facilities, equipment, etc.
Resource checklist can help to plan and manage the resources required for business analysis work, but it does not assess or verify the quality of the requirements. Traceability matrix is not a technique that is used to identify ambiguous or unverifiable requirements. Traceability matrix is a tool that is used to track and document the relationships and dependencies among requirements and other project elements, such as design, test cases, risks, issues, etc. Traceability matrix can help to monitor and control changes to requirements and ensure alignment with project objectives and stakeholder needs, but it does not measure or validate the quality of the requirements. References: Business Analysis for Practitioners: A Practice Guide 1, page 162-163; PMI Professional in Business Analysis (PMI-PBA)Examination Content Outline 2, page 19-20.

Explanation
Workshop sessions are a technique to elicit, analyze, and prioritize requirements by bringing together a group of stakeholders, such as subject matter experts, to collaborate and reach a consensus. Workshop sessions can be used to identify and prioritize the requirements for a newly approved project. The other techniques are not suitable for this purpose. Delphi technique is a technique to obtain expert opinions anonymously and iteratively until a consensus is reached. Brainstorming is a technique to generate a large number of ideas or solutions in a short time. Idea and mind mapping is a technique to visually organize ideas or information using diagrams or graphs. References: PMI-PBA
Examination Content Outline, page 10; PMI-PBA
Reference
List, page 1, BABOK
Guide v3, page 50.

Explanation
A matrix is a tool that can be used to record, organize, and track the requirements throughout the lifecycle of the project. A matrix can help the business analyst to identify the sources, dependencies, relationships, and attributes of the requirements, as well as to monitor their status, changes, and traceability. A matrix can also facilitate the communication, verification, and validation of the requirements with the stakeholders, and ensure their alignment with the business needs and objectives. A matrix can be updated and reviewed regularly to reflect the current state of the requirements and the solution, and to obtain the approval and acceptance from the stakeholders. A common example of a matrix is the Requirements Traceability Matrix (RTM), which is a tool that links the requirements to the project scope, objectives, deliverables, and test cases12. References:
PMI Professional in Business Analysis (PMI-PBA)
Examination Content Outline3, page 18; Business
Analysis for Practitioners: A Practice Guide4, page 92.

Explanation
A use case is a technique that describes how an actor interacts with a system to achieve a goal or perform a task. A use case consists of a main scenario and possible alternative scenarios that capture the normal, exceptional, and error flows of events. A use case can also include the acceptance criteria that specify the conditions that must be met for the use case to be successfully completed and accepted by the stakeholders.
The test team can review the use cases to help identify the acceptance criteria for the solution, as they provide a comprehensive and realistic view of the expected behavior and outcomes of the system. The test team can also use the use cases to design and execute test cases that verify and validate the functional requirements and acceptance criteria of the solution. : PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 99.