Traceability and Monitoring Flashcards
6 cards from real PMI PBA Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Traceability and Monitoring flashcards as text
What does 'requirements status' tracking help a business analyst monitor?
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.
Which activity involves reviewing requirements regularly to ensure they remain valid, current, and aligned with business goals?
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.
A scope change is approved that impacts three existing requirements. What should the BA update FIRST?
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.
What is the purpose of a requirements status report?
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.
Which of the following BEST describes 'coverage analysis' in requirements traceability?
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.
A BA is using a requirements management tool that flags 'orphaned requirements.' What does this mean?
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.
How this page was made: written with AI tools and published by Nathan Beja, founder of Practice Test Geeks, who is responsible for its content. Exam facts are checked against the official sources listed below. Not reviewed by a subject-matter expert. Editorial policy
Sources & references
Exam facts on this page (fees, format, dates, passing scores) are checked against these official sources; the date is our last check. Editorial policy
- pearsonvue.com — Test delivery · verified Oct 2026
- pmi.org — Exam format, renewal, time limit, score validity, passing score, retake policy, score release, test dates · verified Oct 2026