BCS BA Found. · BCS · Validating and Managing Requirements · Bank updated 2026-11-04
BCS BA Found. practice questions: Validating and Managing Requirements
5 free questions from 9 on this area · answer and explanation for each · no sign-up
These 5 questions come from the Validating and Managing Requirements section of our BCS BA Found. bank (9 questions on this area, which carries 5% 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 9 Validating and Managing Requirements questions and the full BCS BA Found. bank: $15 one-time.
1/5 · Validating and Managing Requirements · easy
In business analysis practice, what is the primary purpose of requirements validation?
ATo rank documented requirements in order of importance, and agree the scope of the next release with the stakeholders before further work proceeds
BTo create links between each documented requirement and the corresponding test cases and design elements across levels before further work proceeds
CTo record each change to the documented requirements in a single master change log kept for audit purposes, before further work proceeds with stakeholders
DTo confirm that documented requirements are correct, complete and consistent, and genuinely reflect the needs of stakeholders before further work proceeds
2/5 · Validating and Managing Requirements
A business analyst needs to trace a single business requirement forward through the more detailed user and system requirements that derive from it, down to the design elements and test cases used to confirm it has been delivered. Which type of traceability does this describe?
AHorizontal traceability
BBackward compatibility checking
CVertical traceability
DBaseline reconciliation
3/5 · Validating and Managing Requirements
A stakeholder submits a request to change a requirement that has already been baselined. Which sequence of activities correctly reflects a sound change control process?
ARefuse the change request outright, since baselining a requirement means it can never be changed again, and explain to the stakeholder that the baseline stays fixed whatever the impact
BAdd the change directly into the requirements catalogue and re-run the full validation exercise on all requirements from the beginning, before updating the baseline and related traceability records
CUpdate the baseline immediately to keep documentation current, then log the change request afterwards for audit purposes and assess its impact on cost and schedule once the update is done
DLog the change request, assess its impact on cost, schedule and other requirements, obtain approval from the appropriate authority, and then update the baseline and related traceability records
4/5 · Validating and Managing Requirements
During prioritisation using the MoSCoW technique, one requirement is categorised as 'Won't have this time'. The project sponsor asks the business analyst to delete this requirement from the requirements documentation entirely, since it will not be built. What should the analyst explain to the sponsor?
AThe requirement should be retained in the documentation, since 'Won't have this time' means it is out of scope for the current delivery but may still be considered for a future iteration or release.
BThe requirement should be moved into the non-functional requirements section, since 'Won't have' items are always non-functional in nature.
CThe requirement must be reclassified as 'Could have' rather than deleted, since MoSCoW does not permit a 'Won't have' category.
DThe requirement should be deleted immediately, since anything categorised as 'Won't have' by definition will never be revisited in any future release.
Answer: A. MoSCoW prioritises requirements into Must have, Should have, Could have and Won't have (this time). The final category is a frequent source of confusion because it is often misread as a permanent rejection; correct practice is to retain such requirements in the documentation, since they may be reconsidered for a future release.
Source: the BCS Business Analysis Foundation syllabus - Validating and Managing Requirements
5/5 · Validating and Managing Requirements · hard
A business analyst submits a requirements specification for a formal inspection. Before the session, the moderator finds that the document does not meet the entry criteria defined for the inspection process. What happens next under the inspection technique?
Athe inspection proceeds, and the unmet entry criteria are logged as defects
Bthe inspection is replaced by a walkthrough that waives the entry criteria
Cthe inspection does not take place until the document has been reworked
Dthe inspection proceeds, with the exit criteria relaxed to compensate
Answer: C. An inspection follows a defined process based on rules and checklists, including entry and exit criteria. If a document does not meet the entry criteria, the inspection does not take place, and the document is released only when it passes the exit criteria. This formality distinguishes it from walkthroughs and peer reviews.
Source: Paul, Cadle, Turner (eds), Business Analysis Techniques, 2nd ed., BCS, Technique 81: Requirements validation, p. n/a
Source: the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) - Investigating the Business Situation
Other BCS BA Found. areas
The same kind of free sample for every other section of the BCS BA Found. bank:
Practise BCS BA Found. with instant feedback
6 free questions in study mode · no card · full BCS BA Found. bank with area filters and the error log: $15 one-time · no dumps, no ads.
Start BCS BA Foundation free →
ExamDeck is an independent study tool, not affiliated with, endorsed by, or sponsored by BCS. BCS BA Found. and related marks are trademarks of their respective owners, used for identification only. Exam facts checked against official BCS materials (as of August 2026); always confirm current details with the vendor before booking.