PMI PBA Certification Traceability and Monitoring 2 — Questions and Answers
Question 1: What does 'requirements status' tracking help a business analyst monitor?
- The current state of each requirement (e.g., proposed, approved, implemented, verified) (Correct answer)
- The number of stakeholders who have reviewed each requirement
- The budget allocated to implement each requirement
- The sprint in which each requirement will be developed
Correct answer: The current state of each requirement (e.g., proposed, approved, implemented, verified)
Tracking requirements status provides real-time visibility into where each requirement is in its lifecycle, from proposal through verification.
Question 2: Which activity involves reviewing requirements regularly to ensure they remain valid, current, and aligned with business goals?
- Requirements monitoring (Correct answer)
- Requirements elicitation
- Requirements packaging
- Requirements decomposition
Correct answer: Requirements monitoring
Requirements monitoring involves ongoing review of requirements to ensure they remain valid, aligned with business goals, and are not affected by project changes.
Question 3: A scope change is approved that impacts three existing requirements. What should the BA update FIRST?
- The requirements traceability matrix to reflect impacts across linked artifacts (Correct answer)
- The project budget to account for the additional work
- The stakeholder register to add any new stakeholders
- The project schedule to extend the timeline
Correct answer: The requirements traceability matrix to reflect impacts across linked artifacts
Updating the RTM first ensures all linked artifacts (test cases, designs) are identified and flagged for review, preventing gaps from the scope change.
Question 4: What is the purpose of a requirements status report?
- To communicate the current state, progress, and issues related to requirements activities to stakeholders (Correct answer)
- To provide the development team with the final list of approved requirements
- To record stakeholder sign-off on completed deliverables
- To document the cost and effort spent on each requirement
Correct answer: To communicate the current state, progress, and issues related to requirements activities to stakeholders
A requirements status report communicates progress on requirements activities, highlights issues or risks, and keeps stakeholders informed about the requirements lifecycle.
Question 5: Which of the following BEST describes 'coverage analysis' in requirements traceability?
- Verifying that all requirements have corresponding design, development, and test coverage (Correct answer)
- Calculating the percentage of the project budget spent on requirements activities
- Identifying which stakeholders reviewed each requirement
- Ensuring all team members understand the requirements document
Correct answer: Verifying that all requirements have corresponding design, development, and test coverage
Coverage analysis verifies that every requirement is fully addressed through the project lifecycle — from design and development through testing — leaving no gaps.
Question 6: A BA is using a requirements management tool that flags 'orphaned requirements.' What does this mean?
- Requirements that exist in the system but are not linked to any project objective, test case, or deliverable (Correct answer)
- Requirements that were submitted by stakeholders who are no longer on the project
- Requirements that have been approved but not yet assigned to a developer
- Requirements that are duplicates of other approved requirements
Correct answer: Requirements that exist in the system but are not linked to any project objective, test case, or deliverable
Orphaned requirements are those that exist in the requirements system but lack linkages to project objectives, test cases, or deliverables, indicating potential gaps in coverage.
What does 'requirements status' tracking help a business analyst monitor?