Certified Business Analysis Professional Requirements Life Cycle Management 1 — Questions and Answers
Question 1: What is the primary purpose of requirements traceability in business analysis?
- To document the history of stakeholder meetings
- To establish relationships between requirements and their sources, components, and deliverables (Correct answer)
- To assign ownership of each requirement to a specific team member
- To create a timeline for requirement delivery
Correct answer: To establish relationships between requirements and their sources, components, and deliverables
Requirements traceability establishes and maintains relationships between requirements and their origins, components, designs, and solution deliverables to ensure alignment throughout the project.
Question 2: Which of the following best describes the MoSCoW technique in requirements prioritization?
- A method to categorize requirements as Must have, Should have, Could have, and Won't have (Correct answer)
- A voting system where stakeholders rank requirements numerically
- A cost-benefit analysis framework for requirements
- A technique for grouping requirements by business domain
Correct answer: A method to categorize requirements as Must have, Should have, Could have, and Won't have
MoSCoW stands for Must have, Should have, Could have, and Won't have, and is used to prioritize requirements based on stakeholder consensus about their relative importance.
Question 3: What is the primary artifact used to document relationships between requirements, test cases, and business objectives?
- Business Requirements Document
- Requirements Traceability Matrix (Correct answer)
- Stakeholder Register
- Use Case Diagram
Correct answer: Requirements Traceability Matrix
A Requirements Traceability Matrix (RTM) maps requirements to their sources, test cases, and business objectives, ensuring complete coverage and accountability.
Question 4: When a change request is submitted that affects existing requirements, what should a business analyst do first?
- Immediately update the requirements documentation
- Reject the change to protect the project baseline
- Assess the impact of the proposed change on related requirements and solution components (Correct answer)
- Escalate the change to the project sponsor for approval
Correct answer: Assess the impact of the proposed change on related requirements and solution components
The first step in assessing a requirements change is to analyze its impact on all related requirements, designs, and solution components before any decision is made.
Question 5: What is the purpose of establishing a requirements baseline?
- To prevent any future changes to requirements
- To provide a fixed reference point against which changes can be assessed and controlled (Correct answer)
- To finalize stakeholder sign-off and close the elicitation phase
- To document all rejected requirements for audit purposes
Correct answer: To provide a fixed reference point against which changes can be assessed and controlled
A requirements baseline creates a stable, approved reference point that allows teams to measure scope changes and manage deviations systematically.
Question 6: Which task within Requirements Life Cycle Management ensures requirements remain accurate and up to date throughout the solution lifecycle?
- Trace Requirements
- Prioritize Requirements
- Maintain Requirements (Correct answer)
- Approve Requirements
Correct answer: Maintain Requirements
Maintain Requirements is the task focused on keeping requirements accurate, consistent, and current as the project and business environment evolve.
Question 7: Why is requirements prioritization important in the Requirements Life Cycle Management knowledge area?
- It eliminates low-value requirements from the project scope permanently
- It ensures stakeholders understand the technical architecture of the solution
- It helps allocate limited resources to the most valuable requirements first (Correct answer)
- It documents the order in which requirements were elicited
Correct answer: It helps allocate limited resources to the most valuable requirements first
Prioritization ensures that resources, time, and effort are directed toward requirements that deliver the highest business value, especially when trade-offs must be made.
Certified Business Analysis Professional Requirements Life Cycle Management 1
What is the primary purpose of requirements traceability in business analysis?