HomeBCS BA Found.Practice questionsValidating and Managing Requirements
BCS BA Found. · BCS · Validating and Managing Requirements · Bank updated 2026-07-03

BCS BA Found. practice questions: Validating and Managing Requirements

5 free questions from 6 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 (6 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.

Start 6 free in study mode → All BCS BA Found. sample questions
1/5 · Validating and Managing Requirements · easy
In business analysis practice, what is the primary purpose of requirements validation?
ATo rank requirements in order of importance so that scope can be agreed for the next release
BTo create links between each requirement and the corresponding test cases and design elements
CTo record every requirement change in a single master change log for audit purposes
DTo confirm that documented requirements are correct, complete and consistent, and genuinely reflect the needs of stakeholders before further work proceeds
Show answer & explanation
D is correct. Requirements validation is the quality-checking activity that confirms requirements are correct, unambiguous, complete, consistent and testable, and that they truly represent stakeholder needs. It is distinct from traceability (linking requirements across levels/artefacts) and from change control (managing amendments after baselining).
↗ the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) — Validating and Managing Requirements
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
Show answer & explanation
C is correct. The BCS approach distinguishes vertical traceability (tracking a requirement through the different levels of abstraction, from business need down to design and test) from horizontal traceability (tracking relationships between requirements and other artefacts, such as related requirements or documents, at the same level). Following a business requirement all the way down to test cases is vertical traceability.
↗ the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) — Validating and Managing Requirements
3/5 · Validating and Managing Requirements
A business analyst is embedded in a Scrum team that develops working software in short iterations. Which approach to requirements validation is most consistent with this iterative way of working?
ALeaving all validation of requirements to the independent test team once full system testing has been completed
BProducing one comprehensive requirements document and obtaining formal sign-off from the project board before any development work begins
CAssessing every requirement solely against the CPPOLDAT framework before it is added to the requirements catalogue
DReviewing and confirming requirements continuously with stakeholders, for example through sprint demonstrations of working software or prototypes at the end of each iteration
Show answer & explanation
D is correct. Formal validation typically involves structured reviews and sign-off of a complete requirements baseline before proceeding, suited to plan-driven projects. Agile/iterative validation instead confirms requirements incrementally, often through demonstrations of working software or prototypes and ongoing stakeholder feedback within each iteration.
↗ the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) — Validating and Managing Requirements
4/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 request outright, since baselining a requirement means it can never be changed again
BAdd the change directly into the requirements catalogue and re-run the full validation exercise on all requirements from the beginning
CUpdate the baseline immediately to keep documentation current, then log the change afterwards for audit purposes
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
Show answer & explanation
D is correct. Change control is designed to manage amendments to baselined requirements in a governed way: requests are logged, their impact is assessed, an authorised decision-maker approves or rejects them, and only then are the baseline and traceability records updated. Baselining does not freeze requirements permanently; it establishes a controlled reference point against which changes are managed.
↗ the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) — Validating and Managing Requirements
5/5 · Validating and Managing Requirements · hard
During a pre-release audit, a business analyst finds that a business requirement recorded in the requirements catalogue has no linked acceptance test case, even though the related user requirements derived from it do have linked test cases. What does this gap most likely indicate, and what should the analyst do first?
AA version control problem; the analyst should roll the requirements baseline back to the previous approved version
BA break in vertical traceability; the analyst should investigate why the chain from the business requirement down to a test case is incomplete, then either establish the missing link or raise it for assessment as a potential change
CA failure of formal validation only; the analyst should have the entire requirements document re-issued for sign-off by the project sponsor
DA break in horizontal traceability; the analyst should immediately submit a change request to delete the business requirement from the catalogue
Show answer & explanation
B is correct. Tracing a requirement from the business level down through user requirements to test cases is vertical traceability; a missing link in that chain, while related requirements at a lower level are fully linked, points to an incomplete vertical trace rather than a horizontal (same-level) issue. The correct first step is to investigate and either restore the link or determine, via impact assessment, whether the requirement or its testing needs to be formally changed — not to jump straight to deletion, full revalidation, or a baseline rollback.
↗ the BCS Business Analysis Foundation syllabus v4.1 + 'Business Analysis, 4th Edition' (Paul & Cadle, BCS 2020) — Validating and Managing Requirements
Practise all 6 Validating and Managing Requirements questions - start free → See the whole BCS BA Found. bank

Other BCS BA Found. areas

The same kind of free sample for every other section of the BCS BA Found. bank:

What is Business Analysis?9 qThe Competencies of a Business Analyst6 qThe Strategic Context for Business Analysis12 qThe Business Analysis Service Framework6 qInvestigating the Business Situation17 qAnalysing and Managing Stakeholders14 qImproving Business Services and Processes16 qDefining the Solution11 qMaking the Business Case9 qEstablishing the Requirements12 qDocumenting and Modelling Requirements13 qDelivering the Requirements7 qDelivering the Business Solution8 q

Study Validating and Managing Requirements with instant feedback

6 free questions · filter study mode by area and difficulty · error log with spaced repetition · no card, no dumps, no ads.

Create your free account →
Read next
ECBA vs CCBA vs CBAP: Which IIBA Certification Fits Your Experience Level? (2026) ECBA, CCBA or CBAP? The eligibility gate that picks for you, what the 2026 ECBA rewrite changed, and each credential's three-year cost, verified against IIBA. PMI-PBA vs CBAP: The Business Analysis Certification Decision, Settled with Data PMI-PBA ($405-555, 36 months of experience) vs CBAP ($495-650 all-in, 7,500 hours plus references): eligibility, exam mechanics, three-year cost, salary data.
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.