PMI PBA Certification Traceability and Monitoring 1 — Questions and Answers
Question 1: What is the primary purpose of a requirements traceability matrix (RTM)?
- To link requirements to their sources, related artifacts, and implementation to ensure completeness and change control (Correct answer)
- To track the project schedule milestones and deliverables
- To document all stakeholder communication during the project
- To assign development tasks to specific team members
Correct answer: To link requirements to their sources, related artifacts, and implementation to ensure completeness and change control
An RTM links each requirement to its source, related test cases, and implementation artifacts, enabling impact analysis, completeness checks, and effective change control.
Question 2: Which of the following is an example of forward traceability?
- Tracing a business requirement to its corresponding test case (Correct answer)
- Tracing a defect back to the requirement that caused it
- Tracing a stakeholder request to its originating interview
- Tracing project scope changes to the change control log
Correct answer: Tracing a business requirement to its corresponding test case
Forward traceability follows a requirement downstream through the project lifecycle, such as linking a business requirement to its test case to verify coverage.
Question 3: What is 'backward traceability' in requirements management?
- Tracing a requirement or deliverable back to its originating business need or stakeholder request (Correct answer)
- Reviewing previously rejected requirements for potential reuse
- Revisiting earlier project phases to correct documentation errors
- Tracing defects found in testing back to the development team
Correct answer: Tracing a requirement or deliverable back to its originating business need or stakeholder request
Backward traceability links a requirement, design element, or test case back to the originating business need or stakeholder request, validating its justification.
Question 4: Why is requirements traceability critical during change management?
- It enables impact analysis by showing which artifacts are affected when a requirement changes (Correct answer)
- It automatically approves or rejects change requests based on priority
- It prevents stakeholders from submitting new change requests
- It records the cost of each change for budget management purposes
Correct answer: It enables impact analysis by showing which artifacts are affected when a requirement changes
Traceability enables impact analysis by revealing all linked artifacts (test cases, designs, code) that would be affected by a proposed requirement change, supporting informed decision-making.
Question 5: Which tool or technique is MOST commonly used to visualize requirements dependencies and traceability?
- Requirements traceability matrix (Correct answer)
- Gantt chart
- Risk breakdown structure
- Stakeholder map
Correct answer: Requirements traceability matrix
The requirements traceability matrix is the standard tool for documenting and visualizing how requirements link to other project artifacts, showing dependencies and coverage.
Question 6: A business analyst is performing a traceability audit and finds several requirements with no associated test cases. What is the risk?
- Those requirements may not be tested, leading to undetected gaps in the delivered solution (Correct answer)
- The project schedule will automatically be extended to accommodate testing
- Stakeholders will reject the solution during user acceptance testing
- The development team will need to rewrite the requirements
Correct answer: Those requirements may not be tested, leading to undetected gaps in the delivered solution
Requirements without associated test cases may not be verified before delivery, risking that undetected gaps or defects are included in the final solution.
What is the primary purpose of a requirements traceability matrix (RTM)?