PMI-PBA® · PMI · Traceability and Monitoring · Bank updated 2026-07-02
PMI-PBA® practice questions: Traceability and Monitoring
5 free questions from 45 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Traceability and Monitoring section of our PMI-PBA® bank (45 questions on this area, which carries 15% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
1/5 · Traceability and Monitoring · easy
Why does a business analyst trace requirements back to the business objectives documented in the business case?
ATo identify which stakeholders hold veto power over requirement approval decisions.
BTo confirm that each requirement supports at least one business objective, helping ensure the solution will deliver intended value and reducing the risk of unnecessary scope.
CTo determine which requirements should be tested first, regardless of the value they deliver.
DTo calculate the return on investment figures used in the sponsor's annual performance review.
Show answer & explanation
B is correct. Tracing requirements to business objectives is a core traceability activity that confirms alignment between scope and strategic intent. If a requirement cannot be traced to an objective, it is a signal for the business analyst to investigate whether the requirement is necessary or represents unneeded scope.
↗ PMI-PBA Examination Content Outline — Traceability and Monitoring
2/5 · Traceability and Monitoring
A business analyst wants to confirm both that every approved business requirement has been implemented in at least one design or deliverable, and that every deliverable produced maps back to an approved requirement (guarding against unnecessary added functionality). What is this practice called?
ABenefits realization tracking, which measures whether delivered value materializes after the solution is deployed.
BBidirectional traceability, since it verifies traceability both forward from requirements to deliverables and backward from deliverables to requirements.
CConfiguration management, which controls versions of project artifacts and baselines.
DRoot cause analysis, a technique used during needs assessment to identify the underlying cause of a business problem.
Show answer & explanation
B is correct. Bidirectional traceability is the practice of confirming coverage in both directions — forward, from requirements to the deliverables that satisfy them, and backward, from deliverables to the approved requirements that justify them — helping detect both missing coverage and unauthorized (gold-plated) scope.
↗ PMI-PBA Examination Content Outline — Traceability and Monitoring
3/5 · Traceability and Monitoring · easy
In PMI business analysis practice, what does it mean when a set of requirements has been "baselined"?
AThe requirements have been formally reviewed and approved, and are now placed under change control
BThe requirements have been implemented and tested in the delivered solution
CThe requirements have been elicited but not yet validated by stakeholders
DThe requirements have been archived because the project has closed
Show answer & explanation
4/5 · Traceability and Monitoring
The business analyst must report requirements status to both the project steering committee and the technical delivery team. What is the most effective approach for communicating status to these two audiences?
ASend the identical detailed technical traceability matrix to both audiences to keep information consistent
BOnly report to the steering committee, since the technical team is already close to the details
CTailor the format, level of detail, and terminology of the requirements status report to each audience, while keeping the underlying source data, such as the traceability matrix, consistent
DWithhold status updates until all requirements are fully baselined to avoid confusion
Show answer & explanation
5/5 · Traceability and Monitoring
While preparing for a compliance audit, a business analyst finds a requirement that is fully traced forward to design specifications and test cases, but the RTM shows no link connecting it back to any stakeholder need, business objective, or regulation. What risk does this most specifically indicate?
AThe requirement may represent unjustified scope, since its business justification cannot be confirmed from the traceability record.
BThe requirement's acceptance criteria are ambiguous and need rewriting.
CThe requirement is a duplicate of another requirement in the backlog.
DThe requirement was never tested and should be re-verified before release.
Show answer & explanation
A is correct. A requirement with forward links but no backward link to a business objective, need, or regulation is an orphan requirement. This is a risk indicator because the team cannot confirm why the requirement exists, which may point to unauthorized scope or a broken traceability record that needs correction.
↗ PMI-PBA Examination Content Outline — Traceability and Monitoring
Other PMI-PBA® areas
The same kind of free sample for every other section of the PMI-PBA® bank:
Study Traceability and Monitoring with instant feedback
6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.
Create your free account →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by PMI. PMI-PBA® and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official PMI materials (as of August 2026); always confirm current details with the vendor before booking.