A business analyst has a high-level requirement: 'Improve customer satisfaction.' To analyze this, the BA needs to decompose it into manageable components. What is the best approach?

Break it down into sub-requirements such as 'reduce response time to under 2 hours' and 'provide self-service options'

Keep it as a single requirement and proceed to design

Ask stakeholders to prioritize the requirement without further analysis

Create a traceability matrix for the requirement

During requirements verification, a business analyst discovers that a requirement for a mobile app states: 'The app should be user-friendly.' The BA needs to verify this requirement. What is the most appropriate action?

Decompose the requirement into smaller parts and verify each part separately

Accept the requirement as-is because it reflects stakeholder intent

Ask the stakeholder to sign off on the requirement to confirm it is correct

Rewrite the requirement to include measurable criteria, such as 'The app must allow a new user to complete registration in under two minutes'

A business analyst is managing traceability for a project with several requirements that are affected by a change in a regulatory standard. The BA needs to identify which requirements, design components, and test cases are impacted. What is the most effective approach?

Ask the testing team to re-run all test cases to see which fail

Review the project scope statement to identify affected requirements

Conduct interviews with stakeholders to ask which requirements are affected

Review the traceability matrix to trace the impact from the regulatory change to affected requirements and downstream artifacts

What is the purpose of requirements traceability?

To assign requirements to releases

To break down requirements into smaller parts

To establish and maintain links between requirements, design, and testing

PMIProfessional in Business Analysis

Domain 3Objective 2

Task 2 PMI-PBA Practice Questions (Page 4)

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

21questions here

5free pages

9concepts

35%of the exam

Questions 16–20

16application · medium
A business analyst has a high-level requirement: 'Improve customer satisfaction.' To analyze this, the BA needs to decompose it into manageable components. What is the best approach?
Select an answer first
17application · medium
During requirements verification, a business analyst discovers that a requirement for a mobile app states: 'The app should be user-friendly.' The BA needs to verify this requirement. What is the most appropriate action?
Select an answer first
18application · medium
A business analyst is managing traceability for a project with several requirements that are affected by a change in a regulatory standard. The BA needs to identify which requirements, design components, and test cases are impacted. What is the most effective approach?
Select an answer first
19foundation · easy
A business analyst needs to gather detailed requirements from a group of stakeholders who have conflicting opinions about a new feature. Which elicitation technique is most appropriate for this situation?
Select an answer first
20foundation · easy
What is the purpose of requirements traceability?
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.