A business analyst is evaluating tools for traceability and monitoring. The project has a small budget and a short timeline. The team is already using a shared spreadsheet for requirements. What is the most appropriate tool decision?

Use a free online document sharing service without traceability features.

Use the existing spreadsheet and enhance it with traceability columns and status tracking.

Create a new database from scratch to manage traceability.

Purchase an enterprise requirements management tool with full traceability features.

During user acceptance testing, a stakeholder reports that a delivered feature does not match the approved requirement. The business analyst uses the traceability matrix and finds that the feature is linked to a different requirement than the one the stakeholder expected. What is the most likely cause of this discrepancy?

The test case was executed by a different tester than planned.

The project manager changed the scope without approval.

The stakeholder did not attend the requirements review meeting.

A traceability link is incorrect or missing between the requirement and the design or test artifact.

What is the purpose of a change control process for requirements?

To automatically implement changes without stakeholder approval

To prevent any changes to requirements once they are approved

To manage and document changes to requirements in a controlled manner, assessing impact and maintaining traceability

To create a backup of the requirements document

Which of the following is a key benefit of maintaining traceability links throughout a project?

It eliminates the need for change control processes

It automatically generates test cases from requirements

It enables impact analysis when a requirement changes, helping to identify affected artifacts

It guarantees that the project will be completed on time

Which of the following is an example of monitoring a requirement's status?

Updating the requirement's status from 'In Progress' to 'Implemented' after the development team completes the feature

Creating a new requirement without assessing its impact

Assigning a priority to a requirement for the first time

Deleting a requirement from the project documentation without approval

PMIProfessional in Business Analysis

Domain 4Objective 5

Task 5 PMI-PBA Practice Questions (Page 5)

Part of the Traceability and Monitoring domain, which accounts for 15% of the PMI-PBA exam. PMI does not publish an official question count, but from its 240-minute exam (~95–160 total, ~14–24 in this domain), expect 3–5 from this objective — we provide 31 practice questions to prepare you well beyond it. (estimate)

31questions here

7free pages

8concepts

15%of the exam

Questions 21–25

21application · medium
A business analyst is evaluating tools for traceability and monitoring. The project has a small budget and a short timeline. The team is already using a shared spreadsheet for requirements. What is the most appropriate tool decision?
Select an answer first
22application · medium
During user acceptance testing, a stakeholder reports that a delivered feature does not match the approved requirement. The business analyst uses the traceability matrix and finds that the feature is linked to a different requirement than the one the stakeholder expected. What is the most likely cause of this discrepancy?
Select an answer first
23foundation · easy
What is the purpose of a change control process for requirements?
Select an answer first
24foundation · easy
Which of the following is a key benefit of maintaining traceability links throughout a project?
Select an answer first
25foundation · easy
Which of the following is an example of monitoring a requirement's status?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to PMI-PBA

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by PMI. “PMI-PBA” is a trademark of its owner, used for identification only.