A BA is working on a project where a change request is approved. The change affects a requirement that is linked to several test cases. What should the BA do to maintain traceability?

Update the requirement and its links to the affected test cases

Inform the test team that the test cases are no longer valid

Remove the links to the test cases and create new ones

Leave the traceability matrix unchanged until the change is implemented

A BA is preparing a report for a stakeholder who is interested in the progress of requirements implementation. The stakeholder wants to know how many requirements have been implemented, validated, and deployed. What type of report should the BA provide?

A requirements status summary showing counts by status category

A technical report on the number of test cases executed

A detailed list of all requirements with their owners and approval dates

A financial report showing the cost of implementing each requirement

What is the purpose of reporting traceability and monitoring status to stakeholders?

To replace the need for stakeholder meetings

To assign tasks to team members

To provide stakeholders with information for informed decision-making

To document the project's financial performance

A BA is working on a project where a stakeholder requests a change to a requirement. The BA performs an impact analysis and determines that the change will affect three other requirements and two test cases. What should the BA do next?

Implement the change immediately to avoid delays

Submit the change request with the impact analysis to the change control board

Reject the change because it affects too many other requirements

Ask the stakeholder to withdraw the request

What is the main benefit of establishing traceability links between requirements and design artifacts?

It replaces the need for stakeholder communication

It eliminates the need for change control

It enables impact analysis when a requirement changes

It guarantees the project will be delivered on time

PMIProfessional in Business Analysis

Domain 4Objective 4

Task 4 PMI-PBA Practice Questions (Page 1)

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 29 practice questions to prepare you well beyond it. (estimate)

29questions here

6free pages

5concepts

15%of the exam

Questions 1–5

1application · medium
A BA is working on a project where a change request is approved. The change affects a requirement that is linked to several test cases. What should the BA do to maintain traceability?
Select an answer first
2application · easy
A BA is preparing a report for a stakeholder who is interested in the progress of requirements implementation. The stakeholder wants to know how many requirements have been implemented, validated, and deployed. What type of report should the BA provide?
Select an answer first
3foundation · easy
What is the purpose of reporting traceability and monitoring status to stakeholders?
Select an answer first
4application · medium
A BA is working on a project where a stakeholder requests a change to a requirement. The BA performs an impact analysis and determines that the change will affect three other requirements and two test cases. What should the BA do next?
Select an answer first
5foundation · easy
What is the main benefit of establishing traceability links between requirements and design artifacts?
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.