Certified Business Analysis Professional Requirements Life Cycle Management

Question 1

What is the primary purpose of requirements traceability in business analysis?

Accepted Answer

To establish relationships between requirements and their sources, components, and deliverables

Answer

To document the history of stakeholder meetings

Answer

To assign ownership of each requirement to a specific team member

Answer

To create a timeline for requirement delivery

Question 2

Which of the following best describes the MoSCoW technique in requirements prioritization?

Accepted Answer

A method to categorize requirements as Must have, Should have, Could have, and Won't have

Answer

A voting system where stakeholders rank requirements numerically

Answer

A cost-benefit analysis framework for requirements

Answer

A technique for grouping requirements by business domain

Question 3

What is the primary artifact used to document relationships between requirements, test cases, and business objectives?

Accepted Answer

Requirements Traceability Matrix

Answer

Business Requirements Document

Answer

Stakeholder Register

Answer

Use Case Diagram

Question 4

When a change request is submitted that affects existing requirements, what should a business analyst do first?

Accepted Answer

Assess the impact of the proposed change on related requirements and solution components

Answer

Immediately update the requirements documentation

Answer

Reject the change to protect the project baseline

Answer

Escalate the change to the project sponsor for approval

Question 5

What is the purpose of establishing a requirements baseline?

Accepted Answer

To provide a fixed reference point against which changes can be assessed and controlled

Answer

To prevent any future changes to requirements

Answer

To finalize stakeholder sign-off and close the elicitation phase

Answer

To document all rejected requirements for audit purposes

Question 6

Which task within Requirements Life Cycle Management ensures requirements remain accurate and up to date throughout the solution lifecycle?

Accepted Answer

Maintain Requirements

Answer

Trace Requirements

Answer

Prioritize Requirements

Answer

Approve Requirements

Question 7

Why is requirements prioritization important in the Requirements Life Cycle Management knowledge area?

Accepted Answer

It helps allocate limited resources to the most valuable requirements first

Answer

It eliminates low-value requirements from the project scope permanently

Answer

It ensures stakeholders understand the technical architecture of the solution

Answer

It documents the order in which requirements were elicited