Which activity is typically part of requirements validation?

Writing code to implement the requirements

Reviewing requirements with stakeholders to confirm they are correct and complete

Deploying the solution to production

A business analyst is working on a project to improve the customer support process. The analyst has elicited a large number of requirements from various stakeholders, but some requirements are contradictory and others are unclear. The analyst needs to structure and refine the requirements to make them easier to analyze and prioritize. Which technique should the analyst use?

Create a requirements traceability matrix

Prioritize the requirements using a simple ranking technique

Conduct a stakeholder survey to collect more requirements

Use a requirements model, such as a use case diagram or process flow, to visualize and clarify the requirements

Which output of Task 7 captures the decisions made during requirements analysis and approval?

The final solution architecture

The project's communication plan

The stakeholder engagement assessment matrix

Updated documentation, such as the requirements traceability matrix

A business analyst has completed the analysis and validation of requirements for a new project management tool. The stakeholders have approved the requirements, and the analyst has documented the decisions. What should the analyst do next to ensure the outputs of Task 7 are complete?

Send the approved requirements to the development team and archive the analysis documents

Begin the solution design without further documentation

Update the requirements documentation to reflect the approved changes and decisions

Conduct another validation session to confirm the requirements are still valid

What does it mean for a requirement to be 'complete' in the context of requirements analysis?

It is written in a formal technical language

It contains all necessary information to be understood and implemented without needing further clarification

It is technically feasible to implement

It is approved by all stakeholders

PMIProfessional in Business Analysis

Domain 3Objective 7

Task 7 PMI-PBA Practice Questions (Page 5)

Part of the Analysis domain, which accounts for 35% of the PMI-PBA exam. PMI does not publish an official question count, but from its 240-minute exam (~95–160 total, ~33–56 in this domain), expect 4–7 from this objective — we provide 38 practice questions to prepare you well beyond it. (estimate)

38questions here

8free pages

10concepts

35%of the exam

Questions 21–25

21foundation · easy
Which activity is typically part of requirements validation?
Select an answer first
22application · medium
A business analyst is working on a project to improve the customer support process. The analyst has elicited a large number of requirements from various stakeholders, but some requirements are contradictory and others are unclear. The analyst needs to structure and refine the requirements to make them easier to analyze and prioritize. Which technique should the analyst use?
Select an answer first
23foundation · easy
Which output of Task 7 captures the decisions made during requirements analysis and approval?
Select an answer first
24application · medium
A business analyst has completed the analysis and validation of requirements for a new project management tool. The stakeholders have approved the requirements, and the analyst has documented the decisions. What should the analyst do next to ensure the outputs of Task 7 are complete?
Select an answer first
25foundation · easy
What does it mean for a requirement to be 'complete' in the context of requirements analysis?
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.