CPRE FL · IREB · Management Practices for Requirements · Bank updated 2026-10-15
CPRE FL practice questions: Management Practices for Requirements
5 free questions from 20 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Management Practices for Requirements section of our CPRE FL bank (20 questions on this area, which carries 11% of the real exam). Every question is original, with the correct answer explained and linked to the source it is drawn from.
Free: 6 questions in study mode, no card. All 20 Management Practices for Requirements questions and the full CPRE FL bank: $15 one-time.
1/5 · Management Practices for Requirements
Using the MoSCoW prioritization technique, a project team labels a requirement as 'Could have'. What does this classification mean?
AIt is explicitly out of scope for the current release and will not be implemented under any circumstances
BIt is an important requirement that should be included if at all possible, though the project could still succeed without it in the worst case
CIt is a mandatory requirement without which the resulting system would not be acceptable
DIt is a low-priority, desirable feature that should be included only if time and resources permit, but the project remains viable without it
2/5 · Management Practices for Requirements · easy
Why are individual requirements or requirements documents typically assigned version identifiers over the course of a project?
ATo record which downstream design or test artifacts were influenced by the requirement
BTo formally approve a requirement without requiring any further review by stakeholders
CTo enable tracking of how a requirement has changed over time and, if necessary, to revert to an earlier state
DTo assign a business priority level that determines implementation order
3/5 · Management Practices for Requirements
A requirements engineer maintains trace links from each requirement to the design elements and test cases that implement and verify it. Which traceability purpose is primarily supported by these links?
AForward traceability, supporting verification of implementation coverage and impact analysis toward downstream work products
BBackward traceability, documenting the rationale and stakeholder origin of each requirement
CVersion assignment, tracking successive states of each requirement
DPrioritization, determining the relative importance of requirements
4/5 · Management Practices for Requirements · hard
A customer requests a significant change to a requirement that has already been baselined. According to established requirements change management practice, what should happen before the requirement is actually modified in the specification?
AThe original requirement should be deleted immediately so that no conflicting versions exist in the repository
BThe change should be recorded only as a new, unrelated requirement, leaving the original baselined requirement completely untouched regardless of its actual scope
CThe developer should apply the change directly in the code as soon as it is technically feasible and update the requirement document later if time permits
DThe change request should undergo impact analysis and be formally evaluated and approved by an authorized decision body (e.g., a change control board) before the baseline is updated
5/5 · Management Practices for Requirements
Mid-project, a stakeholder submits a request to modify a requirement that has already been agreed upon and included in the current baseline. Following the change-management approach described in the syllabus, what should happen before a decision is made on whether to accept this change request?
AThe impact of the proposed change (e.g., effects on cost, schedule, risk and other related requirements) should first be analyzed and documented to inform the decision.
BThe entire elicitation phase should be restarted so that all stakeholder needs are recollected from scratch before considering the single change.
CThe change request should be rejected automatically, because requirements that are part of an agreed baseline can no longer be altered.
DThe requirement should be updated immediately in the specification so that no working time is lost while the request is pending.
Answer: A. Change management as described in the syllabus involves systematically capturing, analyzing the impact of, deciding on, and then implementing/communicating changes to requirements. Impact analysis precedes the decision so that cost, schedule, risk and knock-on effects on other requirements are understood before an agreed requirement is altered.
Source: the IREB CPRE Foundation Level Syllabus v3.3.0 — Management Practices for Requirements
Other CPRE FL areas
The same kind of free sample for every other section of the CPRE FL bank:
Practise CPRE FL with instant feedback
6 free questions in study mode · no card · full CPRE FL bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start CPRE FL free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by IREB. CPRE FL and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official IREB materials (as of August 2026); always confirm current details with the vendor before booking.